Looking for a Data API builder alternative?

One API layer over Postgres, MySQL, MariaDB and ClickHouse.

REST for your apps and MCP for your AI agents, from one binary behind the sign-in you already have.

Free for 60 days, no card.

For the developer

What you get, and how it fits what you run.

One request. No code was written for it.

http
GET /minimal/api/rest/auto/v1/acme/people/pg/acme/employee?fc=id,full_name,department_id&department_id=gt.6&oy=id.as&ps=2&pg=0
json · 200
[
  { "id": 1, "full_name": "Rafael Delacroix", "department_id": 11 },
  { "id": 2, "full_name": "Rafael Müller", "department_id": 7 }
]

From the Book of Minimal, Vol. I. pg is the engine; swap it for ch and the same request reads ClickHouse.

It drops in behind the sign-in you already have

Minimal Core has no login screen of its own. It runs on a private address, such as an internal sub-domain, where only your gateway can reach it. Your gateway already knows who is calling. It adds five headers to each request: organisation, project, environment, user and roles. Minimal Core decides from those what the caller may read or change. There is no user table to migrate and no second login to build.

Every table is a REST endpoint

Each table answers GET, POST, PUT and DELETE. Filters, sorting, column choice and paging are query parameters, so there is no schema language, resolver or client library to learn. Tables start locked; you open create, read, update and delete per role.

Your own logic is one file

When plain CRUD is not enough, you write a Custom API: one YAML file is one endpoint. SQL steps and small scripts run in order, and every write runs in a single transaction. Prove it in your dev environment, then copy it to staging and production.

The right engine for each job, one way to call them

One project can hold Postgres for orders and ClickHouse for analytics. A second engine usually means a second API layer; here it is one segment of the URL, /pg/ or /ch/. The filters, the paging, the errors and the permissions stay the same.

Your APIs become your product’s MCP service, with no code

There are two MCP servers here. The one built into Minimal Core lets an AI agent work with your data in plain English, under the caller’s role and on the audit trail. The second, minimal-mcp, is for your customers: it turns the Auto and Custom APIs you choose into named tools of your own product, behind OAuth 2.1, checking tokens from your own authorisation server. You supply the documentation for each API. You do not write an MCP server. minimal-mcp is a paid add-on.

One binary, with tracing already in it

Run it as a systemd unit, a container or a plain process, from one config file. Set one OpenTelemetry endpoint and every request is traced. Every call, read or write, also writes an audit row saying who made it.

Side by side

Minimal Core and Microsoft’s Data API builder.

Data API builder facts are from Microsoft’s overview, configuration reference, multiple data sources, MCP custom tools and OpenTelemetry pages, read 12 November 2026.

Data API builderMinimal Core
DatabasesSQL Server, Azure SQL, Azure Cosmos DB, PostgreSQL and MySQLPostgres, MySQL, MariaDB, ClickHouse, Aurora MySQL, Percona, TimescaleDB, Vitess, TiDB, CockroachDB, Citus, YugabyteDB, SingleStore, StarRocks and RisingWave
Several engines at onceYes, one config file per database. Entities in different files cannot be relatedYes, in one project, under one URL grammar and one permission model
Your own logicStored procedures you write in the database, exposed as entitiesCustom API: SQL steps and scripts in one YAML file, promoted from dev to staging to production
What you learnREST, GraphQL and its JSON config formatREST. An AI agent needs neither: it asks in English
Sign-inChecks tokens itself (Entra ID or a custom JWT provider), or trusts App Service headersTrusts headers set by the gateway you already run; no login of its own
MCP for your dataYes, from version 1.7: tables and views through generic read and write toolsYes, built in: every table and Custom API, under the caller’s role
Your own APIs as your product’s MCP serviceStored procedures can be registered as named tools from version 2.0. Any other logic needs an MCP server you buildYes, with minimal-mcp: each Auto or Custom API you expose becomes a named tool behind OAuth 2.1. You write documentation, not code. Paid add-on
TracingOpenTelemetry, configuredOpenTelemetry, configured, plus an audit row for every call
How it runsA container or a .NET toolOne binary: systemd, container or process
PriceFree, MIT licence$100 a year plus $1 per 1,000 requests, after a 60-day free trial
StatusGenerally availableBeta. One production workload has run on it for two years

