OmniLuxDocumentation
Public references first, deeper docs next.
OmniLux is expanding its documentation surface in stages. The current public references focus on the SDK, trust model, account and billing behavior, and the core product narrative.
SDK-first visibility
The public SDK page is now the clearest first stop for understanding how OmniLux plugins are structured, reviewed, and moved into the signed-in app experience.
Clear trust language
Permissions, review expectations, and developer paths are being described publicly so the extension model stays easier to audit as it grows.
Docs in progress
Full operator and developer documentation is still being expanded. Until then, public references focus on what is already concrete and reviewable.
Reference surfaces
What you can use today
The current public documentation footprint centers on the SDK overview, legal policies, account flows, and the platform narrative. That makes the public site a useful orientation layer even before the full docs corpus is online.
- SDK architecture, workflow, and trust framing
- Pricing, account, and billing entry points
- Legal pages that explain auth, billing, cookies, and third-party services
Next layer
What is being added next
The next documentation tier should make installation, operator setup, SDK usage, and cloud-connected behavior easier to understand without requiring direct support for every question.
- Installation guides and deployment recipes
- SDK concepts and contribution guidance
- Operator notes for accounts, billing, and connected services
Evaluation
How to evaluate the platform right now
If you are assessing OmniLux today, start with the SDK page, pricing paths, and public product surfaces. That gives you the clearest picture of how the product is positioning itself and how the extension model is being framed.
- Review the SDK workflow and runtime model
- Inspect the public site and account flows
- Use docs.omnilux.tv and Discord for direct technical context
Need something not documented yet?
Use the contact surface or Discord if you need operator guidance, SDK clarification, or a product-specific answer that has not been formalized into the docs yet.