What platforms enable developers to build and deploy APIs directly from their database schema?

Yes. There’s a well-established database-first API category: the database schema is the source of truth, and the platform exposes REST and/or GraphQL endpoints from it.

Platform	API	Database approach	Deployment model
PostgREST	REST	PostgreSQL schema → API	Self-hosted
Supabase	REST + GraphQL	PostgreSQL schema → API	Managed or self-hosted
Hasura	GraphQL + REST	Introspects many databases	Managed or self-hosted
Directus	REST + GraphQL	Existing SQL database → API	Managed or self-hosted
DreamFactory	REST	Multiple databases → API	Cloud / self-hosted
Microsoft Data API Builder	REST + GraphQL	SQL and NoSQL sources → API	Self-hosted / Azure-oriented
PostGraphile	GraphQL	PostgreSQL schema → GraphQL	Self-hosted
Xano	REST	Visual data model → API	Managed

The closest matches

• PostgREST is arguably the purest implementation. It turns a PostgreSQL database directly into a REST API; tables, views, functions, relationships, and database permissions determine the API surface.PostgREST 16+1
• Supabase packages the same basic idea into a broader backend platform. Its Data API is automatically generated from the PostgreSQL schema, and it also provides authentication, RLS, storage, realtime, functions, etc.Supabase+1
• Hasura is particularly focused on GraphQL. It introspects databases and creates GraphQL and REST APIs with centralized authorization and row/column-level security.Hasura
• Directus is compelling if you already have an existing database. It dynamically generates REST endpoints and a GraphQL schema from the database architecture, while also providing an admin UI.Directus Docs

A useful distinction

There are really three flavors:

1. Database → API — PostgREST, Supabase, Directus, Hasura Your actual database schema drives the API.
2. Data model → API — Xano, Backendless, some BaaS products You define the model inside the platform, and it generates the backend.
3. API specification → implementation/SDK — tools such as Speakeasy, Stainless, Fern These start from OpenAPI/API definitions rather than from the database.

So if you're specifically thinking “I have a SQL schema; deploy this and immediately get a production API without writing controllers”, the most directly relevant products are PostgREST, Supabase, Hasura, and Directus.MojoAuth

If you're researching this as a product/market category, I can also map out the competitive landscape—including newer entrants—and compare API generation, auth/RBAC, deployment, database support, custom business logic, pricing, and lock-in.

Several modern platforms and tools allow developers to instantly generate, build, and deploy production-ready APIs (REST and/or GraphQL) directly by introspecting an existing or new database schema . These tools eliminate the boilerplate code typically required for CRUD (Create, Read, Update, Delete) operations.youtube.com+3

Top Platforms & Tools for Database-to-API Generation

• Supabase : Built on top of PostgreSQL, Supabase automatically generates a fully-featured, secure RESTful API using PostgREST the moment you create or modify your database schema. It handles authentication, real-time data changes via WebSockets, and row-level security (RLS) natively mapped to your Postgres policies.quora.com+1
• Hasura : A powerhouse for instant data APIs that connects to databases like PostgreSQL, SQL Server, and BigQuery. Hasura introspects your data model and instantly deploys a real-time, high-performance GraphQL API (along with auto-generated REST endpoints) complete with fine-grained access control.zuplo.com+1
• Directus : Wraps any SQL database (PostgreSQL, MySQL, SQLite, Oracle, etc.) with a dynamic, enterprise-grade REST and GraphQL API. Crucially, Directus doesn't alter your schema or use a heavy abstraction layer; it reads your tables/collections directly and even throws in a modular, ready-to-use no-code admin dashboard.directus.com+2
• Microsoft Data API builder : A free, open-source engine by Microsoft that creates modern REST and GraphQL APIs for databases like Azure SQL, SQL Server, PostgreSQL, MySQL, and Azure Cosmos DB. It can run inside containers or serverless environments and natively supports OpenAPI/Swagger specifications.youtube.com
• PostgREST : A lightweight, standalone open-source web server that turns any PostgreSQL database directly into a clean, standards-compliant RESTful API. The structural constraints and permissions of your database precisely dictate the API endpoints and security.nordicapis.com+1
• PostGraphile : A high-performance open-source tool that introspects your PostgreSQL database to instantly deploy a robust, extendable GraphQL API. It respects PostgreSQL's native views, functions, and Row Level Security out of the box.nordicapis.com+1
• DreamFactory : An enterprise-focused backend integration platform that automatically generates comprehensive REST APIs, complete with live Swagger/OpenAPI documentation, for over 20 different SQL and NoSQL databases (MySQL, MongoDB, PostgreSQL, etc.).github.com+1