Where Data API builder is the better choice

  • SQL Server, Azure SQL and Azure Cosmos DB. If that is your database, use Data API builder.
  • GraphQL. Minimal Core serves REST and MCP, by choice.
  • A free, MIT-licensed codebase you can change.
  • Checking sign-in tokens inside the API server. Minimal Core leaves that to your gateway.

For the engineering manager

Take the API layer out of the backlog.

The queue you have now

Every new screen, report and agent waits for a backend developer to write, secure and test another route. The database is ready. The API layer is the bottleneck.

What comes out of the queue

The routine routes, the permission checks, the checks that keep one customer’s rows from another, audit and tracing. What stays is the endpoints that are really your product, each one a file.

Changing engines

Change engines without rewriting your routes.

In most stacks the cost of changing engines grows with every route you ever wrote. Here it does not.

  • Generated routes (the Auto API). The engine and the database are one part of the URL. Change your app’s base path once. How many routes you have does not matter.
  • Custom APIs. Each one names its database in one block. Read it, swap the block, save it: two calls, and the same edit every time. A script or a coding agent can run them side by side and check each one before saving.
  • So the work depends only on how many Custom APIs you have, and it divides by the number of workers you run. Even one at a time, a few thousand finish inside a day. Side by side, far sooner.

Two things come on top. SQL written in one engine’s dialect needs a review on the new one. And moving the data itself takes as long as the data is large.

Is it ready

Beta by label. Two years in use.

Minimal Core carries a beta label. It has also served the analytics of a production call-dialling app for two years, stopped only to move to the next version, and it runs the chat on this site. Judge it on the 60-day trial, on your own database, before you pay anything.

For whoever signs it off

A free licence is not a free API layer.

Choosing a tool is one decision. Owning an API layer is eight costs that arrive every month. Data API builder is free, and it also generates routes and traces requests; where it fits your databases, it removes some of these too. The eight below compare Minimal Core with building and running the layer yourself.

With Minimal Core
DevelopmentList, read, insert, update and delete routes are generated. Your developers write only the endpoints that are yours.
Testing and QAGenerated routes behave the same on every table. You test the Custom APIs you wrote, not the plumbing.
DevOpsOne binary and one config file to deploy, on the machines you already run.
UptimeOne production analytics workload has run on it for two years, stopped only for upgrades.
TroubleshootingOpenTelemetry traces on every request and an audit row for every call: who, what, when.
PerformanceEach generated call is one SQL statement, paged at up to 100 rows, so no caller can pull a whole table in one request.
Security and patchingTables start locked. Access is granted per role, separately for apps, AI agents and other services. One binary to patch.
Scaling with trafficPriced per request, so a quiet month costs less than a busy one.

What you pay us

Nothing for 60 days: 3,000,000 requests, every feature, no card. Then $100 a year, plus $1 per 1,000 requests. One million requests is $1,000. It runs on your hardware, and your data never leaves it.

Comparing tools? See Minimal Core and Data API builder side by side, including where Data API builder is the better choice.

Questions

The short answers.

Is Minimal Core a Data API builder alternative?

Yes, on Postgres, MySQL, MariaDB and ClickHouse, and when you want one API layer across more than one of them. On SQL Server, Azure SQL or Cosmos DB, no: use Data API builder, which is free.

Does Minimal Core handle sign-in?

No, by design. It runs on a private address behind the gateway or single sign-on you already have. That gateway adds five headers to each request: organisation, project, environment, user and roles. Minimal Core applies permissions from them.

Can one project use more than one database engine?

Yes. One project can register Postgres, MySQL, MariaDB and ClickHouse databases together. The engine is one segment of the URL; the filters, paging and permissions are the same on each.

Can my own APIs be served to my customers over MCP?

Yes, without writing an MCP server. minimal-mcp, a paid add-on, turns the Auto and Custom APIs you choose into named MCP tools behind OAuth 2.1, using the documentation you supply. Data API builder can register stored procedures as named MCP tools from version 2.0.

Does it serve GraphQL?

No. Minimal Core serves REST and MCP tools. Data API builder serves REST and GraphQL.

What does it cost?

A 60-day trial with 3,000,000 requests and every feature, no card. Then a licence at $100 a year plus $1 per 1,000 requests. One million requests is $1,000. Data API builder is free at any volume.

Point it at a database you already run.

Teaching a coding agent first? Get the one-page skill file. Or read Minimal Core over PostgreSQL, MySQL and MariaDB or ClickHouse. Moving off a backend platform instead? Minimal Core vs Supabase.