Next.js hosting, the way WordPress should have shipped.
Yovale Pages takes the isolated-container, AI-ready, fixed-annual-price idea behind our WordPress product and points it at Next.js. We're building it now. Sign up for early access and we'll mail you when the preview opens.
in development · no card · we'll email when preview opens
Same dashboard, different runtime.
Yovale Pages will live alongside your WordPress sites in the same dashboard — same backups, same crawler logs, same AI visibility, same annual pricing. This view is a mock of what the preview will ship with.
- 12:04:22Edge fetch/blog/post-1 · ISR hit200
- 12:04:18GPTBot/docs · static200
- 12:03:55Build workerdeploy abc1234 finishedok
- 12:03:42Edge function/api/contact · 12ms200
- 12:03:11ClaudeBot/pricing · static200
Vercel is the only honest option, and it's not cheap.
Hosting Next.js properly today means Vercel ($20/seat + bandwidth) or rolling your own on Cloudflare Workers, Netlify, AWS Amplify, Render or DIY VPS. The serious option costs serious money; the cheap options miss ISR, edge functions or the runtime contract.
Most teams running a Next.js site alongside a WordPress site end up paying two hosts, juggling two dashboards, and explaining to the AI crawler dashboard why half their content is invisible to it.
Yovale Pages will run Next.js (App Router, RSC, ISR, edge functions) in the same isolated-container model we use for WordPress — in the same dashboard, with the same crawler visibility, at annual pricing instead of seat pricing. That's what we're building. Waitlist is open.
Same Yovale shape, Next.js runtime.
Four ideas that already work for WordPress, ported to Next.js. None of this is shipped — these are the design decisions we've locked in.
- 0101isolation
One isolated container per app
Same Docker-per-tenant model as our WordPress product. No shared Node runtime, no noisy-neighbour cold starts, predictable memory and CPU ceilings.
design locked - 0202rendering
ISR + RSC + edge functions
App Router with React Server Components, ISR with stale-while-revalidate, edge functions on the same Traefik edge that handles our WordPress sites.
rendering primitives - 0303discovery
AI crawler logs and llms.txt
Same crawler dashboard you'd get on WordPress, applied to your Next.js routes. llms.txt is generated from your route manifest at build time.
AI surfaces shared - 0404pricing
Annual, not per-seat
Target pricing is a fixed annual fee per app — $99 starter, more apps at higher tiers — not per-seat with bandwidth overage panic. Final numbers settle before preview opens.
pricing direction
Where Yovale Pages will sit.
stack direction · still being built
Same control plane, new runtime container.
Pages will reuse Yovale's existing edge (Traefik), control plane (the agent and dashboard) and storage (R2 backups, Postgres metadata). The Next.js runtime container is the only new piece. That's why the timeline is realistic, not aspirational.
Already running for WordPress. Will route to Next.js containers the same way it routes to PHP-FPM containers today. Auto SSL, HTTP/3, no new edge to build.
The new piece. A Docker image we maintain, locked to a Next.js LTS major, with isolated filesystem and bounded memory. This is most of what we're building between now and preview.
The agent that provisions WordPress sites today will provision Pages apps tomorrow. Backups, deploys, env vars, crawler logs — same surface. Less to learn, less to build.
Annual fee per app, not per seat.
These are direction numbers, not commitments. Final pricing locks before private preview opens. Waitlist subscribers get the launch price honoured for the first year.
Likely Starter — 1 Next.js app, isolated container, AI crawler dashboard, daily backups. Higher tiers for more apps.
See what's shipping today.
Adjacent things we already ship.
Things people ask before joining a waitlist.
When can I actually use this?+
Private preview target is Q3 2026, public launch later in the year. Waitlist subscribers get preview invites in waves as we expand capacity.
Will it really be cheaper than Vercel?+
For most apps, yes — that's the design goal. Annual pricing per app rather than per seat, no bandwidth-overage surprises. We won't undercut the experience to hit a price; if we can't ship a good product at $99/yr, we'll set the number higher.
Which Next.js features will work at launch?+
App Router, React Server Components, ISR with on-demand revalidation, edge functions, route handlers, server actions. Image optimisation and OG generation included. Pages Router will work too but isn't the focus.
Can I run it next to my WordPress site?+
Yes — same dashboard, same account, same billing. That's the main reason we're building this in-house rather than partnering with an existing Next.js host.
What about other frameworks?+
Next.js first, then SvelteKit, then Remix / React Router 7. We won't ship a generic 'Node.js runtime' product — the value is in framework-specific tuning, not a bare Node container.
What happens if I waitlist and never get an invite?+
Nothing. We'll mail you when the preview opens — you can decline. We don't pre-charge, we don't reserve capacity.
Join the waitlist before preview fills up.
We're opening preview in waves. Waitlist subscribers get the launch price honoured for the first year. No card on file, no pre-charge.