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

# Postgres

> A Postgres database for your app, with backups in Live.

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

```yaml theme={null}
capabilities:
  database: { type: postgres, size: small, extensions: [vector] }
```

* **Live** gets its own database cluster with backups. `small` is one instance; `standard` is two, for high availability.
* **Preview and Beta** each get their own database on a shared Postgres of the same version.
* The app receives the connection string as `DATABASE_URL`, and the usual `PG*` variables. Nobody types a database password.
* Ask for extensions by their `CREATE EXTENSION` name. The platform creates them; your migrations must not.
* Put the schema upgrade command in the component's `migrate` field. It runs before each release, at every stage.

Field details: [gliss.yaml reference](https://docs.glissando.dev/reference/gliss-yaml.md#postgres).


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