Skip to main content

Use Case

The world's most trusted databases deserve effortless migrations.

Minimal completes your migration story.

Postgres, MySQL, MariaDB, ClickHouse, and 15+ more across 3 protocol families — each earns its place in your stack. When it is time to move, the hard work is moving the data. The application layer should cost nothing. With Minimal, it does not. Change one config line. Your API contract is preserved. Your consumers change nothing.

Try Live Apply for a Founders License →

The migration that should only be half as hard.

Your team has outgrown MySQL. Postgres is the right move. The data migration is scoped and understood. Then someone maps the application layer: every ORM model, every API route, every database-specific query, every test. Two months of engineering. One maintenance window. Weeks of unexpected breakage. The migration was worth it. The application layer cost was not. With Minimal, that cost disappears entirely.

  • API endpoints derived from schema at runtime — no routes to rewrite
  • Database type comes from config, not from application code
  • API contract preserved — consumers change nothing
  • Schema differences resolved in migration — not in the application layer
  • Config change reloads instantly — no deployment, no downtime

No code to migrate — because none was written.

Auto API covers 70–80% of every migration. Every endpoint is derived from your schema at runtime — not written by hand. The database type comes from one config variable. Update it when your data migration is complete. Your endpoints reflect the new database. Your API consumers change nothing.

The remaining 20–30% — custom logic, complex joins, business rules — are authored as Custom APIs via MCP. Starlark and Expr are database-agnostic by design. SQL definitions can be re-authored in a single conversation. No sprint. No rewrite.

Before migration

DATABASE = "ms/" # MySQL

After migration

DATABASE = "pg/" # Postgres

One variable. Same endpoints. Same response format. Same API contract.

What remains yours

Moving the data. Schema differences between databases. That work is always yours — and always will be. Everything in the application layer is not.

The Difference

Traditional migration

Rewrite every ORM model

Rewrite every API route

Rework every database-specific query

Full regression test suite

Negotiate a maintenance window

Discover post-launch breakage

Application layer cost: months

Migration + Minimal

No ORM models to rewrite

No API routes to rewrite

No database-specific queries in application code

Endpoint contract unchanged — existing tests pass

Application updates one URL segment — Minimal requires no changes

Nothing in the application layer to break

Application layer cost: near zero

Products Involved

Auto API

Schema-derived endpoints that adapt to the new database automatically on config change.

Custom API

Logic definitions written in SQL, Starlark, or Expr — database-agnostic where possible.

See it on live data.

No signup needed.

Try Live

Or apply for a Founders License — 100 unlimited licenses, free for 12 months.