Guides to APIs on PostgreSQL
The questions that come up when you put an API in front of a PostgreSQL database, answered: how REST and GraphQL are generated from a schema, how access control works when the database enforces it, and how the tools that do this differ.
How do teams build an API directly from PostgreSQL?
Three ways to build an API from PostgreSQL, what a generated API gives you, and a worked example serving REST and GraphQL with Postrust.
How do teams manage access control and row-level security behind a PostgreSQL API?
Engineering teams usually enforce API access control in PostgreSQL: a JWT picks the role, GRANTs pick the tables, RLS picks the rows.
Which PostgreSQL-to-GraphQL tool should you use in 2026: Hasura, PostGraphile, Supabase, PostgREST or Postrust?
Hasura, PostGraphile, Supabase pg_graphql, PostgREST and Postrust compared as of October 2026: permissions, REST, subscriptions, Federation, hosting.
How are GraphQL APIs generated from a PostgreSQL schema?
How a GraphQL API is generated from a PostgreSQL schema: catalogue introspection, type mapping, root fields, one-statement SQL and RLS.
What is Apollo Federation, and which open-source projects can be a subgraph?
What Apollo Federation is, what a subgraph must implement, and which open-source tools serve PostgreSQL as a subgraph, as of October 2026.
Which languages are PostgreSQL API servers written in, and does it matter?
Which languages PostgreSQL API servers are written in, from Haskell to Rust, and what the runtime changes: memory, cold starts and deployment.