17 engines, one way of working
Every engine below is explored, compared, governed and promoted the same way: the same approvals, the same generated rollback, the same audit trail. Open an engine for its versions and the details worth knowing before you plan around it.
What you get on every engine
Connect it and it behaves like the rest of your estate. Nothing on this list depends on which engine you picked.
Explore under RBAC
Browse objects, preview rows, run SQL and open an ER diagram, with roles per environment and production read-only by default. Every read is attributed to a person.
Compare two environments
Structure and data differences between two databases of the same engine, with a script that closes the gap and the option to turn selected differences into a change script.
Promote with approvals
The same pipeline from DEV to production: approval gates per environment, risk analysis before execute, a rollback prepared with the change, and a hash-chained audit trail.
Watch for drift
Scheduled snapshots against a baseline, so a change nobody filed a ticket for shows up as an event with a restore script beside it.
Cross-engine moves with dedicated support
These are the routes we are asked about most often, each with a dedicated page. Any pair of engines in the catalogue can be discussed; bring us the one you actually have.
Oracle to PostgreSQL
The most common licence-reduction move. Dedicated Oracle schema reading and PostgreSQL schema generation, with the target model reviewed before anything runs.
SQL Server to PostgreSQL
Both engines sit in the tested type mapping matrix, making this the most predictable relational conversion, with CDC available to shorten cutover.
MongoDB to MySQL
Turn nested documents into normalised tables, with control over which fields become child tables and which stay as JSON.
Relational to Snowflake
Move an operational database into the warehouse with generated Snowflake types and post-run validation per entity.
A dedicated page for each of the 17
Versions, what the engine rules out, and the paths most often paired with it.
PostgreSQL
Explore, compare, promote governed change scripts, migrate in and out, and capture changes for a short cutover.
MySQL
Explore, compare, promote governed change scripts, migrate in and out, and capture changes for a short cutover.
SQL Server
Explore, compare, promote governed change scripts, migrate in and out, and capture changes for a short cutover.
Oracle
Explore, compare, promote governed change scripts, and migrate to and from Oracle with a reviewed target model.
Snowflake
Explore, compare, promote governed change scripts, and move an operational database into the warehouse with reviewed types.
MongoDB
Explore documents, compare data, promote governed change scripts, and migrate to and from relational engines with the document shape you choose.
MariaDB
Explore, compare, promote governed change scripts, and migrate with the MySQL-family type matrix.
TiDB
Explore, compare, promote governed change scripts, and migrate over the MySQL protocol.
CockroachDB
Explore, compare, promote governed change scripts, and migrate over the PostgreSQL wire protocol.
YugabyteDB
Explore, compare, promote governed change scripts, and migrate over the YSQL (PostgreSQL) API.
Amazon Redshift
Explore, compare, promote governed change scripts, and load an operational database into the warehouse.
ClickHouse
Explore, compare, promote governed change scripts, and query at analytical speed.
Google BigQuery
Explore, compare, promote governed change scripts, and load an operational database into the warehouse.
Databricks SQL
Explore, compare, promote governed change scripts, and load an operational database into the lakehouse.
Apache Cassandra
Explore, compare, promote governed change scripts, and query keyspaces under the same approvals as any other engine.
DuckDB
Explore, compare, promote governed change scripts, and query analytical files.
SQLite
Explore, compare, promote governed change scripts, and query embedded databases.