Skip to main content

Auto API · Exposure Delay, Eliminated

The schema is the API.
Always was.

Point Minimal at any database. Production-safe REST endpoints exist immediately — for every table, every relationship, every schema change. No route files written. No handlers deployed. No backend changes required when the schema evolves.

< 500µs

Processing time

19+

Databases across 3 protocol families

5

Response formats

How it works

01

Connect your database

Point Minimal at any supported database — Postgres, MySQL, ClickHouse, MariaDB, and 15+ more across 3 protocol families. The runtime reads the schema immediately. Cloud or local via tunnel.

02

Endpoints exist instantly

Every table gets GET, POST, PUT, and DELETE endpoints. Paginated, filterable, governed. The schema is the API contract — always up to date, never out of sync.

03

Schema changes. Nothing breaks.

Add a column, rename a field, change a type. Minimal adapts automatically at runtime. There is nothing to update because there is nothing stored.

ClickHouse

The world's greatest OLAP database deserves a governed API layer.

Minimal completes ClickHouse.

ClickHouse is the fastest columnar database on the planet. Minimal gives it the one thing that makes it complete — a governed REST API layer that any developer, business user, or AI agent can call without writing a line of SQL. Runtime governance. Database untouched.

  • Full aggregation support — GROUP BY, HAVING, ORDER BY, window functions — as governed endpoints
  • Governance lives in the runtime, not the database — no RLS required
  • Same access control model as Postgres, MySQL, and MariaDB
  • MCP-native — AI agents can call ClickHouse endpoints safely

Works identically across ClickHouse Cloud, self-hosted, and local via tunnel.

Aggregations

GROUP BY is not an afterthought. It is a first-class governed endpoint.

Every aggregation operation — GROUP BY, HAVING, ORDER BY, COUNT, SUM, AVG, window functions — is accessible as a governed REST endpoint with the same access control model as every other Auto API call. The same persona scoping. The same audit trail. The same response format options.

Response formats

JSONXMLCSVYAMLBSON

Migration

Changing databases is a config change. Not a quarter of engineering.

Auto API endpoints are derived from your schema at runtime — not written by hand. The database type comes from your configuration file. When your data migration is complete, you update one line. Your endpoints reflect the new database. Your API consumers change nothing.

What well-written application code looks like

# Before migration
BASE_URL = "/minimal/api/rest/auto/v1/"
DATABASE = "ms/"# MySQL
URI = BASE_URL + DATABASE + "d3459kd98/users?fc=id,name,email&ps=10&pg=0"
# After migration — one change
DATABASE = "pg/"# Postgres

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

Built in — not bolted on

Access ControlMulti-TenancyMulti-DatabaseTLS and mTLSPaginationFilteringJSON · XML · CSV · YAML · BSONAudit LoggingSchema IntrospectionPower TokensGROUP BY · HAVING · ORDER BYFull Aggregation Support

Supported databases

PostgreSQL wire protocol

PostgreSQLGreenplumTimescaleDBCitusNeon
Amazon Aurora (PG) βAmazon Redshift βYugabyteDB βCockroachDB βApache HAWQ βEnterpriseDB (EDB) βOrioleDB βAlloyDB β

MySQL wire protocol

MySQLMariaDBPercona Server
Amazon Aurora (MySQL) βPlanetScale βTiDB βSingleStore βVitess βAnalyticDB β

ClickHouse wire protocol

ClickHouseClickHouse CloudByteHouseProtonchDB
Altinity β
ComingOracleSQL ServerSnowflake

Originals and direct forks are fully supported. β databases are wire-protocol compatible and currently in active stress testing — the β mark is removed once a full cycle is complete.

When Auto API isn't enough

The 70% is done. The remaining 30% takes minutes.

Auto API resolves every table, every relationship, every standard operation — instantly. For partial reads, bulk operations, complex filters, and genuine business logic, Minimal provides Custom API: SQL, Starlark, or Expr executing inline inside the same runtime. No external handler. No deployment. No cold start.

No Code = No Ownership = Zero Cost

Explore Custom API →

See it on live data.

No signup needed.

Try Live

Or read why the API layer should not be written at all.