Client loginBook a call
Build
Custom Software DevelopmentSystems built to your process
Web Application DevelopmentReact, Next.js, Rails, Django
Mobile App DevelopmentiOS, Android, React Native
App DevelopmentWeb and mobile apps, end to end
SaaS Product DevelopmentMulti-tenant from day one
MVP DevelopmentFirst release in 6–10 weeks
Enterprise SoftwareSSO, audit trails, scale
Connect & operate
API Development & IntegrationREST, GraphQL, webhooks
Cloud & DevOps EngineeringAWS, GCP, Azure, Terraform
QA & Software TestingAutomated suites, load, E2E
Legacy ModernizationStrangler-fig migrations
Cybersecurity EngineeringHardening and remediation
Data EngineeringPipelines, warehouses, reporting
Design & teams
UI/UX DesignInterfaces people finish tasks in
Prototyping & DiscoveryScope before you spend
Staff AugmentationSenior engineers on your team
Dedicated Dev TeamsA full pod, one contract
White-Label DevelopmentEngineering under your brand
Technology ArchitectureDecide once, correctly
Project ManagementDelivery you can audit
Start hereScope a build in one callBring a spec, a wireframe, or a paragraph. You leave with an architecture, a timeline, and a number.Book a scoping call
All software development services →How we price work →Talk to an engineer →
AI software
AI Application DevelopmentFull-stack AI products
AI Agent DevelopmentMulti-step autonomous agents
AI SaaS DevelopmentMulti-tenant AI products
Workflow AutomationReplace manual ops
Custom LLM AppsBranded internal assistants
LLM & data systems
Private LLM DevelopmentSelf-hosted Llama, Mistral, Qwen
RAG DevelopmentCited answers over your docs
MCP & WebMCPMake your systems agent-callable
Vector Database Setuppgvector, Pinecone, Qdrant
Document IntelligenceOCR and extraction pipelines
Vibe coding
AI-Assisted BuildsFast, with senior review
Rapid PrototypingClickable in days
Concept to CodeIdea to working software
Code Review & CleanupMake AI output shippable
Fractional AI TeamOngoing build capacity
Ready to ship?Put AI where the work isAgents, RAG, and private LLMs wired into the systems your team already uses — not a chatbot bolted to a homepage.Discuss an AI project
AI development services →AI readiness checklist →AI vs. traditional development →
Domain firstWe learn your workflow before we model itRegulated, operational, or high-volume — the constraints belong in the schema, not in a training doc.Talk about your domain
Selected workSoftware we own and operateMost agencies show screenshots. We run the products — the same stack, uptime, and on-call we hand to clients.View the portfolio
Plan smarterEstimate before you commitCost ranges, scope templates, and the questions we ask in discovery — free, no form.Open the cost calculator
Real conversationsTalk with a technical leadNo SDR, no discovery gauntlet. The person on the call is the one who scopes the build.Book a call
Open-Source CMS · 9d8dev

next-wp

next-wp is a headless WordPress starter combining Next.js 16, React 19, and TypeScript to decouple WordPress content management from a modern frontend. It includes built-in cache revalidation, dynamic routing, search, and deployment templates for Railway and Vercel.

Talk to DEV.coDiscuss Implementation
Source: GitHub — github.com/9d8dev/next-wp
1.3k
GitHub stars
317
Forks
TypeScript
Primary language
MIT
License (OSI-approved)

Key facts

Objective fields from the source. Values we can't verify are shown as “Unknown” rather than guessed.

FieldValue
Repository9d8dev/next-wp
Owner9d8dev
Primary languageTypeScript
LicenseMIT — OSI-approved
Stars1.3k
Forks317
Open issues1
Latest releaseplugin-v1.1.0 (2025-11-27)
Last updated2026-02-25
Sourcehttps://github.com/9d8dev/next-wp

What next-wp is

TypeScript-based Next.js App Router frontend consuming WordPress REST API with server-side pagination, automatic cache revalidation via webhook plugin, dynamic OG image generation, and shadcn/ui component system. Includes Vitest test suite and Docker-ready WordPress plugin for revalidation.

Quickstart

Get the next-wp source

Clone the repository and explore it locally.

terminalbash
git clone https://github.com/9d8dev/next-wp.gitcd next-wp# follow the project's README for install & configuration

Need it deployed, integrated, or customized instead? DEV.co ships production installs.

Best use cases

Content-heavy sites needing rapid iteration

WordPress editors maintain content independently; Next.js front-end deploys instantly on publish via webhook revalidation. Ideal for blogs, news sites, or publishing platforms where editorial velocity matters.

Headless CMS migration from WordPress

Teams already invested in WordPress infrastructure can modernize the presentation layer without rebuilding content workflows. Preserves WordPress plugin ecosystem and editorial familiarity.

Full-stack deployments requiring integrated infrastructure

Railway template bundles MySQL, WordPress, and Next.js in one deployment. Suitable for agencies or startups needing turnkey WordPress + modern frontend without manual DevOps configuration.

