NanoShip FAQ
Common questions about NanoShip, the production-ready Next.js and Cloudflare starter template. Everything you need to get started and ship.
Quick facts
Production ready
Includes auth, credits, payments, and an AI chat module out of the box.
Cloudflare native
D1, KV, R2, and Durable Objects wired through OpenNext and deployed to Workers.
Five starter pages
Home, changelog, support, FAQ, privacy, and terms with a minimal Simple UI kit.
One command setup
Run the ship skill to wire your brand, domain, and keys into the project.
Frequently asked questions
What do I get with NanoShip?
A working Next.js and Cloudflare site with auth, credits, payments, an AI chat module, i18n, theming, and five starter pages.
Which stack does it use?
Next.js 15 App Router, Cloudflare Workers through OpenNext, D1 with Drizzle ORM, and Tailwind CSS.
Can I remove the AI chat module?
Yes. It lives in its own service and routes, so you can delete it without touching the rest of the template.
How do I rebrand it?
Fill your values in the seed folder and run the ship skill, which writes your brand, domain, and keys into the project.
Is there a pricing page?
A pricing page is planned for a later release. The Stripe skeleton is already in place so you can add pricing yourself.
Does it work without Cloudflare credentials?
Yes. The build and local dev server run entirely offline. You only need credentials when deploying to Workers or applying remote D1 migrations.
Which Node version does it require?
Node 20 or higher is recommended for local development. Cloudflare Workers runs its own runtime in production.
Can I use a different database?
The template is built around Cloudflare D1 and Drizzle ORM. You can swap the database layer, but you will need to update the Drizzle config and the service files that call D1 directly.