Skip to main content
Twenty-nine engines, and every one of them is free to use. What differs between them is where the driver comes from, not what the license covers. Five drivers ship inside the app and cover nine databases. Eighteen registry plugins cover the other twenty and install on the first connection that needs one. See Plugins & Themes.

​
The full list

Rows sharing a page share a driver. MariaDB reads as MySQL, ScyllaDB as Cassandra, Turso as libSQL, and Redshift, CockroachDB and PGlite all speak the PostgreSQL wire protocol.

​
Built-in against plugin

A built-in driver is already in the app and connects with nothing else installed. A plugin is a signed bundle TablePro fetches the first time you pick that engine, before the connection form opens and without a restart. After that the two behave the same: same grid, same editor, same export. The split is about size, not capability. Bundling every client library would put hundreds of megabytes of Oracle and MongoDB code in an app most people use for one database. Plugins update on their own schedule, so a driver fix can reach you without waiting for an app release. Plugins & Themes covers installing, updating and removing them.

​
When yours is not here

Two of these engines already stand in for others. Anything that speaks the PostgreSQL or MySQL wire protocol will usually connect through those drivers, including managed services that never say so: Neon, Supabase, Heroku, Aurora and Cloud SQL all work this way. Point the connection at the host they give you. If it speaks neither, open a request on GitHub. Drivers are plugins, so a new one is a bundle rather than a new version of the app.