$ npx shipnow init acme
resolved 41 files
wrote .env.local
wrote supabase/schema.sql
linked stripe products
$ npm run dev
One command
Scaffolds the repo and links the project
Stripe, Supabase auth and transactional email already talking to each other. Rename the config, point it at your account, take a payment this weekend.
One time payment. Lifetime updates. Thirty day refund.
export async function POST(req) { const session = await stripe .checkout.sessions.create({ mode: "subscription", line_items: [{ price, quantity: 1 }], }) return Response.json({ url: session.url }) }

Pay ShipNow
$199
Pro licence, one time
Postgres
export async function POST(req) { const session = await stripe .checkout.sessions.create({ mode: "subscription", line_items: [{ price, quantity: 1 }], }) return Response.json({ url: session.url }) }

Pay ShipNow
$199
Pro licence, one time
Postgres
$ npx shipnow init acme
resolved 41 files
wrote .env.local
wrote supabase/schema.sql
linked stripe products
$ npm run dev
Monthly recurring
$12,480

Sign in
$ npx shipnow init acme
resolved 41 files
wrote .env.local
wrote supabase/schema.sql
linked stripe products
$ npm run dev
Monthly recurring
$12,480

Sign in

Production
99
Performance
100
SEO
100
Access
ShipNow
hello@shipnow.dev
Your licence key

Production
99
Performance
100
SEO
100
Access
ShipNow
hello@shipnow.dev
Your licence key
Built on
You already know how to build the product. What kills the launch is the fourth time you wire Stripe webhooks, the second week lost to auth edge cases, and the SEO you keep meaning to do.
Monthly recurring
$12,480
Pay ShipNow
$199
Pro licence, one time
The admin, the billing portal and the account pages are already there, reading from a real Postgres schema with row level security switched on.
The infrastructure disappears
The familiar launch work arrives already connected, so your first commit can be the product.

Launch status
Ready for the idea.
Everything around the idea, already in motion.
02 — Payments
Checkout, portal, signed webhooks, licence keys and refunds already agree with each other. Add your Stripe keys and switch to live mode.
See the payment flow
Monthly recurring
$12,480
Search, already moving
Every route leaves the repo ready to be found, previewed and understood.

Your product
Live this weekend.
Fast, clear and ready to share.
Get startedshipnow.dev
Your product — live
From clone to customer
Watch the infrastructure fall away as the product becomes real.
$ npx shipnow init acme
✓ linked Vercel
✓ wrote .env.local
✓ live URL ready

The one thing
Your product,
not the plumbing.
dev server running
src/config.ts
Payment received
€199.00
Webhook 200 · licence issued
The product starts at hour one.
Checkout, the customer portal and webhook verification
One file
Stripe, Supabase, Resend, Vercel, Next.js and Tailwind are not six tutorials to follow. They are already talking to each other, with typed clients, validated environment variables and one place to put your keys.
Every line is typed. A missing key fails the build, not the checkout.

repo / context
I've read the repo. I'll follow the existing architecture.
05 — Built-in context
Claude Code, Cursor and Codex read the same conventions before they touch a file. The architecture stays coherent, even when the agent changes.
Four context files, zero briefing callsAlready solved, still invisible
A live tour of the systems behind the screen.
Payments
Money arrives cleanly.
€199.00
paid · licence issued

Authentication
Auth that survives contact.
tourAuthBody
Transactional email
Every message, on cue.
The same weekend, two starting points
On the left, infrastructure consumes the weekend. On the right, the product begins immediately.
Starting from scratch
Starting from ShipNow

Your product
liveStripe, auth, email and search are already behind it.
First commit: the idea.
Shipped from the same base
One product so far, built on the same base.
Itoptizads
“I built Itoptizads on this. The parts I always dreaded, Stripe, the auth edge cases, the row level security, were already done and already tested. I spent the first weekend on the product instead of the plumbing, and it went live before I expected it to.”
Afef AyedFounder, Itoptizads
Built by
The person
who wrote it.
Who made this
Every product started with the same Stripe file, auth middleware, schema and OG image route. ShipNow is that work extracted once, so the next product starts at the interesting part.
SaaS 01
shipped
Tool 04
shipped
Portal 07
shipped
App 11
extracted
ShipNow
the base
If something breaks, you email the person who wrote it.
Launch pricing while the first hundred licences go out. No subscription, no seat count, and updates are included for as long as the product exists.
Launch
Save €90one time payment
One project, yours forever
Instant access to the private repo
Studio
Save €140one time payment
Unlimited projects, including client work
Instant access to the private repo
Thirty day refund, no questions, keep what you learned
Access to a private GitHub repository and every future update to it. It is a working Next.js 16 application, not a zip of snippets: auth, Stripe billing, a Postgres schema with policies, transactional email, an admin area, the SEO kit and the component library.
You need to be comfortable running a Next.js app and reading TypeScript. You do not need to have wired Stripe or written an RLS policy before, because those parts are done and documented.
Postgres through Supabase, deployed on Vercel, which is what the setup script configures. Both have free tiers that carry a launch. Nothing stops you moving to another Postgres or another host; the data layer is plain SQL and a typed client.
Launch covers one project. Studio covers unlimited projects, including client work, for as long as you keep the licence.
No. You pay once and the licence does not expire. Updates are included for the lifetime of the product, not for twelve months.
Email within 30 days and you get the money back. You keep whatever you learned from the code.
That is a design goal rather than an afterthought. The repo ships CLAUDE.md, AGENTS.md, .cursorrules and a code map, so Claude Code, Cursor and Codex follow the conventions already in the project instead of inventing new ones.
You reply to your licence email and it reaches the person who wrote the code. There is no ticket queue and no community to search through first. If it is a bug, it gets fixed in the repository and you pull it.
Clone the repo, rename the config, point it at your Stripe account. The next thing you write is the part only you can build.
Pay once, keep the repo, thirty day refund.
$ npx shipnow init acme
resolved 41 files
wrote .env.local
wrote supabase/schema.sql
linked stripe products
$ npm run dev
One command
Scaffolds the repo and links the project
Sign in
Auth
Magic links, OAuth and sessions
Pay ShipNow
$199
Pro licence, one time
Payments
Checkout, the portal and refunds
Postgres
Database
Tables with row level security
ShipNow
hello@shipnow.dev
Your licence key
Licence keys and receipts
Production
Pipeline
Types, build and production deploy