> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glissando.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Preview, Beta and Live

> The three stages every app runs in, and how work moves between them.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

People believe that whatever they are looking at is the app. So every Gliss app runs in three separate stages, each with its own database, secrets and address.

| | Preview | Beta | Live |
| - | - | - | - |
| **Who sees it** | You, and people you invite | Invited testers | The audience in `gliss.yaml` |
| **What runs** | Your branch, with changes in seconds | The app as merged, built by CI | Exactly the images that passed Beta |
| **Secrets** | Mock mode by default | Requested, or mock | All must be set |
| **When idle** | Sleeps after 30 minutes; deleted after 7 days | Sleeps after 30 minutes | Always on |
| **Moves on with** | Share to beta | Publish | |

Your IT team's catalog can change the idle times.

## Preview

Your private workspace. With a runtime that supports it (Python and Vite in the first release), a saved change shows in about 5 to 10 seconds, without a full rebuild. A sleeping Preview wakes on the next visit.

The app's `GLISS_STAGE` variable tells it which stage it is in. Show a visible badge on Preview and Beta, for example "Preview: only you can see this".

## Beta

Built from the main branch, for real, by your company's CI. Every merge updates it. Share the link with testers.

## Live

Live never rebuilds. Publish promotes the exact images that ran in Beta. See [Share and publish](https://docs.glissando.dev/build/share-and-publish.md) for what Publish checks.

## Per-stage settings

```yaml theme={null}
stages:
  preview: { config: { LOG_LEVEL: debug } }
  beta:    { secrets: { SALESFORCE_TOKEN: request } }
  live:    { config: { LOG_LEVEL: warning } }
```

Every stage may override `config`. Preview and Beta may also choose `mock` or `request` for each secret. Live may not: every secret must be set before Publish.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.