One repo, two apps
Your site and your api, sharing one set of types.
fast-forward-dev
apps/webWhat people see
- TanStack StartRouting
- ReactInterface
- Tailwind CSSStyling
- daisyUIThemes
- ClerkSign-in
- TanStack QueryData
Clone the repo.Fast-forward to launch.
A web app and a separate API in one monorepo, with sign-in and payments already wired. Clone it, let your agent run the setup, and ship.
Ten tools, one job each
Each piece of the stack does one job in this repository, and each card shows that job being done.
TanStack Start
File-based routing and server rendering
TypeScript
Strict from the database to the browser
Tailwind CSS
Utility classes over one token file
daisyUI
A component layer with a light and a dark theme
Express
The api that owns billing and access
Clerk
Email codes, Google and GitHub sign-in
Stripe
One-time purchases and subscriptions at once
Drizzle
Typed queries and generated migrations
PostgreSQL
Every purchase and entitlement in one place
Resend
Transactional email written as React
The backbone of every project
Four systems every product rebuilds from scratch, wired together so you don't have to.
Sign-in without passwords
Email codes, Google and GitHub, ready on day one.
you@example.com
or
Billing that stacks
One-time purchases and subscriptions, unlocked the moment they are paid.
Pro
$169.00 once
- Checkout paid
- Webhook received
- Purchase recorded
- Entitlement granted
- GitHub invite sent
Docs and a blog in every language
Write in Markdown, publish in English and Danish.
/docs/setup/install
Install and run
Clone the repo, install with pnpm, and hand the in-repo setup to an agent through SETUP.md.
Get started in minutes
Paste one prompt into your coding agent. It clones the repo and sets up every service for you.
Clone github.com/fast-forward-dev/fast-forward-dev and follow SETUP.md
Your agentReading SETUP.md
Neonsub-agent
- neon link --no-env-pull
- Postgres linked, database URL written
Clerksub-agent
- clerk link --app app_31sBqM
- Clerk keys written to both apps
Stripesub-agent
- stripe login
- Stripe account verified
- stripe listen --forward-to localhost:5001/stripe/webhook
- Webhooks forwarding to the api
~/my-productmain agent
- pnpm db:migrate
- Migrations applied
- pnpm dev
- Web on localhost:3000, api on localhost:5001
The rest of the launch checklist
Dashboard
Access, billing and invites
Admin
User lookup and invite re-sends
Transactional email
Written in React, sent by Resend
Docs search
⌘K across every page
Light and dark
No flash on load
SEO
Sitemap, robots.txt and llms.txt
Analytics
PostHog, off until you add a key
Changelog
Dates the pricing card
Agent-ready
AGENTS.md, skills and a setup guide
Hi, I'm Emil
I'm a developer at a tech company by day, and I build my own products the rest of the time. Most of what I learn along the way ends up on my YouTube channel.
Every product I started began the same way: a week of wiring up login, payments and email before I could touch the idea. Fast Forward Dev is the repo I wish I'd had on day one.
I like my frontend and my backend kept apart. The web app handles the interface, and the api keeps the money, the data and the secrets. I just don't want two repos to juggle, so they live side by side in one.
- Writing code since
- 2017
- Startups built in a year
- 4
- Days to build the first version
- 30
More about me on my about page.
Ship the parts nobody wants to build twice
The site you are reading is the thing you get.
Pro
The boilerplate, and the storefront that sells it. One repo.
$169.00once
Pay once. Access is never revoked.
- Permanent read access to the repository
- Web app (TanStack Start)
- API (Express)
- Auth (Clerk)
- Billing (Stripe)
- Database (Postgres + Drizzle)
- Docs, blog, dashboard and admin
- Invite delivery with retries
- Lifetime updates
Frequently asked questions
Here are some of the most frequently asked questions. If you have any other questions, feel free to reach out by email.
What do I get with this boilerplate?
Permanent read access to this repository. It is a pnpm workspace holding a TanStack Start web app, an Express 5 api, and a shared package with the wire contract and the Drizzle schema, with Clerk for identity, Stripe for billing, Postgres for storage and Resend for mail already wired together. The site you are reading is that repo, running.
How do I start a project with this boilerplate?
Clone it, point the origin at your own repo, and follow SETUP.md. It is a guide an agent can execute rather than a checklist that gates the build: every step reports rather than enforces, so you reach a running app before you have configured Stripe.
Is there a subscription, or does it expire?
Neither. It is one payment, and repository access is never revoked. Updates to the boilerplate land in the same repo, so they arrive as a pull rather than as a new download.
Can I sell one-time purchases and subscriptions at the same time?
Yes, and that is why billing is hand-rolled on Stripe rather than delegated to a billing product. Offers stack instead of replacing each other, and what someone is entitled to is derived from the price they actually paid. There is no field anywhere that says what a user bought.
What happens when a Stripe webhook is delivered twice?
The handler re-fetches the Stripe object and upserts its current state, so a replay does not create another payment row. Missed events and concurrent refreshes can still leave state stale until another refresh.
Can I use my own database, auth provider or email service?
Yes. Each one is behind a seam the docs name, and the Extending section walks the swap. Database and email changes stay in the api. Replacing Clerk also requires updating the web sign-in flow and session checks.
Stop wasting time on setting up login and payments
Buy once, clone it, and keep the repository.