Implementation considerations

  • Requires active WordPress REST API endpoint and webhook infrastructure; test webhook delivery and secret rotation in staging before production.
  • Node.js 18.17+ mandatory; pnpm recommended over npm for monorepo-like separation between plugin and app code.
  • Environment variables (WORDPRESS_URL, WORDPRESS_HOSTNAME, WORDPRESS_WEBHOOK_SECRET) must be managed separately per deployment environment (dev/staging/prod).
  • TypeScript definitions in lib/wordpress.d.ts are bundled; custom post types or fields require manual type extension.
  • Search and filtering are client-side debounced queries to WordPress REST API; high-volume searches or large post counts may benefit from Elasticsearch/Algolia abstraction.

When to avoid it — and what to weigh

  • Heavy reliance on WordPress plugins requiring server-side rendering — Headless architecture breaks plugins that depend on wp-admin, theme hooks, or server-side state. Complex plugin interdependencies may not translate to REST API boundaries.
  • Team lacks TypeScript or modern Node.js proficiency — Requires comfort with Next.js App Router, React Server Components, and TypeScript type safety. Learning curve steeper than traditional WordPress theme development.
  • Strict budget constraints or minimal ongoing engineering — Requires maintaining two separate deployments (WordPress + Next.js), monitoring two services, and managing revalidation webhooks. Not suitable for set-it-and-forget-it projects.
  • Real-time updates or collaborative editing features — Cache revalidation is event-driven (publish/update). No live collaboration or real-time subscriptions between WordPress and frontend. Polling or WebSocket extensions would require custom work.

License & commercial use

MIT License. Permissive OSI-approved license allowing commercial use, modification, and redistribution with or without attribution. No copyleft restrictions.

MIT license clearly permits commercial use without royalty or license fees. No enterprise license tier documented. Starter template; production use of WordPress backend and all dependencies remain user's responsibility to license/manage.

DEV.co evaluation signals

Editorial assessment — not user reviews. Directional, with an explicit confidence level.

SignalAssessment
MaintenanceActive
DocumentationStrong
License clarityClear
Deployment complexityLow
DEV.co fitStrong
Assessment confidenceHigh
Security considerations

WORDPRESS_WEBHOOK_SECRET must be cryptographically random and rotated; transmitted in webhook payloads—inspect TLS configuration on both ends. REST API exposure: consider rate-limiting or IP allowlisting on WordPress. Image optimization hostname must match WordPress domain to avoid SSRF via image parameter manipulation. No explicit mention of SQL injection/XSS defenses in README; rely on WordPress core + Next.js built-ins. Plugin auto-activation on Railway could mask security updates—monitor plugin changelog.

Alternatives to consider

Statamic + Laravel

Headless PHP CMS with native REST API; avoids dual-deployment complexity. Trade-off: smaller plugin ecosystem, requires Laravel backend knowledge, less React/TypeScript alignment.

Strapi + Next.js

Node.js-based headless CMS designed for API-first workflows. Trade-off: requires managing Strapi backend separately (no WordPress admin familiarity), smaller content community, more DevOps overhead.

Contentful + Next.js

Fully managed headless CMS with generous free tier. Trade-off: proprietary vendor lock-in, content modeling learning curve, higher cost at scale, WordPress ecosystem features unavailable.

Software development agency

Build on next-wp with DEV.co software developers

Deploy next-wp on Railway in minutes with integrated WordPress and MySQL, or connect to your existing WordPress instance on Vercel. Full TypeScript support and automatic cache revalidation included.

Talk to DEV.co

Related open-source tools

Surfaced by semantic similarity across the DEV.co open-source index.

next-drupalnextjs-woocommercereactpress

Related on DEV.co

Explore the category and the services that help you build with it.

Open-Source CMSWeb App DevelopmentAPI DevelopmentCloud DeploymentTalk to DEV.co

next-wp FAQ

Does this require my WordPress site to run on the same server as Next.js?
No. WordPress and Next.js are completely decoupled. WordPress can be hosted anywhere (Kinsta, WP Engine, self-hosted); Next.js connects via REST API over HTTPS. Deployment can be on different providers (WordPress on WP Engine, Next.js on Vercel).
What happens if the WordPress REST API goes down?
Next.js will fail to fetch posts. Cached pages (via Next.js ISR/static generation) remain served until revalidation is triggered. No fallback UI documented; consider adding error boundaries for graceful degradation.
Can I use custom post types and taxonomies?
Yes, but you must manually extend TypeScript definitions in lib/wordpress.d.ts and add API functions in lib/wordpress.ts. WordPress REST API exposes custom post types by default (if registered with `show_in_rest: true`).
Is the revalidation plugin required for production?
Not strictly required, but highly recommended. Without it, published WordPress edits won't appear on the front-end until the cache naturally expires or manual revalidation is triggered. Strongly impacts editorial workflow.

From evaluation to production software

DEV.co pairs senior engineers with teams adopting tools like next-wp. Our software development services span open-source cms architecture, implementation, and the AI development services that increasingly sit alongside them.

Ready to modernize your WordPress front-end?

Deploy next-wp on Railway in minutes with integrated WordPress and MySQL, or connect to your existing WordPress instance on Vercel. Full TypeScript support and automatic cache revalidation included.

Talk to DEV.coSchedule a Consultation