Cloud Product Contract

This page is the source of truth for how OmniLux Cloud is supposed to behave across the hosted app, managed media, billing, and future native clients.

The short version

OmniLux has two different product layers:

• a first-party cloud account and managed-media layer
• an optional self-hosted server layer

Those layers are related, but they are not the same thing.

What every cloud account gets

Every OmniLux Cloud account is the identity layer for:

• hosted sign-in at app.omnilux.tv
• account recovery
• billing and plan management
• device sign-in across hosted surfaces
• first-party managed media according to the current platform policy

The current default policy is:

• managed media is available to all authenticated cloud accounts

What stays self-hosted

Your own server remains the place where:

• your private libraries live
• your local admin account lives
• local playback happens
• direct LAN, VPN, and user-owned reverse-proxy access happen

OmniLux Cloud does not replace ownership of your own runtime.

What paid cloud is for

Paid cloud is not a tax on local playback.

Paid cloud exists for:

• relay-backed remote access to self-hosted servers
• higher-tier hosted services around your self-hosted runtime
• future premium cloud capabilities that clearly sit outside direct self-hosted ownership

The current default relay policy is:

• self-hosted relay remote access requires an active or trialing paid cloud plan

Managed media contract

media.omnilux.tv is a first-party OmniLux runtime.

It is:

• included through the cloud account according to the managed-media policy
• operated by OmniLux
• surfaced in the hosted cloud app as a managed experience

It is not:

• a claimed customer server
• part of server invites or server ownership
• a replacement for your private self-hosted runtime

Operator contract

ops.omnilux.tv is an internal hosted console.

It is:

• operator-only
• controlled by cloud operator access rules
• used for support, policy, reliability, and incident handling

It is not:

• a customer-facing admin panel
• a self-hosted runtime
• something that should appear in normal server listings

Product rules that should not drift

• Managed media and self-hosted servers must stay conceptually separate in the UI.
• Direct access to self-hosted servers must never be framed as cloud-billed access.
• Relay policy must be stated plainly in billing and server UX.
• Native clients should follow the same contract as the hosted web app.
• Operators can override access, but those overrides should be auditable.

Where this contract should show up

• app.omnilux.tv
• ops.omnilux.tv
• billing copy
• getting started docs
• client-readiness docs
• support runbooks