DATABASE_URL selects PostgreSQL. If it is unset, Ralti uses the local SQLite database at .atlas/atlas.sqlite, with ATLAS_DATA_DIR overriding the private data root. The application stores workspaces, workbook metadata, sheets, fields, records, views, history, collaborations, email, jobs, and workflow definitions in normalized tables. It does not create a SQL table for every sheet. App definitions and immutable releases, participant grants and tasks, record-number allocations, connected-account state, and agent responsibilities and receipts use this same database.
Typed records and transactions#
Records store typed values associated with their fields. Ralti validates field semantics before saving changes and preserves undo history. Existing saved work remains readable as the application evolves.
| Data | Location | Recovery requirement |
|---|---|---|
| Canonical entities | PostgreSQL or atlas.sqlite | Consistent database backup |
| Uploaded bytes | Configured private local directory or private shared Supabase Storage bucket | Preserve private bytes and checksums with a consistent database backup |
| Email credentials | Encrypted database values | Database backup plus separately preserved encryption key |
| SQLite semantic index | search-v1.sqlite sidecar | Rebuildable from canonical sources |
| Finalized document PDFs and snapshots | Document-version database records | Included in database backup; preserve immutable versions |
PostgreSQL is the intended coordinated deployment option: it supplies pooled access, permissions, revision locks, shared rate limits, and native search indexes. SQLite remains a single-host fallback with single-writer constraints. Do not place its live files on ephemeral storage or share them over a network filesystem.
A database dump alone does not recover uploaded files or the email encryption secret. Conversely, the semantic sidecar is not your source of truth. Keep source databases private and never package the data directory into a public website or container image.
Reports and workflow versions#
Report setups are editable configurations. Generated versions preserve their definition, figures, and exported result. Visual workflows separately retain editable drafts, published executable versions, and durable runs with step progress. Keep these resources in the normal backup and restore process; workspace record history is not a replacement for their version history.
Preserve access and pending work#
Apps and agents add durable definitions, grants, sessions, tasks, private sources, memory, budgets, action intents, and history. Backup, transfer, and deletion handling must cover those related resources, not just visible sheet records. Restoring a definition does not undo completed effects. An uncertain external dispatch must be reconciled rather than replayed.