Professional and community support services

Community Support

Share in the knowledge and experiences of the community by chatting on Discord, or filing issues on GitHub. Please be respectful of and grateful for community members' time.


PostGraphile is crowd-funded - we rely on users to become individual or corporate sponsors and support our work on the PostGraphile project, and to enable us to keep the extremely permissive MIT license.

Sponsoring PostGraphile's ongoing development and maintenance is in your interest; resulting in faster features and fixes, and better documentation.

Read more about sponsorship

Code of Conduct

The Graphile project is covered by our code of conduct. Please be respectful of all people and property.

Community chat

Our Discord chat is a great place to get help when you're just starting out; join us on Discord.

GitHub issues

Our software is open source on GitHub; you may file issues against PostGraphile or Graphile Engine.


Follow us for the latest news: @GraphileHQ

How quickly can I expect a response?

Community support can take anywhere from minutes to years for a response. I'm very grateful to the community for helping each other out, improving the documentation and all the other work they help with. Please be respectful of their time!

Professional Services

Leverage the knowledge and experience of PostGraphile's maintainer, Benjie, and give back to ongoing maintainence and development of the project.

Professional support, from $250/mo

Guaranteed response to critical issues in under 1 business day. Support provided over email, chat and VoIP. NDA available.

Email us at [email protected] for more information.

Open source feature development

If PostGraphile lacks a feature you want, you can get in touch and ask about sponsoring the feature. We'll arrange a time to chat about the feature to ensure we have a shared understanding, it addresses your needs and is feasible, and to determine the time-frames. Assuming we can help you, we'll then follow up with a quote for how much it will cost, and a contract for your review. Open source features you sponsor will remain our property, but we will make them available to you under the terms of the MIT license.

Email us at [email protected] for details.


Consultancy services (advice, code review, training, support, debugging) can be purchased in bundles of 8 or more hours, and consumed in a small number of sessions over a period of 8 weeks.

Email us at [email protected] for details.

How quickly can I expect a response?

We aim to respond to all messages by the end of the next working day (UK calendar); often it will be much (much) sooner.

More information

See FAQs below for more information


Who are you?

Benjie Gillam is the maintainer of the Graphile suite of tools. He has been writing JavaScript for 20 years, PostgreSQL for 10 years and Node.js since early 2012. He's been helping people with their PostGraphile/PostGraphQL issues since 2016.

Jem Gillam wears a lot of hats at Graphile HQ, but her primary roles are community manager and customer happiness. She's had a big hand in Graphile documentation and announcements and is in charge of the Graphile social channels such as Twitter and Discord.

Which repository do I report issues to?

If you know which file contains the issue, please report to the repository that file belongs to. If you're not sure and you're using PostGraphile then please report via the PostGraphile issue tracker. For security vulnerabilities please email [email protected] with the details.

There's a typo in...

We ❤️  typo fixes - and it's the easiest way for you to make your mark on the project! If the typo is in this website; please open a PR to the repository - you can click "Suggest improvements to this page" at the top of most pages. If the typo is in one of the tools, please raise a pull request with the relevant repository.

Raising a pull request is super easy - you can edit a markdown file directly through the GitHub interface - simply find the file in question and press the Edit (pencil) button and follow the instructions. If you're not comfortable raising a pull request, feel free to raise the edit as an issue, but be aware that it'll take longer to fix.