Supported databases
Database engines and versions Cocobox is tested against.
Cocobox is tested on the matrix below. Other engines may work but are unsupported.
Matrix
| Engine | Versions tested | Read | Write | DDL | SSH tunnel | TLS modes | mTLS | Schema introspection | ER diagram |
|---|---|---|---|---|---|---|---|---|---|
| MySQL | 5.7, 8.0, 8.1, 8.2, 8.4 | ✅ | ✅ | ✅ | ✅ | disable / require / verify-ca / verify-full | ✅ | ✅ | ✅ |
| MariaDB | 10.5, 10.6, 10.11, 11.x | ✅ | ✅ | ✅ | ✅ | disable / require / verify-ca / verify-full | ✅ | ✅ | ✅ |
| PostgreSQL | 12, 13, 14, 15, 16, 17 | ✅ | ✅ | ✅ | ✅ | disable / require / verify-ca / verify-full | ✅ | ✅ | ✅ |
Cloud-managed flavors
Tested and supported:
- AWS RDS (MySQL / MariaDB / Postgres) and Aurora (MySQL- and Postgres-compatible).
- Google Cloud SQL.
- Azure Database for MySQL / PostgreSQL.
- Supabase.
- Neon.
- PlanetScale (MySQL-compatible).
- DigitalOcean Managed Databases.
- Railway.
Special notes:
- PlanetScale doesn’t support
FOREIGN KEYdeclarations; the ER diagram falls back to inferred edges. - Aurora Serverless v1 can have cold starts. Bump the connection’s idle timeout if you see initial-connect timeouts.
- Supabase — connect via the Connection Pooler (port 6543,
Transactionmode) for best performance.
Coming soon
- SQL Server / Azure SQL — beta program; contact devs@cocobox.io.
- ClickHouse — on the roadmap.
- BigQuery / Snowflake / Redshift — being scoped.
If you need an engine that’s not listed, tell us. We prioritize by demand.