The release-candidate programme is complete.
Trestle was delivered as ordered vertical checkpoints, each with implementation, dashboard UX, public documentation and verification. A separate PostgreSQL parity campaign is complete: the parity matrix, migration safety and recovery semantics are exercised against PostgreSQL 16, 17 and 18 in CI and PostgreSQL 18.6 locally. PostgreSQL is available as the external-database option while SQLite and PostgreSQL are both first-class database options.
Foundation and schema
Contracts, lifecycle, SQLite, embedded dashboard, administration and physical collections are implemented and tested.
Data and identity
Versioned records, typed querying, application auth, scoped service identities and collection rules are active.
Files and events
Local and S3-compatible storage, durable realtime, audit, jobs, signed webhooks and AWS Lambda delivery are implemented.
Release candidate
OpenAPI, reference clients, recovery, dogfood repairs, deployment automation and all ten hardening campaigns are complete.
PostgreSQL parity
The SQL surface and behavioral parity corpus are classified, secure configuration and provider-neutral execution are live, and the 13 system migrations run on a real server with authoritative history and an enforced connection timeout. PG04-PG07 added identity, collection, record and query parity against real PostgreSQL. The campaign closes with identity, collection, record, query, access-rule, file, events, jobs, backup/restore and offline cross-provider migration parity. PostgreSQL is available on a proven supported-version window: the CI matrix runs the provider suite on PostgreSQL 16, 17 and 18, and real PostgreSQL 18.6 is exercised locally.
Use SQLite for embedded storage or PostgreSQL 16-18 for an externally operated database. Both expose the same Trestle API. See Database support.
No stable version is published yet. Completion of a roadmap is evidence, not immunity from defects.