Distributions and read keys

A distribution identifies an application or application group within one project. Each has fixed Preview and Production channels. Branches remain editing contexts; changing the header does not redirect a queued release or publication.

Create a distribution

Owner/Admin can create and configure distributions in an active workspace and project. All members can view distributions and publication history.

1. Open Distributions in the project sidebar.
2. Enter Distribution name.
3. Enter exact Allowed web origins, one per line, for web applications. Use HTTPS origins without paths or wildcards. Loopback HTTP is allowed for development. Leave this empty for native applications that do not send an Origin header.
4. Select Create distribution and wait for its policy operation to complete.

Both nodes store the distribution policy durably. Distribution settings updates use the displayed version; concurrent updates return a conflict. A pending policy update must complete before another policy or key change.

Create and revoke read keys

1. Open the distribution and Read keys.
2. Choose a descriptive Key name and the intended channel.
3. Select Create read key. Save the displayed value immediately; it is shown only once.
4. Wait for both policy acknowledgements before using the key.

Production keys cannot read Preview and no delivery key grants management or publication permissions. Applications send it as Authorization: Bearer <key>, never in a URL. A key embedded in a mobile or web app is not a secret; scope limits and server-side authorization remain necessary.

To revoke a key, select Revoke key, review the effect and confirm. Check the policy operation: an unreachable node has not acknowledged revocation, so completion is not claimed until it reconnects. Already cached application content is unaffected.

Only key metadata and hashes are retained on the server. If the initial response was lost, retry with the same idempotency key returns metadata without revealing the secret again. Revoke the unused credential and create another.

Delivery addresses

Distribution node addresses come from operator configuration, not customer-entered URLs. Use both configured public addresses with the delivery protocol. The local installation provides two independent persistent stores; it is not a claim of independent physical infrastructure or production availability.