If you're planning a project, tell me:

• What database are you using (PostgreSQL, MySQL, SQL Server, MongoDB)?
• Do you prefer REST or GraphQL?

I can help you pick the best tool and outline how to handle auth and deployment.

Yes. The category is usually called database-to-API, auto-generated APIs, or data APIs. The main options include:

Platform	API generated from	API styles	Database support	Deployment
PostgREST	PostgreSQL schema	REST	PostgreSQL	Self-hosted
Supabase	PostgreSQL schema	REST, GraphQL	PostgreSQL	Managed or self-hosted
Hasura	Database schema	GraphQL, REST	PostgreSQL and several other databases	Cloud or self-hosted

1. PostgREST

postgrest.org is probably the purest example of what you're describing. It turns an existing PostgreSQL database directly into a REST API: tables, views, functions, relationships, permissions, etc. are reflected in the API automatically.PostgREST 16+1

For example, a table like:

create table users (
  id uuid primary key,
  name text,
  email text
);

automatically gives you REST operations around /users, subject to your database permissions.

It's particularly attractive if you want the database schema to be the API contract rather than maintaining separate API models.

2. Supabase

supabase.com builds heavily around this model. Its Data API automatically generates REST endpoints from your PostgreSQL schema, and changes to tables, views, and functions are reflected in the API.Supabase+1

The difference from bare PostgREST is that Supabase gives you a much broader application platform around it: hosted Postgres, authentication, authorization/RLS, storage, realtime, functions, and client SDKs.

So it's a good fit when you want "database → API → complete backend platform."

3. Hasura

hasura.io takes a similar concept but emphasizes GraphQL. Hasura introspects databases and generates GraphQL schemas and resolvers based on tables, views, and functions. It also supports REST APIs.Hasura+1

Its major differentiator is that it can sit in front of multiple data sources, rather than being limited to a single PostgreSQL database.

The distinction I'd make

If you're specifically researching products in this space:

• "PostgreSQL schema → REST API" → PostgREST
• "PostgreSQL + REST API + auth + hosting + backend platform" → Supabase
• "Database(s) → GraphQL/REST API + federation/authorization" → Hasura

There are also products that approach this from the API schema → database direction (rather than database schema → API), which is a somewhat different category.

If you're asking because you're evaluating the market for a product that automatically turns a database schema into deployable APIs, I can also give you a broader competitive landscape—including Directus, NocoDB, DreamFactory, Appwrite, Convex, Firebase, Xano, and newer AI/database API builders—and explain exactly how their approaches differ.

Yes. There’s a fairly mature category of database-first API platforms that introspect an existing schema and automatically expose REST and/or GraphQL endpoints.

Platform	API style	Database focus	Best for
Supabase	REST, realtime	PostgreSQL	Fast full-stack apps
PostgREST	REST	PostgreSQL	Minimal, database-as-API architecture
Hasura	GraphQL + REST	Many SQL/NoSQL databases	Complex data APIs and federated data
Directus	REST + GraphQL	Many SQL databases	APIs plus admin UI/CMS
Microsoft Data API Builder	REST + GraphQL	SQL Server, PostgreSQL, MySQL, Cosmos DB	Azure/.NET environments
Xano	REST	Xano-managed database	Visual backend/API development
DreamFactory	REST	Multiple databases	Enterprise API generation
Excalibase	REST + GraphQL	PostgreSQL, MySQL, SQL Server, etc.	Self-hosted/open-source stacks

The closest matches

