PostgREST Project is creating the future of RESTful APIs
5

patrons

$129
per month
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.
Tiers
Backer
$10 or more per month 2 patrons
Your name will be put in the Backers section of BACKERS.md in the PostgREST repository.
Lead Backer
$50 or more per month 2 patrons
Your name (hyperlinked) will be put in the Lead Backers section of BACKERS.md in the PostgREST repository.
Bronze Sponsor
$100 or more per month 0 patrons
Your company or personal logo(small, hyperlinked) will be put on the Bronze Sponsors section of the PostgREST README (28k+ visitors per month).
Silver Sponsor
$250 or more per month 0 patrons
Your company or personal logo (medium, hyperlinked) will be put on the Silver Sponsors section of the PostgREST README (28k+ visitors per month).
Gold Sponsor
$500 or more per month 0 patrons
Your company or personal logo (big, hyperlinked) will be put in two places:


  • The top of PostgREST’s README (28k+ visitors per month).
  • The front page on postgrest.org (4k+ visitors per month).
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.

Recent posts by PostgREST Project

Tiers
Backer
$10 or more per month 2 patrons
Your name will be put in the Backers section of BACKERS.md in the PostgREST repository.
Lead Backer
$50 or more per month 2 patrons
Your name (hyperlinked) will be put in the Lead Backers section of BACKERS.md in the PostgREST repository.
Bronze Sponsor
$100 or more per month 0 patrons
Your company or personal logo(small, hyperlinked) will be put on the Bronze Sponsors section of the PostgREST README (28k+ visitors per month).
Silver Sponsor
$250 or more per month 0 patrons
Your company or personal logo (medium, hyperlinked) will be put on the Silver Sponsors section of the PostgREST README (28k+ visitors per month).
Gold Sponsor
$500 or more per month 0 patrons
Your company or personal logo (big, hyperlinked) will be put in two places:


  • The top of PostgREST’s README (28k+ visitors per month).
  • The front page on postgrest.org (4k+ visitors per month).