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

# Maintenance tiers

> Who keeps the platform and your apps healthy.

> [!WARNING]
>
> **Planned.** This page describes designed behaviour that is not built yet. Details may change before it ships.

Every install monitors itself, and receives signed platform releases that keep the agent, add-ons and cluster version current. Releases roll out to Preview and Beta before Live.

You choose who acts on what Gliss finds:

| Tier | Who acts |
| - | - |
| **Self-maintained** | Your team, or your own AI, acting on Gliss findings |
| **Managed** | Gliss maintenance bots, which propose and apply fixes |

In both tiers, nothing changes without a signed release that your cluster verifies. Cluster and database major upgrades always need a person's approval.


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