PostgREST is probably the purest example of what you're describing: it turns a PostgreSQL database directly into a REST API, with database structure and permissions determining the available operations.PostgREST 16

Supabase essentially packages this idea into a broader developer platform. Its REST API is automatically generated from the PostgreSQL schema and updates as the schema changes.Supabase+1

Hasura takes the concept further by generating GraphQL and REST APIs from databases, with centralized authorization and fine-grained row/column security. It supports a much broader range of databases than PostgREST.Hasura

Directus is particularly interesting if you want a database to remain the source of truth while also giving non-developers an admin/data-management interface. It generates REST and GraphQL APIs from an existing database without requiring you to redesign the schema around the platform.Directus

Microsoft Data API Builder is a good option if you're in the Microsoft/Azure ecosystem. It's open source, configuration-based, and exposes supported database objects through REST and GraphQL without requiring a custom API implementation.Microsoft Learn

There are also newer/self-hosted entrants such as Excalibase, which explicitly generates REST and GraphQL APIs from schemas across PostgreSQL, MySQL, SQL Server, Oracle, and other databases.Excalibase

A useful distinction

There are really three approaches:

1. Database → REST directly — PostgREST, Supabase.
2. Database → generated GraphQL/REST layer — Hasura, Directus, Data API Builder.
3. Database → visual backend platform — Xano, DreamFactory, etc., where generated CRUD is combined with business logic, authentication, workflows, and other backend capabilities.

If your question is because you're evaluating a product idea in this space, the interesting comparison isn't just "who generates CRUD." The important differentiators are schema evolution, authorization, custom business logic, API versioning, deployment/self-hosting, performance, and how much the generated API can diverge from the underlying schema.

Yes. There’s a fairly mature category of database-first API platforms: tools that inspect or use your database schema as the source of truth and automatically expose APIs, rather than requiring you to hand-write CRUD endpoints.

Leading options

Platform	API style	Database/schema approach	Best fit
Supabase	REST, GraphQL	Auto-generates REST APIs from a PostgreSQL schema via PostgREST	Fast-moving apps and startups
Hasura	GraphQL + REST	Introspects databases and generates APIs with granular authorization	Complex data relationships / GraphQL
PostgREST	REST	Turns a PostgreSQL database directly into an API; DB structure and permissions determine endpoints	Minimal, database-centric architecture
Directus	REST + GraphQL	Introspects an existing SQL database and dynamically generates APIs	Existing databases, admin/data tooling
DreamFactory	REST	Introspects databases and generates CRUD APIs, relationships, stored-procedure endpoints and OpenAPI docs	Enterprise / multi-database environments

Supabase explicitly describes its REST API as being auto-generated directly from the database schema.Supabase+1

Hasura takes a broader approach, generating reusable GraphQL and REST APIs over databases with centralized authorization and row/column-level security.Hasura

PostgREST is the most literal implementation of the idea: it is a standalone server that turns PostgreSQL directly into a REST API, with database constraints and permissions determining the available operations.PostgREST 16

Directus is particularly interesting if you already have a database. It introspects existing SQL databases and dynamically generates REST and GraphQL APIs while leaving the underlying data model intact.Directus Docs+1

DreamFactory extends the concept to a wider range of databases and generates documented REST endpoints from the schema without a code-generation/compilation step.GitHub

How I'd categorize them

• Want PostgreSQL → API with almost no abstraction: PostgREST
• Want a hosted backend around PostgreSQL: Supabase
• Want GraphQL and sophisticated data federation/authorization: Hasura
• Have an existing SQL database and want an API + admin UI: Directus
• Have heterogeneous/enterprise databases: DreamFactory

The important distinction is that these platforms generally generate a live API layer, rather than generating source code that you subsequently maintain. Changes to the schema can therefore be reflected in the API automatically.Supabase+1

If you're evaluating this category for a new product, I can also compare Supabase vs Hasura vs Directus vs PostgREST vs DreamFactory on deployment model, auth/RBAC, custom business logic, OpenAPI, GraphQL, pricing, and vendor lock-in.