Why I Stopped Using Faust.js (And What I Use Instead)

The Appeal of Faust.js

Faust.js is WP Engine’s official framework for headless WordPress with Next.js. It promises built-in WordPress template hierarchy, native preview support, and seamless authentication. For many projects, these are compelling features.

Where It Falls Short

Faust.js is locked to the Pages Router. In 2026, the App Router is the standard for new Next.js projects, and the Pages Router is effectively in maintenance mode. Building on Pages Router means missing out on React Server Components, streaming, and the concurrent rendering features that make modern Next.js so powerful.

The template hierarchy concept, while familiar to WordPress developers, adds a layer of indirection that fights against React’s component model. You end up with two mental models — WordPress templates AND React components — and they do not always agree.

The Alternative: Plain Next.js

A custom Next.js application with WPGraphQL gives you full control. Server components fetch their own data. The App Router handles routing. ISR with on-demand revalidation handles caching. You lose the WordPress-specific conveniences, but you gain the full power of the React ecosystem.

The trade-off is clear: more initial setup work, but a codebase that follows standard React and Next.js patterns. Your team does not need to learn Faust-specific APIs. Your components are portable. Your architecture decisions are yours to make.

When Faust.js Still Makes Sense

If your team is primarily WordPress developers, if you need preview mode today without building it yourself, or if you are building on WP Engine’s hosting platform with its tight Faust integration, it remains a solid choice. The right tool depends on your team and constraints.