Maree-DB speaks MySQL, PostgreSQL, SQL Server, and Redis natively. Your existing applications connect on the same port, with the same client libraries, and the same SQL dialect. Zero code changes. Zero downtime.
Other databases make you rewrite your application to use their proprietary driver. Maree-DB is the first database to natively implement four major wire protocols simultaneously — so your app thinks it's still talking to the same database it always has.
MySQL apps connect on port 3306 — no code changes, no driver changes, no SQL rewrite required.
PostgreSQL apps connect on port 5432 — full protocol v3 compatibility including prepared statements, COPY, and extended query.
SQL Server apps connect on port 1433 — MS-TDS 7.4 protocol, compatible with ADO.NET, JDBC, and ODBC drivers.
Redis clients connect on port 6379 — RESP protocol, compatible with every Redis client in every language.
All protocols simultaneously — run your MySQL app, your Node.js PostgreSQL service, and your Redis cache against the same Maree-DB instance at the same time.
Any MySQL 8.0 client
Any psql / libpq client
ADO.NET, JDBC, ODBC
All RESP clients
Any HTTP client
Use the tools you already know. Because Maree-DB IS MySQL, PostgreSQL, SQL Server, and Redis on the wire, your existing export tools are the migration tool — no special importer needed.
Standard mysqldump works perfectly. Pipe directly into Maree-DB on port 3306.
Standard pg_dump works perfectly. Restore via psql on port 5432.
Standard BCP and SSMS backup-restore work via TDS wire. Your tooling connects unchanged.
Standard redis-cli RDB snapshots restore directly via RESP on port 6379.
Install the Maree-DB cPanel plugin. Existing sites switch automatically — zero manual steps per site.
Leaving Oracle or MongoDB? These need schema and syntax translation. The built-in Migration Wizard handles that automatically.
Maree-DB doesn't need a special migration tool for MySQL, PostgreSQL, SQL Server, or Redis because it is those databases on the wire. Your existing tools are the migration tool.
These migrations need schema and syntax translation that standard dump tools can't handle. The built-in Migration Wizard does it automatically — one command.
Automatic translation of Oracle-specific constructs:
Automatic mapping of MongoDB concepts to SQL + JSONB:
Before you renew your Oracle support contract, run our free compatibility assessment — see exactly how much of your schema translates automatically, and what requires review.
Free Oracle Compatibility Assessment →Before you decide whether to migrate, see what you are actually paying — and what happens if you do nothing.
Oracle pricing based on public list prices: $47,500/processor EE, $23,000/processor RAC, $11,500/processor Partitioning & Advanced Security. 22% annual support. SQL Server: $15,123/core. Maree-DB Enterprise: $499/month × 12. Actual Oracle costs may be higher after volume discounts are removed during audits.
Most teams run a relational database, a cache, a document store, a time-series database, a graph database, and a vector store — all separately maintained, all with separate failover, backups, and licensing. Maree-DB replaces all of them.
SQL · KV · Document · Time-Series · Graph · Vector · Columnar · Spatial
Instead of 6 separate backup jobs with 6 different tools and 6 different retention policies, you have one. Maree-DB's tamper-evident write-ahead log covers all 8 data models simultaneously.
Instead of managing users and roles in 6 separate systems (and forgetting to revoke access in 3 of them), you have one user directory, one role hierarchy, one audit log.
Cross-model queries — joining your relational data to your graph to your time-series — are native. No ETL pipelines, no data synchronisation, no eventual consistency lag between systems.
Change Data Capture replication means you can migrate a production database without a maintenance window. Maree-DB tails your existing database's transaction log and stays in sync until you flip the switch.
Maree-DB takes a consistent snapshot of your source database while it continues to serve traffic.
Live changes are captured from the source binlog / WAL and replayed into Maree-DB with sub-second lag.
Row counts, checksums, and query result comparison confirm data fidelity before cutover.
Update your connection string. Traffic moves to Maree-DB. The source database remains unchanged as a fallback.
Answer four questions and get a realistic estimate of migration complexity and effort.
Early adopters from the Beta Programme.
"We pointed our existing MySQL app at Maree-DB on a Friday afternoon. By Monday we had decommissioned our Redis cluster and our MongoDB instance. One bill, one backup job, one team to call."
Head of Engineering — FinTech startup, Sydney
"The Oracle licence was costing us more per year than the salaries of two senior engineers. We migrated 2.8 TB in a weekend using the CDC replication tool. The cutover was a connection-string change."
CTO — Healthcare analytics, Melbourne
"We run in an air-gapped environment. Every database we evaluated needed a cloud licence server. Maree-DB activated via USB on day one and has never phoned home. That was the requirement."
Infrastructure Lead — Government agency, Canberra