# Gliss

> Your AI writes the app. Gliss makes it real.

> ## 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.

- [What is Gliss](https://docs.glissando.dev/index.md): Your AI writes the app. Gliss makes it real.
- [How Gliss works](https://docs.glissando.dev/get-started/how-it-works.md): What happens between your AI writing an app and the app running in your company's cloud.
- [Quickstart](https://docs.glissando.dev/get-started/quickstart.md): Install the gliss client, sign in, release an app to your Preview or Beta, and connect your AI.
- [For AI agents](https://docs.glissando.dev/for-ai-agents.md): Instructions for an AI assistant asked to build or change a Gliss app: what Gliss is, the exact steps from an idea to a running Preview, and the rules.
- [Concepts](https://docs.glissando.dev/get-started/concepts.md): The words you will meet in Gliss, in plain language.
- [Writing gliss.yaml](https://docs.glissando.dev/build/gliss-yaml.md): How your AI asks Gliss for what an app needs, and what it must leave out.
- [Postgres](https://docs.glissando.dev/build/capabilities/postgres.md): A Postgres database for your app, with backups in Live.
- [Redis](https://docs.glissando.dev/build/capabilities/redis.md): An in-cluster cache for each stage of your app.
- [Bucket](https://docs.glissando.dev/build/capabilities/bucket.md): Object storage for files your app keeps.
- [Hostname](https://docs.glissando.dev/build/capabilities/hostname.md): Your app's web address at each stage.
- [Sign-in (SSO)](https://docs.glissando.dev/build/capabilities/sso.md): Company sign-in in front of your app, with no login code.
- [Secrets](https://docs.glissando.dev/build/capabilities/secrets.md): Declaring the secrets your app needs, without ever writing their values.
- [Healer](https://docs.glissando.dev/build/capabilities/healer.md): A bot that watches your app and proposes fixes.
- [Preview, Beta and Live](https://docs.glissando.dev/build/stages.md): The three stages every app runs in, and how work moves between them.
- [Share and publish](https://docs.glissando.dev/build/share-and-publish.md): Moving your app from Preview to Beta, and from Beta to Live.
- [Secrets and mock mode](https://docs.glissando.dev/build/secrets-and-mock-mode.md): How secret values get set by the people who hold them, and how apps run before they are set.
- [Diagnostics with your AI](https://docs.glissando.dev/build/diagnostics.md): How your AI learns what went wrong, and fixes it without you copying errors.
- [Supported AI tools](https://docs.glissando.dev/build/ai-tools.md): Using Gliss from Claude Code, Claude Desktop, Cursor and Codex: the guidance in every app, and the Gliss tools over MCP.
- [Install Gliss](https://docs.glissando.dev/administer/install.md): Installing Gliss into your company's AWS account from one CloudFormation form.
- [The Gliss GitHub App](https://docs.glissando.dev/administer/github-app.md): What the Gliss GitHub App does in your organisation, and why.
- [The catalog](https://docs.glissando.dev/administer/catalog.md): Deciding what apps may ask for, how much of it, and what Publish requires.
- [Approvals](https://docs.glissando.dev/administer/approvals.md): When Publish needs IT approval, and how to set the policy.
- [Sign-in and SSO](https://docs.glissando.dev/administer/sign-in.md): Connecting Gliss to your company's identity provider.
- [Outbound access](https://docs.glissando.dev/administer/egress.md): Controlling which outside services apps may call.
- [Support access](https://docs.glissando.dev/administer/support-access.md): How Gliss support can look at diagnostics, only when you allow it.
- [Maintenance tiers](https://docs.glissando.dev/administer/maintenance.md): Who keeps the platform and your apps healthy.
- [Security model](https://docs.glissando.dev/administer/security-model.md): What runs where, what Gliss can do in your account, and what it cannot.
- [Levels 1 and 2](https://docs.glissando.dev/engineers/levels.md): When a project needs more than gliss.yaml, and what changes.
- [garden.yml with Gliss action types](https://docs.glissando.dev/engineers/garden-yml.md): Composing an app from Gliss action types at level 1.
- [Garden basics](https://docs.glissando.dev/engineers/garden-basics.md): Projects, actions and the dependency graph: the Garden ideas behind level 1 and level 2 Gliss projects.
- [Building containers](https://docs.glissando.dev/engineers/building-containers.md): Build container images with Garden's container Build action in your own CI.
- [Tests and runs](https://docs.glissando.dev/engineers/tests.md): Run tests and one-off tasks with Garden's Test and Run actions, in CI or in the cluster.
- [Caching](https://docs.glissando.dev/engineers/caching.md): How Garden's action versions let Gliss skip builds and tests that haven't changed, and what the cache holds.
- [Variables and templating](https://docs.glissando.dev/engineers/variables-and-templating.md): Template strings, variables and varfiles in Garden configuration, and how they work in a Gliss project.
- [Helm charts](https://docs.glissando.dev/engineers/helm.md): Deploy your own or third-party Helm charts with Garden's helm Deploy action, at level 2.
- [Kubernetes manifests](https://docs.glissando.dev/engineers/kubernetes-manifests.md): Deploy your own Kubernetes manifests with Garden's kubernetes Deploy action, at level 2.
- [CI with GitHub Actions](https://docs.glissando.dev/engineers/ci.md): How your GitHub Actions workflow builds a Gliss app and requests releases without stored secrets.
- [Troubleshooting](https://docs.glissando.dev/troubleshooting/overview.md): Reading a diagnosis, and what to do for each kind of failure.
- [Capacity](https://docs.glissando.dev/maintenance/capacity.md): When the cluster has no room for an app's pods, and how to add capacity.
- [gliss.yaml](https://docs.glissando.dev/reference/gliss-yaml.md): Every field of gliss.yaml v1, the one file your AI writes to ask Gliss for what an app needs.
- [Catalog](https://docs.glissando.dev/reference/catalog.md): The menu your IT team publishes: what apps may ask for, how much of it, and what Publish requires.
- [Refusal messages](https://docs.glissando.dev/reference/refusals.md): How Gliss says no to a gliss.yaml, with every refusal Gliss is tested against.
- [Install parameters](https://docs.glissando.dev/reference/install-parameters.md): Every value the Gliss install form asks for, and its CloudFormation parameter.
- [AGENTS.md](https://docs.glissando.dev/reference/agents-md.md): The guide for AI assistants that Gliss writes into every app: gliss.yaml, the rules, the stages, day-2 commands and the MCP tools.
- [gliss CLI](https://docs.glissando.dev/reference/cli.md): Commands of the gliss client: sign in, release, status, diagnosis, logs and the MCP server.
- [MCP tools](https://docs.glissando.dev/reference/mcp-tools.md): The tools gliss mcp gives your AI: status, diagnosis, logs, and releases when you allow them.
- [Environment variables](https://docs.glissando.dev/reference/environment-variables.md): What Gliss sets in your app's environment.
- [API](https://docs.glissando.dev/reference/api.md): The Gliss REST API.


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