PostgREST Project

is creating the future of RESTful APIs

Select a membership level


per month
You'll be included in a mailing list for security announcements. You'll also be included in a private gitter room for prioritized support and
roadmap discussion.

Your name will be put in the Backers section of in the PostgREST repository.

Lead Backer

per month

You may prioritize any issue labeled as "bug" in the PostgREST issue tracker.

Your name (hyperlinked) will be put in the Lead Backers section of in the PostgREST repository.


per month

You may prioritize any issue labeled as enhancement in the PostgREST issue tracker.

Your company or personal logo (medium, hyperlinked) will be put on the Sponsors section of the PostgREST README (28k+ visitors per month).




per month

About PostgREST Project

PostgREST is a standalone web server that turns your PostgreSQL database directly into a RESTful API. The structure, constraints and permissions in the database determine the API endpoints and operations.

Using PostgREST is an alternative to manual CRUD programming. Custom API servers suffer problems. Writing business logic often duplicates, ignores or hobbles database structure. Object-relational mapping is a leaky abstraction leading to slow imperative code.
The PostgREST philosophy establishes a single declarative source of truth: the data itself.

PostgREST also seeks to comply with HTTP standards, while maintaining great developer experience and staying as performant as possible.

Since its inception PostgREST has been running on @begriffsfree support, including responding to questions on gitter chat, discussing issues, reviewing pull requests, adding features, solving bugs and adding documentation. This is a lot of work and is clearly unsustainable in the long term.

To ensure PostgREST keeps thriving, we have moved it into its own Github organization, and @steve-chavez has stepped forward as the primary maintainer. Steve is a core contributor who has implemented major features over the past year.

PostgREST has come a long way, from @begriffs' original idea, to the addition of GraphQL-inspired capabilities implemented by @ruslantalpa. Along the way many other contributors have offered their improvements, bug fixes, and advice.

However there's still work to do. Some of the planned improvements include:

More features:

  • Allow using multiple schemas on a single instance
  • Improved memory usage during INSERT
  • INNER JOIN embedding
  • HTTP interface for multiple requests in a single transaction
  • Solving remaining issues

Additions to the documentation:

  • PostGIS Tutorial
  • Nginx/openresty recipes for common use cases
  • FAQ
  • Solve remaining issues in postgrest-docs

With your support we can take PostgREST to the next level. Your donations allow Steve Chavez to spend dedicated time accomplishing the improvements above.
$1,301.65 of $1,500 per month
The $1500/mo goal ensures that Steve Chavez can continue maintaining PostgREST in the long term. He will take care of:

  • PostgREST core: fixing bugs, improving performance, adding new features, refactoring the codebase to ensure stability.
  • PostgREST documentation: evolving and organizing documentation, adding references and how-tos, improving tutorials and explanations.
  • CI and releases: making cross-platform releases for Linux distros, Windows, MacOS, FreeBSD and continuously improving CI infrastructure for better testing and automation.
  • Support: answering questions on gitter chat, discussing issues, helping new contributors, reviewing and merging pull requests.
1 of 1

How it works

Get started in 2 minutes

Choose a membership
Sign up
Add a payment method
Get benefits