Build the product.Not the infrastructure.
The open-source Next.js foundation for authentication, private data, subscriptions, email and deployment. Clone Xerv, add your brand and build what makes your product different.
Pricing
Start free. Upgrade when you need it.
Example app pricing: Free and Pro, billed monthly or annually. Xerv itself is free and MIT licensed.
Free
$0
Account, recovery, settings, and retained-data access — designed together.
- Account & recovery
- App shell
- Read retained own Example resources
- Delete retained own Example resources
- Billing upgrade path
Pro
$12 / month
Unlock create and edit access for the replaceable Example Resource.
- Everything in Free
- Create Example resources
- Edit Example resources
- Monthly or annual subscription
- Customer Portal
- Server-derived Pro access
No trial. A browser return never grants Pro; access follows trusted server-side billing state and the confirmed paid-through period.
FAQ
Know what you’re
starting from.
A focused foundation is easier to understand, adapt, and trust.
01What is Xerv?
Xerv is a free, MIT-licensed Next.js foundation for individual-account subscription products. The Example Resource is deliberately small and replaceable.
02Is Xerv free and open source?
Yes. Clone, fork and adapt it under the MIT license. Configure your own Supabase, Stripe, Resend SMTP and Vercel resources.
03What does the starter cover?
The supported product surface is intentionally closed: public marketing, Google and email/password Auth, private user-owned data, one Free plan, one Pro entitlement, Billing, Account, Help, and the replaceable Example Resource.
04Which authentication methods are supported?
Google OAuth and email/password with verification, resend, and recovery. Magic-link authentication is intentionally not part of the product.
05Why Supabase?
Supabase is the supported identity and Postgres platform. The private-data contract uses user ownership and Postgres row-level security rather than client-side entitlement checks.
06How is Stripe handled?
The commercial model is Free plus one Pro plan, billed monthly or annually, using Checkout and Customer Portal. The billing contract derives Pro access from trusted financial facts and confirmed paid-through semantics.
07Does access depend on the Checkout success page?
No. The supported billing contract never treats a browser return as authority for Pro access.
08Can I replace the Example Resource with my product?
Yes. It is the replaceable boundary for exercising Auth, ownership, RLS, Pro gating, and CRUD together. Replacing it must not require rebuilding Auth, Billing, Account, configuration, or the app shell.
09Does it support teams or organizations?
No. Xerv deliberately supports individual customer accounts only.
10Is it friendly to coding agents?
Yes. The structure favors few canonical documents, explicit boundaries, generated types, executable tests, and centralized configuration rather than agent-specific frameworks.
11Where does it deploy?
Vercel is the only supported deployment target, with Supabase and Stripe isolated across local, staging, and production environments.