Manage and deploy

Use your own brand

You can give people a company AI experience in three ways: use the hosted Mobius app, configure the supported hosted experience under your identity, or put the Mobius API behind an interface you build.

The choice is mostly about how much of the visible experience you need to own. It does not change the assistants, account grants, conversations, or routine records underneath.

Choose the experience

Experience	Best fit	What you operate
Hosted Mobius	An internal team that can work at `mobiusops.com`	Your members, assistants, accounts, and access
Configured hosted brand	A provider or company that needs a supported hostname and identity for employees or customers	Brand decisions and DNS, with operator help for edge and sign-in readiness
Custom interface	A product that needs its own navigation, workflows, and end-user authentication	The interface, user mapping, and application behavior around the Mobius API

Start with hosted Mobius when the interface is not part of the problem. Choose a configured hosted brand when the supported app already fits but the door, navigation, and help identity should be yours. Build a custom interface when your product needs a different workflow, not just a different logo.

What the hosted brand covers

A saved brand can set the product name, surface label, sign-in tagline, logos, square mark, primary color, color scheme, support link, sign-in note, governance text, and self-service sign-up policy. Sparse fields inherit the provider or Mobius default instead of copying it into every organization.

Part of the experience	Current behavior	How to confirm it
Product name and surface label	Used in supported app chrome, page titles, and authentication copy	Reload the branded hostname and inspect the title and navigation
Logos, mark, color, and scheme	Loaded from the effective brand at runtime	Check signed-out and signed-in pages in light and dark modes
Hostname and TLS	A hostname record starts `pending`; it is `active` only after the edge and identity systems are ready	Read the reconciled hostname status, then open the HTTPS address
Sign-in	A branded hostname hands authentication to the primary sign-in service and returns the person to the branded host	Complete a signed-out sign-in and confirm the final hostname
Help and sign-in copy	The support link appears at the branded entry and sign-in surfaces; the sign-in note appears on the sign-in screen	Follow the support link and inspect the note during a signed-out sign-in
Governance fields	The current brand record stores a governance title and text, and the internal editor previews them; do not assume another hosted page renders them	Name the exact target surface and verify it before relying on this copy
Other communications	Third-party consent screens, sender domains, and provider messages keep their own configuration	Test each named email, consent screen, or destination separately

A local theme preview proves that the fields and color are valid. It does not prove that DNS, the TLS certificate, or the sign-in return path works.

Know who can configure it

Hosted branding is an operator-managed capability, not a switch inside an ordinary organization settings page.

A provider portfolio must first be enabled. An Owner or Admin of that root portfolio organization can use the portfolio branding endpoints to save its own brand and set or reset the brand for organizations it manages. A native Owner or Admin inside a managed customer organization cannot use that in-org role to replace a provider-owned brand.

The current app does not expose the portfolio brand editor. Mobius platform staff have an internal Branding editor and can perform the same setup with the operator. Hostname activation also needs platform access because the edge certificate and identity-provider satellite must both be checked.

Prepare the brand

Decide these values before the operator starts:

the product name and short label people should see;
light and dark SVG or PNG logos, plus an optional square mark;
one six-digit primary color with readable text contrast;
the support label and HTTPS or mailto: destination; and
the hostname, such as ai.example.com, whose DNS you control.

Uploaded brand assets must be SVG or PNG and no larger than 512 KB. Mobius stores a validated upload at a content-addressed public URL. The saved color is rejected if it cannot produce accessible text contrast.

For a provider with several managed organizations, use inheritance for the common identity. Add a sparse child override only for the fields that customer should change. Choose an own brand when the child must stop inheriting provider changes.

Activate a hostname

Have the portfolio Owner or Admin, or a Mobius platform operator, save the brand for the intended organization.
Register the bare hostname without a scheme, path, or port. Registration reserves it in pending state; it does not claim that the domain works.
Add the DNS record supplied during operator setup.
Have the platform operator provision or adopt the edge hostname and the identity-provider satellite.
Have the platform operator run Check status, which reads both systems and records pending, verifying, active, or failed from their answers.
Continue only when the hostname is active.

An active status means the edge can serve the domain and the identity provider has the satellite registration needed for sign-in. A failure message names the side that still needs repair.

Verify the experience people will use

Use a signed-out browser first. Open the branded root, check the name, logo, mark, color, support link, and sign-up choice, then click Sign in. Inspect the sign-in note on that screen. Complete authentication and confirm that you return to the branded hostname and can open the intended assistant.

Repeat with a real member of the organization. Their role and assistant audience still control what they can use after sign-in. A branded address does not widen organization or resource access.

If customers will see the experience, test one customer identity whose access matches the production boundary. If a service provider will use the same brand for several managed organizations, test one member from each organization and confirm that the active organization, assistants, and records do not cross.

Build a custom interface

A custom interface can use your own layout, hostname, authentication, and product workflow while Mobius runs configured assistants and keeps their sessions. Your application must map each end user to the right organization and conversation, preserve idempotency keys, enforce its own interface access, and reconnect to streamed work safely.

Build a custom interface with Mobius shows the technical path. Start from an existing assistant and its audience rather than copying instructions into every API request.