Deploy Now

SaaS Alternative

Supabase Firebase Hasura Nhost

Stars

4,631

Forks

324

Watchers

73

Developer links

prest

pRESTd points at your PostgreSQL or MySQL database and instantly serves every table as a REST API, so the CRUD backend you were about to spend a week writing already exists. Every table answers at its own address with filtering, ordering, pagination, and column selection in the query string, and batch endpoints group several operations into one call. When a table endpoint is not enough, drop a SQL file into the queries folder and it becomes a named route with bound parameters, or store the scripts in the database and manage them through the admin API. Turn on the auth module and the server issues JWTs from your own users table, checks them on every route, and enforces table-level permissions so public tables stay open while payroll stays shut. The same database also appears as a read-only MCP endpoint, which lets Claude, Cursor, and other AI clients discover your tables and query them with your permissions instead of a copied export. One process can front several databases at once, Postgres and MySQL side by side, each under its own alias for tenants or reporting replicas. An embedded Studio in the same binary browses the catalog and rows, builds GET requests, and invokes MCP tools, so you can inspect everything from the browser before writing a line of client code. Running on a dedicated VPS on RepoCloud with guaranteed CPU, RAM, and SSD, full root SSH access, and a browser serial console. MIT licensed.

prest
prest
prest

Benefits

  • Skip The CRUD Backend
  • Tables become filtered, paginated REST endpoints the moment pRESTd connects, which removes the controller boilerplate between your database and every client that needs it.
  • Auth And ACL Built In
  • The /auth endpoint mints JWTs from your users table and table-level access rules decide who reads or writes what, without a separate auth service.
  • AI Clients Included
  • A read-only MCP endpoint lets Claude, Cursor, and other agents explore and query your data under the same permissions as any other caller.
  • Many Databases One Process
  • A registry of aliases lets one pRESTd serve tenant, reporting, and legacy databases together, across Postgres and MySQL hosts, behind a single port.

Features

  • Instant Table APIs
  • GET, POST, PUT, and DELETE map to CRUD on /{database}/{schema}/{table} with filters, ordering, pagination, joins, and column selection as query parameters.
  • Custom SQL Routes
  • Named .read.sql and .write.sql scripts become /_QUERIES endpoints with safely bound parameters, stored on disk or in a database registry.
  • JWT Auth ACL
  • /auth validates credentials against your database and returns JWTs; access rules then grant or deny each table per operation and role.
  • Read-Only MCP Endpoint
  • /_mcp exposes tables as tools for AI clients, inheriting the same JWT and ACL stack as REST and never accepting writes.
  • Embedded Studio UI
  • pREST Studio at /_studio/ browses catalogs and rows read-only, builds GET requests, and invokes MCP tools, all inside the single binary.

Apps Similar to prest