# Roadmap

> Status: Pre-beta. What is true today, what is planned for v1 and what comes after. Planned work is worth nothing until it is built.

Phases have exit conditions, not dates. Plan item numbers are given so that a claim here can be checked against the project's plan.

## Today

- Strict serializability for every transaction, including across shards.
- Every acknowledged write in the bucket; disposable nodes.
- PostgreSQL wire and an HTTP JSON API.
- Many named databases per deployment; activation on first request and release when idle.
- Whole-image backup, verification, scheduled backups and restore into a new database.
- Tigris and Cloudflare R2 exercised by the project.

## Before the beta

- The beta acceptance run: three hosts, node kills, 48–72 hours of load and a restore drill.
- Storage reclamation, switched on step by step with evidence.

## v1

| Area | Planned | Item |
|---|---|---|
| Schema changes | `ADD COLUMN`, `CREATE INDEX`, `DROP TABLE` | P10.1 |
| Clients | libSQL-compatible endpoint and ORM support | P10.2 |
| Keys and defaults | Generated integer keys; `DEFAULT CURRENT_TIMESTAMP` | P10.3, P10.4 |
| Introspection | A schema surface for migration tools | P10.5 |
| Leaving | Dump and load; one-command import from SQLite-dialect sources | P10.6, P10.6a |
| Client helpers | SDK retry on `40001`, lookup on `40003`; server-side retry of standalone statements | P10.7 |
| Certified list | What works, what is partial, what is refused | P10.8 |
| Vectors | A published contract for exact vector search | P10.9 |
| Tokens | A read-only token; platform-issued short-lived tokens | P10.10, P10.13a |
| Fleet proof | Qualification at 100,000 databases | P10.11 |
| Tenancy | Scopes, paged listing, per-scope limits | P10.12 |
| Failover | 10 s or less at the median, kill to first SQL | P5.11 |

## After v1

| Area | Planned | Item |
|---|---|---|
| Branches | Fork by copy, then copy-on-write | P10.16, P6.8 |
| Recovery | Restore to a transaction ID | P10.17 |
| Insights | Query fingerprints, runtime share, read amplification | P10.23 |
| Fleet | Labels for agent, tenant and environment; listing that never activates | P10.53 |
| Change stream | One resumable cursor in commit order | P10.14 |
| Deploy requests | Diff, lint, gated apply, revert | P10.37 |
| Moves | One procedure for every data move; a home region per database | P10.41, P10.30 |
| Search | Full-text and approximate vector indexes | P10.18, P10.19 |
| Fleet proof | Qualification at one million databases | P10.25 |
| MCP | A server per database with a credential per query | P10.40 |
| Latency | Optional peer-durable mode; shared commit objects | P5.9, P10.55 |

## Gauntlet Cloud

A managed service is designed and not built. The plan is an invited alpha on dedicated deployments in one EU region, then a private beta with billing, then open sign-up. Bring-your-own-cloud packaging follows. No prices are published; see [pricing](https://gauntlet-db.stavros.xyz/pricing) for the model.

## Not planned

- An in-process library with offline sync. A write made offline cannot be strictly serializable against the bucket.
- PostgreSQL SQL in v1.
- Embedding generation inside the server.

---
Source: https://gauntlet-db.stavros.xyz/docs/roadmap