Databases
Supported engines, version floors, and what the beta leaves out.
Tablify supports four engines across two data models. Relational and key/value stay separate, and neither is presented in the other’s terms.
Version floors
| Engine | Minimum | Policy |
|---|---|---|
| PostgreSQL | 15 | Reference driver. Community-supported majors from 15 upward |
| MySQL | 8.4 LTS | The 8.4 LTS line, not the Innovation releases |
| SQLite | 3.37 | Newer types and metadata are preserved without lossy coercion |
| Redis Open Source | 7.2 | Standalone mode only |
These are compatibility targets, not bundled server versions. An older server may connect, but it stays unsupported until it passes the same contract suite.
Capabilities
Each driver declares which operations it supports, including browsing tables, running SQL, cancelling work, running transactions, mutating rows, identifying rows, and negotiating verified TLS. Nothing is inferred from the engine’s name.
Anything a driver does not declare is hidden, or disabled with a reason, before you can reach it. The server checks the same declaration again before dispatching, so a disabled control is never the only thing enforcing it.
Outside the beta
Redis Cluster, Sentinel, and pub/sub are unsupported, as are SQL Server, MariaDB-specific behavior, document stores, and cloud warehouses. See Roadmap.