PostGraphile V5 Beta Status
The V5 pre-alpha phase completed after 38 releases.
The V5 alpha phase completed after 20 releases.
➡️ The PostGraphile V5 beta phase is roughly 90% complete. ⬅️
About PostGraphile V5
Production-ready and already powering many apps, V5 is a complete ground-up rewrite powered by Grafast, our cutting-edge planning and execution engine for GraphQL. It dramatically reduces Postgres load, supports true polymorphism, and introduces incremental delivery, executable schema exports, greater control over your schema, and much more. Its efficient and ergonomic extensibility guides you into the pit of success. It even introduces an “eject button” for when you feel the need to move beyond an autogenerated schema!
V5 remains in “beta” while we finalize the APIs, so minor adjustments may be needed between updates. Postgres-centric users who leverage trusted documents (highly recommended!) should experience particularly smooth sailing!
Current Status
Now that all four epics are complete, all that remains is fixing the types, smoothing the edges, tracking down and adding tests for all the edge cases, adding documentation and a final review of the exposed APIs. Much of this you can help with!
How to help
To aid us in reaching the release candidate stage faster, you can:
- Try V5 out on your real use cases and report back
- Try in production, or just on a test branch
- Send us feedback — good & bad — through GitHub or Discord
- Use benjie/ouch-my-finger to generate minimal reproductions
- Help address issues in the V5 Project Board
- Contribute to documentation and examples
- Sponsor us — you rely on our software, we rely on your financial support
Crowd-funded open-source software
Sponsoring the Graphile project directly increases the time and resources we can spend on getting PostGraphile V5 to release candidate stage. THANK YOU to all our sponsors!
Learn more about sponsorshipEpics - COMPLETE!
With the help of the community, we identified four major issues in our new planning engine, Grafast. These issues related to ergonomics, edge cases, or efficiency; they all required changes to user code (“plan resolvers”), so addressing them before release was vital.
Since fixing these issues required fundamental changes to the way the system works — re-architectures that took many months to complete — we called them “epics”. All four are now complete, hurrah!
- ✅ Global dependencies (solved via “unary” steps that represent exactly one value)
- ✅ Early exit (solved via value “flags” tracking when a value should inhibit dependents)
- ✅ Stop branching due to planning of nested input values (aka remove
$step.eval*()
) - ✅ Avoid excessive polymorphic branching (achieved June 2025)
Milestone releases
Some of the more notable recent releases are listed below. Graphile sponsors have access to release notes through our community support channels. Everyone else can see some detail in the PostGraphile changelog.
Date | Release | Details |
---|---|---|
2025-06-06 | beta.41 | Polymorphism epic achieved (read more) |
2025-03-25 | beta.40 | Removing $step.eval*() epic achieved (read more) |
2024-12-11 | beta.36 | Introduce safe step caching methods |
2024-10-07 | beta.30 | Behavior system overhaul |
2024-07-17 | beta.27 | Error handling overhaul |
2024-05-09 | beta.22 | Early exit and global dependencies epics achieved |
2023-08-03 | beta.1 | Version 5 beta public release (read more) |
2023-04-26 | alpha.1 | First alpha release (sponsors only) |
2023-01-11 | 0.3 | First pre-alpha release (sponsors only) |
Development Support
Priority text support straight from the maintainer
Give your company access to the knowledge and experience of the Graphile team through your chat server and GitHub/GitLab organization. Reference your code verbatim and arrange calls for any trickier topics.
Learn more