Hosted, self-hosted, white label

ALYT runs in two modes: hosted by ALYT, or self-hosted by a customer such as a brand or integrator. White label is available in self-hosted mode. The important developer rule is that connector distribution follows approval, not branding: approved connectors are available across the platform, while unapproved connectors stay in the installation that created them. The house keeps working when the cloud is down, and a household sees less than staff. A DEV key acts in a sandbox, and a LIVE key only works for its own connector.

The two ways to run ALYT

	Hosted by ALYT	Self-hosted
Who runs the platform	ALYT	the customer, such as a brand or integrator
Tenancy	multi-tenant	typically one tenant
Branding	ALYT branding	white label permitted
Connector catalogue	the central catalogue	the central catalogue, plus private connectors
Who answers when it breaks	ALYT	the operator, for what they added

Hosted is the default platform. Self-hosted is a documented path for moving a house from ALYT’s hosted environment to hardware the operator controls. The contract, client library, and capability descriptors stay the same, and the base URL changes.

White label

White label is a self-hosted privilege. In the hosted platform, the household is ALYT’s customer and the branding stays ALYT’s. In a self-hosted installation, the operator can present their own brand to their own customers.

This does not change the connector rules. White label changes what the user sees, not who can distribute a connector.

Connector approval and distribution

Connector distribution has two states:

	PUBLIC	PRIVATE
Where it can be installed	every ALYT installation, hosted and self-hosted	only the installation that wrote it
Who approved it	ALYT, through review	nobody
Updates	distributed centrally	shipped by the operator
In the central catalogue	yes	no
Who is answerable	ALYT vetted it; the developer supports it	the operator is entirely responsible

An approved connector is available to everyone, including future updates. An unapproved connector can still be used in a white-labelled mono-tenant or limited self-hosted installation, but it stays private to that installation.

This separation matters for safety and for portability. A common connector should be written once and reused across deployments. A connector for an in-house system, a regional vendor, or something under NDA can stay local without blocking the operator from using the platform.

What self-hosting means for developers

A self-hosted installation uses the same connector contract as the hosted platform. A developer does not rewrite a connector to move between them.

For a developer, the practical difference is where the connector is allowed to live:

• PUBLIC connectors are installed everywhere.
• PRIVATE connectors stay in the installation that created them.

A connected integration keeps the definition version it was connected with. New connections use the newest version available. Moving an existing integration is an operator action.

Hosted, self-hosted, and the offline rule

The house keeps working when the cloud is down. If the connector catalogue cannot be reached, a failed pull does not change the installation. Existing connectors remain available.

That means a self-hosted or hosted installation is not destabilized by a bad or missing catalogue response. The local house keeps the connectors it already had.

What a developer should expect

A developer building against ALYT can expect three boundaries:

1. Hosted and self-hosted use the same API contract.
2. White label is available only in self-hosted mode.
3. Connector approval decides whether a connector is shared broadly or stays private.

A household sees less than staff, so developer and operator tools are not the same as what a home user sees. A DEV key is for sandbox use. A LIVE key only works for its own connector, so production access stays scoped to the connector that owns it.

What this page does and does not promise

This page describes the supported model for hosted, self-hosted, and white label operation. It does not promise that every part of self-hosting is already built. It does promise the rules that matter to developers:

• hosted is the default
• self-hosted allows white label
• approved connectors are distributed centrally
• unapproved connectors stay local to the installation that wrote them
• the house continues to work when the cloud is unavailable
• DEV and LIVE keys stay separated by purpose and scope