Hatch vs WPGraphQL, Faust.js and static export plugins
An honest comparison of Hatch Connect, WPGraphQL, Faust.js and static export plugins: APIs, hosting, forms, deploys, and when each tool is the right fit.
Last updated October 29, 2026
There are several ways to run WordPress with a separate frontend. This page compares Hatch Connect with WPGraphQL, Faust.js and static export plugins such as Simply Static, so you can pick the right tool. Descriptions of other tools are based on their public documentation at the time of writing; check their sites for current details.
The short version
- WPGraphQL is an API layer: it adds a GraphQL API to WordPress. You build and host the frontend yourself.
- Faust.js is a developer framework for Next.js/React frontends, oriented around WPGraphQL.
- Static export plugins turn WordPress into HTML files you upload to a host such as Cloudflare Pages.
- Hatch Connect deploys a ready-made Astro frontend to a Cloudflare Worker in your own account from the WordPress dashboard, and exposes a REST API under
hatch/v1.
Comparison table
| Topic | Hatch Connect | WPGraphQL | Faust.js | Static export (e.g. Simply Static) |
|---|---|---|---|---|
| What it is | Plugin that deploys an Astro frontend plus a REST bridge | GraphQL API plugin | Next.js/React framework and plugin | Exports the site to static files |
| API | WordPress REST API, hatch/v1 |
GraphQL | WPGraphQL | None needed at runtime |
| Frontend included | Yes, Astro | No | You build it with the framework | Your existing theme, exported |
| Deploy from dashboard | Yes, to your Cloudflare account | No | No | Yes, to supported destinations (see the tool’s documentation for which) |
| Hosting target | Cloudflare Workers only | Any | Any Node host | Several, including Cloudflare Pages |
| Forms, comments, search | Handled through WordPress; Turnstile optional | You build it | You build it | Not part of a plain export; see the tool’s documentation |
| SEO, WooCommerce, ACF data | Reads Rank Math, Yoast, WooCommerce, ACF when active | Through extension plugins | Through WPGraphQL extensions | Whatever the theme outputs |
| Content updates | Publishing tells the frontend to refresh | Depends on your frontend | Depends on your setup | Re-export; how it reaches your host depends on the destination you set up |
| Best for | Site owners and agencies who want Cloudflare without running servers | Developers who want GraphQL | React developers | Brochure sites without dynamic features |
Where Hatch is not the right fit
- You want GraphQL. Hatch uses REST. WPGraphQL is the established choice.
- You want a React or Next.js frontend. Faust.js is built for that.
- You must host somewhere other than Cloudflare. Hatch deploys to Cloudflare only in this version, although its REST API works with any frontend you build.
- Your site cannot be reached over https from the internet. A static export may suit you better.
Where Hatch fits well
- You want a guided, click-through deploy rather than a build pipeline.
- You need forms, comments and optional sign-in that go back to WordPress.
- You want your token and Worker in your own Cloudflare account, with no third-party Hatch server in the middle.
We do not make speed claims against these tools. Performance depends on your content and configuration; test your own site.
FAQ
Can I use Hatch and WPGraphQL together?
They are separate plugins with separate APIs. Hatch’s frontend reads hatch/v1 REST routes, so it does not need WPGraphQL.
Is Hatch a static site generator?
No. It deploys a Worker that reads WordPress over REST, and publishing tells the frontend to refresh.
Does Hatch charge fees?
Hatch itself has no fees. Cloudflare sets its own limits and prices.