Know exactly what the candidate supports.

CP23 and the PostgreSQL parity campaign close Trestle's planned implementation and hardening programme. The resulting commit is a release candidate, not a published stable release.

Candidate-supported surfaces

• Linux and macOS on amd64 and arm64, plus Windows on amd64 and arm64.
• One Trestle process using an owned local SQLite database or PostgreSQL 16, 17 or 18.
• Versioned HTTP contracts under /api/v1, /admin/v1 and /system.
• Application users, scoped service identities, access rules, records, files, SSE, jobs, audit, webhooks, Lambda targets, backups and offline restore.
• Cross-provider migration between SQLite and PostgreSQL, with provider-specific backup and restore procedures.
• Checksum-verified archives, user installation, executable update and explicit rollback.

Outside the candidate contract

• Multiple Trestle processes sharing one database or SQLite on a shared/network filesystem.
• Managed/serverless PostgreSQL topologies beyond the tested single-process ownership model.
• Automatic database downgrade during executable rollback.
• Direct application-user file delivery through collection rules.
• Target-aware relation foreign keys or automatic relation expansion.
• Outbound verification email and self-service password recovery.
• An official container image or managed service.