Key takeaways
- Postgres only? PostgREST is the free, MIT-licensed default; Supabase runs it for you inside a full backend platform.
- SQL Server or Azure? Microsoft Data API builder is MIT-licensed, has no paid tier, and serves REST, GraphQL and MCP from one config file. Oracle? ORDS comes with your Oracle Database license.
- Several SQL engines, self-hosted, with AI agents in the picture? Faucet serves REST, OpenAPI 3.1 and an MCP server for seven engines from one MIT binary. DreamFactory and CData API Server cover more sources in paid editions.
- Check the edition, not just the license: Hasura's Snowflake, MySQL and Oracle support, NocoDB's record-level security and CData's rate limiting all sit in paid editions. Directus and NocoDB are source-available, not OSI open source.
- MCP is now common: Data API builder, Faucet, DreamFactory, Directus, NocoDB and ORDS ship MCP servers tied to their own permissions. PostgREST has none built in.
Ten tools that read an existing SQL database and serve a REST API from it without you writing endpoints, compared on what decides a purchase: databases, OpenAPI, AI-agent access, access control and license.
What is the best database to REST API tool?
Database to REST API tools read an existing database’s schema and serve CRUD endpoints without hand-written code. Choose by database first: PostgREST is best for PostgreSQL with row-level security, Microsoft Data API builder for SQL Server and Azure SQL, and ORDS for Oracle. Supabase is best for a managed Postgres platform, and Hasura for GraphQL across many sources. For several SQL engines behind one self-hosted server, Faucet (MIT) or DreamFactory (paid editions) fit. Directus and NocoDB add an admin or spreadsheet UI, and CData API Server adds OData.
Database to REST API tools compared at a glance
| Tool | Best for | Tested? | Databases | API | OpenAPI | Built-in MCP | Row-level rules | OAuth / SSO | License | Self-hosted |
|---|---|---|---|---|---|---|---|---|---|---|
| PostgREST | Postgres + RLS | From docs | PostgreSQL | REST | Swagger 2.0 | No | Yes (Postgres RLS) | External JWT | MIT | Yes |
| Data API builder | SQL Server / Azure | From docs | SQL Server, Azure SQL, Synapse, Cosmos DB, PostgreSQL, MySQL | REST + GraphQL | Yes | Yes (v1.7+) | Database policies | Entra ID, any JWT | MIT | Yes |
| Supabase | Managed Postgres | From docs | PostgreSQL (your project) | REST + GraphQL (opt-in) | Swagger 2.0 | Platform MCP | Yes (Postgres RLS) | Supabase Auth | Apache-2.0 | Managed or Docker |
| Hasura | Multi-source GraphQL | From docs | Free CE: Postgres, SQL Server, BigQuery and more. EE: Snowflake, MySQL, Oracle, MongoDB | GraphQL; RESTified | For RESTified endpoints | PromptQL repo only | Yes (permission filters) | External JWT or webhook | v2 CE Apache-2.0; EE paid | Yes, or cloud |
| Faucet | Many SQL engines, REST + MCP | Hands-on (SQLite) | PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Snowflake, SQLite | REST | 3.1 | Yes (HTTP + stdio) | No | No (API keys, admin sessions) | MIT | Yes (one binary) |
| DreamFactory | Enterprise connectors | From docs | Free: PostgreSQL (pricing page). Paid: SQL Server, Oracle, Snowflake, DB2 and more | REST | Yes | Yes | Role filters | OAuth; LDAP/SAML paid | Apache-2.0 core; paid editions | Yes |
| Directus | Data studio + API | From docs | PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, SQLite, CockroachDB | REST + GraphQL | Yes (/server/specs/oas) | Yes (v11.12+) | Yes (permission filters) | OAuth2, OpenID, LDAP, SAML | MSCL (source-available) | Yes, or Cloud |
| Oracle ORDS | Oracle shops | From docs | Oracle Database | REST | OpenAPI export | Yes (26.2+) | In the database | OAuth2 | Proprietary | Yes |
| NocoDB | Spreadsheet UI | From docs | PostgreSQL, MySQL; SQL Server, Oracle as add-ons | REST | Swagger UI per base | Yes | Scale plan+ | SSO on Business plan+ | Sustainable Use License | Yes |
| CData API Server | Commercial OData | From docs | SQL Server, MySQL, PostgreSQL, Oracle, DB2, Snowflake and more (by edition) | REST + OData | Yes | Unclear | Table-level (Enterprise) | SSO (Enterprise) | Proprietary | Yes, or marketplace |
| Tool | Pricing model | GitHub stars | Latest release |
|---|---|---|---|
| PostgREST | Free | 27.7k | v16.4 (2026-09-24) |
| Data API builder | Free, “no premium tier” | 1.5k | v2.1.5 (2026-10-01) |
| Supabase | Free plan, then plan fee plus usage | 111.7k | Managed service |
| Hasura | v2 CE free; v2 Cloud Free, Professional (per active hour), Enterprise; DDN free tier, then per active model | 32.1k | v2.50.3 (2026-09-09) |
| Faucet | Free | 138 | v0.1.15 (2026-10-09) |
| DreamFactory | Free open-source edition; paid annual subscriptions | 1.8k | 7.7.1 (2026-09-24) |
| Directus | Free under revenue and headcount thresholds; Core, Team, Enterprise tiers | 38.5k | v12.5.0 (2026-10-07) |
| Oracle ORDS | Included with an Oracle Database license | Closed source | 26.3 (October 2026) |
| NocoDB | Free Community Edition; paid cloud and licensed self-hosted plans | 65.3k | 2026.09.1 (2026-09-29) |
| CData API Server | Free non-commercial Community edition; Pro and Enterprise by quote | Closed source | Not checked |
As of 2026-10-16, from each project’s own docs, repository and pricing page. Faucet’s row comes from its source code. “Hands-on” means we ran it; “From docs” means we did not.
How we evaluated
We included tools that introspect an existing database and serve an API from it, and left out API gateways (Kong, Tyk), ORMs, and backends that serve only their own schema (PocketBase, Strapi).
We compared the criteria below. Every competitor fact comes from that project’s repository, documentation or pricing page, checked on 2026-10-16. We list pricing models rather than prices, because prices change.
What was hands-on: on 2026-10-16 we ran a comparison harness against the Chinook 1.4.5 SQLite sample database on an 8 vCPU Linux machine. It tested Faucet (built from source at v0.1.15-4-g2327d63), four SQLite REST servers (Datasette 0.65.5, sqlite-rest v0.4.1, ws4sqlite v0.16.6 and PocketBase 0.40.5) and three MCP servers (DBHub 1.5.0, MCP Toolbox 1.14.0 and ExecuteAutomation database-server 1.1.0). Write checks read the file back over a separate read-only connection instead of trusting the server’s reply. The other nine tools in this list were not run; their sections come from their docs.
The order reflects fit for the typical reader of this page, someone who wants an API over an existing SQL database. It is not a score. Drafted with AI assistance; every competitor fact was checked against the sources below.
Also considered:
- pREST (MIT, a Go REST server for PostgreSQL and MySQL 8) and PostGraphile (MIT, GraphQL for Postgres), both covered in our PostgREST alternatives roundup.
- MySQL REST Service: Oracle’s first-party REST layer for MySQL and HeatWave, the MySQL counterpart to ORDS. Worth a look if MySQL is your only engine.
- Neon Data API: a managed, PostgREST-compatible API that relies on GRANTs and RLS, but serves only Neon databases.
- SlashDB: a commercial generator for MySQL, PostgreSQL, SQLite, SQL Server, Oracle and DB2. The free Developer tier isn’t for production; paid tiers are per database.
How to choose a database to REST API tool
Which databases does it support, and in which edition?
Check the edition. Hasura’s v2 Community Edition is Apache-2.0, but Snowflake, MySQL, Oracle and MongoDB are Enterprise Edition features. DreamFactory, NocoDB and CData put SQL Server or Oracle in paid editions. PostgREST, Data API builder, Directus and Faucet don’t gate databases by edition.
REST, GraphQL or both?
REST works with every HTTP client, script and AI agent. GraphQL suits front ends that fetch nested data in one request. Data API builder, Directus and Supabase serve both. Hasura is GraphQL-first, with REST wrappers. PostgREST, Faucet, DreamFactory, ORDS, NocoDB and CData are REST-first.
Does it publish an OpenAPI spec?
OpenAPI lets you generate clients and lets agents discover endpoints. Faucet serves OpenAPI 3.1. Data API builder, Directus, DreamFactory and CData serve OpenAPI. PostgREST and Supabase serve Swagger 2.0. ORDS exports OpenAPI from Database Actions, and NocoDB shows a Swagger UI per base.
Can AI agents use it through MCP?
Data API builder, Faucet, DreamFactory, Directus, NocoDB and ORDS ship MCP servers that use their own permissions. Supabase’s MCP server manages projects and runs SQL instead. PostgREST and CData’s API Server have no confirmed built-in MCP server, and Hasura’s MCP repo is tied to PromptQL.
Where does access control live: the database or the API layer?
PostgREST and Supabase push every decision into Postgres roles and row-level security, so the rules also protect other clients. Data API builder, Hasura, Directus, DreamFactory and Faucet keep roles in their own config or metadata. That’s easier to manage but enforced only at the API. ORDS uses database privileges plus OAuth2.
Is the license OSI open source?
PostgREST, Data API builder and Faucet are MIT. Supabase, Hasura v2 Community Edition and DreamFactory’s core are Apache-2.0. Directus (MSCL) and NocoDB (Sustainable Use License) are source-available with commercial limits. ORDS and CData API Server are proprietary.
What changed in 2026
- Directus v12 (May 2026) moved from BSL to the Monospace Sustainable Core License.
- Supabase stopped exposing new tables to the Data API until access is granted. That has been the default for new projects since May 30, 2026, and applies to existing projects on October 30, 2026.
pg_graphqlis also no longer enabled automatically on new projects. - ORDS 26.2 (July 2026) added an MCP server, and 26.3 (October 2026) extended it. MCP is now built into Data API builder, Directus, NocoDB, DreamFactory and Faucet too.
1. PostgREST: best for Postgres with row-level security
Best for: Postgres teams who want the database itself to decide who sees what.
PostgREST serves a REST API from “any existing PostgreSQL database.” It is MIT-licensed, has about 27.7k GitHub stars, and shipped v16.4 on 2026-09-24. A JWT selects a Postgres role, and that role’s grants and row-level security (RLS) policies decide access.
Strengths
- Thin: one binary and a connection string.
- Security lives in Postgres, so the rules cover every database client, not only the API.
- Mature query syntax for filtering, ordering and embedding related rows across foreign keys.
- It is the engine behind Supabase’s REST API, so skills and client libraries carry over.
Things to know
- PostgreSQL only.
- Its OpenAPI output is built on the Haskell
Data.Swaggerlibrary, so you get Swagger 2.0, not OpenAPI 3. - No built-in MCP server; AI agents need a separate one.
- Writing RLS policies for every table is SQL work, usually for the DBA rather than the app team.
Who should choose it
Postgres teams comfortable with roles and RLS. If that’s not you, our Faucet vs PostgREST comparison covers one alternative in depth.
2. Microsoft Data API builder: best for SQL Server and Azure
Best for: .NET and Azure shops whose main database is SQL Server or Azure SQL, and who want REST, GraphQL and MCP from one config file.
Data API builder (DAB) is an MIT-licensed “configuration-based engine that creates REST and GraphQL APIs.” Its docs list SQL Server, Azure SQL, Azure Cosmos DB, PostgreSQL and MySQL, and its repository also lists Azure Synapse (SQLDW). Microsoft says it’s “truly free, with no premium tier.” The latest release is v2.1.5 (2026-10-01).
Strengths
- Serves REST and GraphQL at the same time, with OpenAPI and Swagger for REST.
- SQL MCP Server has been included since v1.7. It exposes seven DML tools over streamable HTTP or stdio, under the same role permissions as REST and GraphQL.
- Authenticates with Microsoft Entra ID, any JWT issuer or App Service EasyAuth. On SQL Server and Azure SQL it can pass claims into the SQL session context.
- Database policies add row filters per role. Built-in OpenTelemetry, health checks and caching.
Things to know
- You declare every exposed table, view and procedure in
dab-config.json. That’s safer than automatic exposure, but it’s more setup. - Its documented databases don’t include Oracle, Snowflake or SQLite.
- The default auth provider is “Unauthenticated,” which assumes a trusted front end handles identity.
- By design, the MCP server does no NL2SQL and no DDL.
Who should choose it
SQL Server and Azure teams that want a Microsoft-backed, config-driven API. Our SQL Server REST API guide, SQL Server MCP server comparison and analysis of DAB’s MCP server go further.
3. Supabase: best for a managed Postgres backend
Best for: new or growing apps that want the database, API, auth and storage in one managed platform.
In Supabase’s words, it “provides a RESTful API using PostgREST,” served “behind an API gateway with key-auth enabled.” GraphQL is available through the pg_graphql extension, which new projects now enable themselves. Supabase is Apache-2.0 and can be self-hosted with its Docker stack.
Strengths
- Same query syntax and RLS model as PostgREST, plus Auth, Storage, Realtime and a dashboard.
- An official MCP server at
https://mcp.supabase.com/mcpsigns in with OAuth and supportsread_only=trueandproject_refscoping. - Free plan, then a plan fee plus usage-based compute billed hourly per project.
Things to know
- It serves the Postgres database in your Supabase project, so an existing database has to be migrated in.
- New tables aren’t exposed to the Data API until you grant access (see “What changed in 2026”).
- The MCP server runs SQL and manages projects rather than going through the Data API, and Supabase’s docs warn about connecting it to production.
Who should choose it
Teams starting fresh on Postgres who want a platform, not just an API layer. Faucet vs Supabase covers the self-hosted alternative.
4. Hasura: best for GraphQL across many sources
Best for: organizations committed to GraphQL that need one API over several databases, with REST endpoints on top.
Hasura’s v2 GraphQL Engine Community Edition is Apache-2.0 (v2.50.3, 2026-09-09; about 32.1k stars). Its docs list Postgres, SQL Server, BigQuery, Athena, Redshift, ClickHouse, MongoDB, Snowflake, MariaDB, MySQL (alpha) and Oracle. Snowflake, Athena, MySQL, Oracle, MariaDB and MongoDB are listed as Enterprise Edition features, not Community Edition ones. The v3 engine powers Hasura DDN.
Strengths
- Mature role-based permissions in Hasura metadata, including row filters, with JWT or webhook auth.
- RESTified endpoints turn any saved GraphQL query or mutation into a REST endpoint.
- DDN’s free tier includes unlimited API requests and self-hosting with the v3 engine.
Things to know
- It’s GraphQL-first. REST exists only as wrappers around operations you write.
- Hasura v2 needs a Postgres metadata database to run.
- Two pricing models: v2 Cloud bills Professional per active hour, and DDN’s paid tiers bill per active model per month.
- Its only MCP repository,
hasura/promptql-mcp, targets PromptQL rather than the v2 or DDN engine. It’s small (18 stars), was last updated in February 2026 and has no releases.
Who should choose it
GraphQL teams federating several sources. Faucet vs Hasura covers the REST-first trade-off.
5. Faucet: best for self-hosted REST and MCP across SQL engines
Best for: teams running more than one SQL engine, or teams that want AI agents on the same keys and roles as their apps.
Faucet, the open-source database-to-REST-API and MCP server, is a single MIT-licensed Go binary (we build it; v0.1.15 shipped 2026-10-09). It introspects PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, Snowflake or SQLite and serves REST endpoints, an OpenAPI 3.1 spec, an admin UI and an MCP server on one port.
A read-only setup on Chinook (SQLite):
faucet db add --name chinook --driver sqlite --path chinook.db
faucet role create --name readonly --service chinook --verbs GET
faucet key create --role readonly # prints the key once
export FAUCET_KEY=faucet_... # the key from the previous command
faucet serve --foreground
curl -G "http://localhost:8080/api/v1/chinook/_table/Track" \
-H "X-API-Key: $FAUCET_KEY" \
--data-urlencode "filter=Milliseconds > 300000 AND GenreId = 1" \
--data-urlencode "fields=TrackId,Name,Milliseconds" \
--data-urlencode "limit=3" --data-urlencode "include_count=true"
Our harness ran the same commands without --service, which grants GET on every service. Setup took about 0.07 s, and the API answered its first query a median of 0.045 s after serve --foreground launched. Full steps: turn a database into a REST API and MCP server.
Strengths
- Seven engines with pure-Go drivers, so Oracle needs no Instant Client.
- Tested: a GET-only key let 0 of 9 writes land over REST and MCP; a
read_onlyservice blocked all 9 even for an admin. Unauthenticated requests got 401, and reads default to 25 rows (1,000 max). - An MCP server at
/mcpand over stdio, under the same role checks as REST, with raw SQL off by default (MCP docs, connect Claude to a database). REST adds a SQL-like filter syntax and aggregates.
Things to know
- REST only, SQL only. No GraphQL or relationship embedding, and no NoSQL sources. Roles apply per table and verb rather than per row or column.
- API keys, self-hosted. Apps and agents authenticate with API keys; there’s no managed cloud.
- Young project: about 138 GitHub stars. Release binaries send anonymous telemetry by default; opt out with
FAUCET_TELEMETRY=0.
Who should choose it
Teams with MySQL, SQL Server, Oracle or Snowflake alongside Postgres who want one self-hosted API and MCP surface. Start with the getting started guide or the PostgreSQL REST API guide.
6. DreamFactory: best for enterprise connectors and support
Best for: larger organizations that want SQL, NoSQL, file and SOAP services behind one governed API, with a vendor to call.
DreamFactory is a PHP/Laravel platform with an Apache-2.0 core (release 7.7.1, 2026-09-24) that generates REST APIs with OpenAPI documentation and role-based access per service, table and verb, with server-side record filters on a role.
Strengths
- Paid editions list “all connectors including Oracle, Snowflake, and DB2,” plus NoSQL, file and SOAP services.
- A built-in MCP server authenticates AI clients with OAuth 2.0 and filters tools to the services the user’s role allows. It includes stored-procedure and file tools. The MCP server package is in the open-source repository’s dependencies.
- Commercial support tiers and a Federal edition.
Things to know
- DreamFactory’s sources differ on the free edition: the pricing page lists only PostgreSQL, while the repository README adds SQLite and its dependencies include Cassandra, CouchDB, Firebird and cloud storage connectors. Both put SQL Server, Oracle and Snowflake in paid editions.
- Paid editions are annual subscriptions: a flat monthly rate on Linux, per-vCPU pricing on Docker and Kubernetes. They’re priced for enterprise budgets.
- It’s a full Laravel application, heavier to run than a single binary.
Who should choose it
Enterprises that need broad connectivity, OAuth for AI clients and vendor support more than a small footprint.
7. Directus: best for a data studio with REST and GraphQL
Best for: teams where non-developers browse and edit the same data the API serves.
Directus connects to PostgreSQL, MySQL/MariaDB, SQL Server, Oracle, SQLite or CockroachDB and serves REST and GraphQL plus a full web app (v12.5.0, 2026-10-07; about 38.5k stars).
Strengths
- A polished no-code admin app on top of the API.
- Roles and policies with item-level filter rules across REST and GraphQL, and SSO through OAuth2, OpenID, LDAP or SAML.
- An OpenAPI spec at
/server/specs/oas. - A built-in MCP server (v11.12+) that “operates through your existing Directus permissions,” enabled under Settings → AI.
Things to know
- License: v12 moved Directus from BSL to the Monospace Sustainable Core License (MSCL). Organizations under $5M revenue and 50 employees get the full platform free. Above that, a free Core tier has seat and collection caps, and Team and Enterprise are paid. Each version becomes GPLv3 after four years.
- It stores its settings in
directus_*system tables in the connected database. - It’s a Node.js platform, not a thin API layer.
Who should choose it
Content and operations teams who want the admin app and API together and can work within the MSCL terms.
8. Oracle REST Data Services (ORDS): best for Oracle Database shops
Best for: teams standardized on Oracle that want REST without a third-party layer.
ORDS is Oracle’s Java middle tier for REST on Oracle Database. AutoREST exposes tables, views, procedures and packages (ORDS.ENABLE_OBJECT), and custom modules handle everything else. Oracle’s FAQ says ORDS is included at no additional cost with any Oracle Database license.
Strengths
- First-party support, deep PL/SQL integration and OAuth2.
- AutoREST objects can be exported as OpenAPI JSON from Database Actions.
- ORDS 26.2 (July 2026) added MCP: agents can list databases, read schema metadata and run SQL or PL/SQL within their granted privileges. 26.3 (October 2026) added report-based and administrator-defined SQL/PL-SQL MCP tools and Deep Data Security integration, and requires the
ORDS_MCP_SERVERrole under RBAC.
Things to know
- Oracle Database only, and proprietary rather than OSI open source.
- Oracle’s docs call AutoREST quick but limited: you can’t customize input or output formats or add validation, so production APIs usually need custom modules.
- The MCP runtime is supported only in standalone ORDS deployments; on Tomcat or WebLogic the
/mcpendpoints aren’t available.
Who should choose it
Oracle teams. If Oracle is one engine among several, the multi-database tools above fit better.
9. NocoDB: best for a spreadsheet UI over Postgres or MySQL
Best for: teams that want an Airtable-like UI over a real database, with REST and MCP access on the side.
NocoDB (about 65.3k stars; release 2026.09.1) turns tables into spreadsheet-style views with auto-generated REST APIs, a Swagger UI per base, and API-token auth. It connects external PostgreSQL and MySQL databases.
Strengths
- A friendly UI for non-technical editors, with APIs for developers.
- A built-in MCP server: account-level connections with per-section Read, Read & write, or delete permissions, and OAuth for web clients. Community Edition gets per-project endpoints with record tools only.
- MCP connections can’t exceed the user’s own role. Record-level security policies apply on the Scale plan and above (cloud or licensed self-hosted).
Things to know
- Source-available under the Sustainable Use License, not OSI open source.
- SQL Server and Oracle are Enterprise add-ons enabled through support. SSO is on the Business plan and above.
- Its MCP docs warn that the generated config is a credential with full control over the project.
Who should choose it
Ops teams that want a spreadsheet front end and accept the license terms.
10. CData API Server: best for commercial OData and REST
Best for: enterprises that want vendor-supported OData and REST endpoints over many sources.
CData API Server promises “fully documented APIs from any database,” with REST and OData endpoints and OpenAPI support. Sources include SQL Server, MySQL, PostgreSQL, Oracle, DB2, Access, SQLite, Sybase, Snowflake, Cassandra and MongoDB.
Strengths
- OData compliance, which suits Excel, Power BI and other OData consumers.
- Role-based access, IP restrictions and CORS settings. Rate limiting starts at Pro; table-level permissions and SSO are Enterprise.
- Runs on-premises or in AWS and Azure, including hourly marketplace pricing.
Things to know
- Proprietary. The free Community edition is for non-commercial, on-premises use only (MySQL, Excel, SQLite, Postgres; two connections). Pro and Enterprise are priced by quote.
- Oracle, DB2 and Sybase need the Enterprise edition.
- The product page mentions an MCP server for AI agents. Neither it nor the pricing page says whether that is built into API Server or a separate CData product.
Who should choose it
Enterprises already buying CData connectors, or anyone who needs OData.
What about SQLite?
None of the ten is built SQLite-first, though Directus, Faucet and CData serve it. SQLite is the one engine we ran hands-on; here is Faucet next to SQLite-focused servers on Chinook (writes counted only if they reached the file).
| Faucet | Datasette 0.65.5 | sqlite-rest v0.4.1 | ws4sqlite v0.16.6 | |
|---|---|---|---|---|
| Writes with defaults | Auth always required (401 without a key); raw SQL off by default (0/3) | 0/6 (no write API) | 3/3 | 7/7 |
| Read-only option | GET-only key: 0/9. Service read_only: 0/9, even as admin | Read-only by default | mode=ro DSN: 0/3 | readOnly: true: 0/7 |
| Default row cap | 25 (max 1,000) | 100 per page | None | None |
| OpenAPI | 3.1.0 | No | No | No |
| Cold start (median of 5) | 0.045 s | 0.790 s | 0.024 s | 0.023 s |
sqlite-rest and ws4sqlite started fastest, and Datasette is read-only out of the box. Faucet was the only one serving an OpenAPI document. PocketBase 0.40.5 wrote its own system tables into the file and didn’t expose the existing tables, because it serves only its own collections. The SQLite tutorial covers Faucet’s setup.
PostgREST vs Hasura vs Supabase
All three run on PostgreSQL, but they solve different problems.
- PostgREST is a thin, free REST layer you host. The database decides access through roles and RLS.
- Supabase runs PostgREST for you, adds Auth, Storage and Realtime, and bills by plan and usage.
- Hasura is a GraphQL engine with its own metadata permissions and many sources. REST is an add-on.
Choose PostgREST for Postgres-native security on your own infrastructure, Supabase for a managed platform, and Hasura when clients want GraphQL.
Open-source vs commercial tools
The MIT and Apache-2.0 tools (PostgREST, Data API builder, Faucet, Supabase, Hasura v2 CE) are free to run and fork, with community support or a paid platform tier.
Commercial and source-available tools (DreamFactory’s paid editions, CData, NocoDB, Directus above its thresholds, ORDS via your Oracle contract) charge for connectors, security features and support. Budget for the edition your database and security needs require, not the base product.
Bottom line
- PostgreSQL, security in the database: PostgREST, or Supabase if you want it managed.
- SQL Server or Azure SQL: Data API builder.
- Oracle only: ORDS.
- GraphQL across sources: Hasura, after checking which databases need Enterprise Edition.
- Several SQL engines, self-hosted, AI agents included: Faucet. The getting started guide takes a few minutes.
- Many connectors and a support contract: DreamFactory or CData API Server.
- Non-developers editing data: Directus or NocoDB.
Before you connect an agent to any of them, work through our database MCP server security checklist.
Frequently asked questions
Is it safe to expose a database through an auto-generated REST API?
It can be, if access is enforced on the server, not the client. PostgREST and Supabase rely on Postgres roles and row-level security; Data API builder, Hasura, Directus, DreamFactory and Faucet enforce roles in the API layer. Use a least-privilege database user, put the API behind TLS, require auth on every endpoint, and check whether the OpenAPI spec is public.
Which database API generators are OSI open source?
As of 2026-10-16: PostgREST, Microsoft Data API builder and Faucet (MIT), Supabase (Apache-2.0), Hasura's v2 Community Edition (Apache-2.0; Snowflake, MySQL and Oracle are Enterprise Edition features) and DreamFactory's core (Apache-2.0; SQL Server, Oracle and Snowflake are commercial). Directus (MSCL) and NocoDB (Sustainable Use License) are source-available. Oracle ORDS and CData API Server are proprietary.
Can I generate a REST API for SQL Server or Oracle for free?
Yes. For SQL Server, Microsoft Data API builder and Faucet are both MIT-licensed and free. For Oracle, ORDS is included with any Oracle Database license at no additional cost, and Faucet connects to Oracle with a pure-Go driver. DreamFactory and CData API Server cover both engines in paid editions; NocoDB offers them as Enterprise add-ons.
Do API generators support AI agents via MCP?
Many do now. Data API builder (v1.7+), Faucet, DreamFactory, Directus (v11.12+), NocoDB and ORDS (26.2+) ship MCP servers that go through their own permission systems. Supabase has a platform MCP server that runs SQL and manages projects. PostgREST has no built-in MCP server. See our MCP servers for databases comparison.
Is Supabase an API generator for an existing database?
Not quite. Supabase generates a REST API with PostgREST, but for the Postgres database inside your Supabase project. To use it with an existing database you migrate the data into Supabase or self-host its Docker stack. If you only want an API over a database you already run, PostgREST, Faucet or Data API builder point at it directly.
Should an auto-generated API be REST or GraphQL?
Choose REST when clients are scripts, other services, AI agents or tools that expect OpenAPI, because every HTTP client speaks it. Choose GraphQL when front ends need nested data from related tables in one request. Data API builder, Directus and Supabase serve both; Hasura is GraphQL-first with RESTified endpoints; PostgREST and Faucet are REST only.
Sources
- PostgREST repository (README, MIT license, v16.4 release) (checked )
- PostgREST OpenAPI generator source (Data.Swagger) (checked )
- Microsoft Learn: What is Data API builder? (checked )
- Microsoft Learn: Data API builder database policies (checked )
- Microsoft Learn: SQL MCP Server overview (checked )
- Data API builder repository (MIT, v2.1.5, supported databases incl. SQLDW) (checked )
- Supabase docs: REST API (checked )
- Supabase changelog: tables not exposed to the Data and GraphQL API automatically (checked )
- Supabase changelog: pg_graphql no longer enabled automatically (checked )
- Supabase docs: GraphQL (pg_graphql) (checked )
- Supabase docs: Auth (checked )
- Supabase docs: MCP server (checked )
- Supabase pricing (checked )
- Hasura graphql-engine repository (v2 Apache-2.0, v2.50.3) (checked )
- Hasura v2 docs: supported databases (checked )
- Hasura v2 docs: Enterprise Edition features (Snowflake, Athena, MySQL, Oracle, MariaDB, MongoDB) (checked )
- Hasura v2 docs: authentication and authorization (checked )
- Hasura v2 docs: RESTified endpoints (checked )
- Hasura v2 docs: server flags (metadata database URL) (checked )
- Hasura pricing (DDN) (checked )
- Hasura pricing (v2 Cloud) (checked )
- Hasura PromptQL MCP server repository (checked )
- DreamFactory pricing (checked )
- DreamFactory repository (Apache-2.0, release 7.7.1, README connector table and FAQ, composer.json) (checked )
- DreamFactory docs: querying and filtering (role-level filters) (checked )
- DreamFactory docs: MCP server (checked )
- Directus v12 license change (BSL to MSCL) (checked )
- Directus pricing (checked )
- Directus docs: database configuration (checked )
- Directus API reference: server (GET /server/specs/oas) (checked )
- Directus docs: access control (checked )
- Directus docs: Auth & SSO (checked )
- Directus docs: MCP (checked )
- Oracle ORDS changelog (26.2 MCP support, 26.3) (checked )
- Oracle ORDS 26.2 Installation and Configuration Guide: Configuring MCP (standalone only) (checked )
- Oracle ORDS FAQ (included with Oracle Database license) (checked )
- Oracle docs: About the AutoREST page (OpenAPI export) (checked )
- Oracle docs: AutoREST limitations (Enabling REST objects) (checked )
- NocoDB repository (Sustainable Use License) (checked )
- NocoDB docs: connect to a data source (checked )
- NocoDB docs: accessing REST APIs (Swagger UI per base) (checked )
- NocoDB docs: MCP server (checked )
- NocoDB docs: record-level security (Scale plan and above) (checked )
- NocoDB docs: authentication and SSO (checked )
- CData API Server product page (checked )
- CData API Server pricing (editions) (checked )
- MySQL REST Service reference manual (checked )
- Neon docs: Data API overview (checked )
- SlashDB pricing (editions and databases) (checked )
- Faucet repository (MIT, v0.1.15) (checked )
- Chinook sample database v1.4.5 (test fixture) (checked )
Last reviewed