[P.01]MULTI-WEEK
Authentication is a rabbit hole
Login, OAuth, 2FA, verification, password recovery, session handling, and account security arrive before product work.
System readyTarget: Cloudflare WorkersProduct: Saavo Starter
// Saavo / Cloudflare SaaS starter kit
SaavoCloudflare SaaS Starter Kit
Build and ship SaaS on Cloudflare without rebuilding the foundation.
Saavo Starter is a production-oriented TypeScript SaaS boilerplate for Cloudflare Workers. More than a UI template, it connects authentication, Stripe billing, access control, admin operations, documentation, and deployment infrastructure in one codebase you can own and extend.
Built-in capabilities
Authentication
Billing
Access Control
OAuth 2.0
i18n
Docs
Saavo CLI / createv0.1.0
$ npx saavo-cli@latest create my-saas
Preflight: checking Node.js
Node.js 24.16.0
Preflight: checking npm
npm 11.13.0
Preflight: checking Saavo access
Saavo access: Builder (builder@example.com)
Requesting Saavo Default Template 0.2.9
Downloading and verifying template archive
Extracting template
Applying project name
Preparing local development
Project is ready for local development
Created my-saas from Saavo Default Template 0.2.9.
OAuth 2.0 / PKCESHA-256 verified
FIG.01Saavo CLI project creation flow
Cloudflare Workers SaaS stack / config driven
// Section_01 :: Problem statement
A SaaS boilerplate should remove the work users never see.
Authentication, Stripe billing, authorization, account operations, and Cloudflare infrastructure are essential to a serious SaaS product. They are also the repeated groundwork your customers will never pay for directly.
[P.02]HIGH-RISK
Payment is not access control
Checkout is only the first step. Products, entitlements, grants, revocation, and audit history still need a coherent lifecycle.
[P.03]REPEATED
Operations need real screens
Users, payments, Reaction executions, OAuth clients, tickets, and logs all need usable administrative workflows from day one.
[P.04]CONFIG-HEAVY
Cloud infrastructure needs glue
D1, KV, R2, Queues, Durable Objects, scheduled tasks, email, and deploy configuration must work as one system.
FIG.02 / Starting point comparison
FROM SCRATCH
Build the reusable foundation, then build the product.
WITH SAAVO
Configure the SaaS starter kit, then build what makes the product yours.
// Section_02 :: Module inventory
A full-stack SaaS starter kit. 16 working modules.
Start with working identity, commerce, access, operations, content, and Cloudflare services. This is more than a dashboard template or a collection of disconnected UI blocks.
[M.01]
Authentication
Email and OAuth login, verification, password reset, TOTP 2FA, recovery codes, secure sessions, Google One Tap, login modal, and account deletion.
signup / login
Google OAuth
GitHub OAuth
One Tap
TOTP 2FA
recovery codes
password reset
email verify
sessions
account security
[M.02]
Billing & Stripe
Checkout, verified webhooks, purchases, subscriptions, billing portal, promo codes, and automatic tax.
[M.03]
Access Control
Roles, boolean entitlements, grants, revocation, and event history.
[M.04]
Reaction Engine
Typed Events trigger durable, observable Commands with retry behavior.
[M.05]
Admin Dashboard
Operational pages for users, commerce, access, Reaction, notifications, affiliates, tickets, analytics, and logs.
[M.06]
OAuth2 Server
Authorization code, PKCE, scopes, consent, token, and revocation flows.
[M.07]
Internationalization
Typed locale routing, translation loading, cookies, and RTL support.
[M.08]
Docs & Content
Documentation, content collections, sitemap, metadata, and structured data.
[M.09]
KV & R2 Storage
Storage backends, public delivery, cache policy, TTL, and size constraints.
[M.10]
Email System
Cloudflare Email and Resend providers behind typed delivery services.
[M.11]
Support Tickets
Create, reply, filter, prioritize, resolve, and close support tickets.
[M.12]
Logging & Audit
System, audit, and alert logs with asynchronous persistence.
[M.13]
Security
CSRF, Turnstile hooks, rate limits, trusted origins, and sanitization.
[M.14]
In-App Notifications
Publish rich-content messages to all or selected users, track reads, and surface unread account indicators.
[M.15]
Affiliate Program
Referral attribution, commission tracking, payout profiles, monthly settlement, and admin operations.
[M.16]
Config System
Typed ownership for products, access, Reaction behavior, menus, and runtime settings.
// Section_03 :: System architecture
Clear boundaries. Code you can own.
The TypeScript SaaS boilerplate keeps product behavior above the reusable foundation, while typed UI and API contracts keep Cloudflare platform details in the proper layer.
FIG.03 / dependency direction / top-down
LAYER_01 / YOUR PRODUCT
Your business behavior stays above the reusable SaaS foundation.
business-logic/custom-modules/branding/config/
LAYER_02 / SAAVO STARTER
Implemented SaaS modules with clear configuration and ownership.
authbillingaccessreactionadminoauth2notificationsaffiliatedocsstorage
LAYER_03 / FRONTEND & API
SSR, hydrated islands, typed APIs, and service boundaries.
React 19ViteHonoTailwindNanostoresshadcn
LAYER_04 / CLOUDFLARE PLATFORM
Global edge runtime with first-party storage and async primitives.
WorkersD1KVR2QueuesDurable ObjectsCronEmail
ENTRY / fetch + queue + scheduled
DEPLOY / wrangler deploy
SCALE / Workers managed
SETUP / bindings + secrets
// Section_04 :: Payment to access lifecycle
From checkout to access. Traceable end to end.
A verified one-time payment maps its Stripe Price to the Starter license, triggers an idempotent Reaction Command, and grants the configured account entitlement.
FIG.04 / forward lifecycle
Owner
Product configuration
Input
Product ID + Plan ID
Output
One-time plan and declared access
Source
config/products.ts
Configuration stays close to the product
Products, Reaction Events and Commands, and access checks stay visible and typed instead of disappearing into provider-specific glue code.
RuntimeWorkers
ContractTyped
AccessExplicit
saavo_starter: {
plans: {
license: {
type: 'one-time',
access: {
entitlements: [{
target: 'starter_download',
config: { kind: 'boolean' }
}]
}
}
}
}// Section_05 :: Development lifecycle
Configure the starter kit. Build what differentiates you.
Set your brand, providers, products, Cloudflare bindings, and secrets; then spend the rest of the development cycle on product behavior instead of rebuilding SaaS infrastructure.
01
CONFIGURE
Set brand, providers, products, bindings, and secrets.
02
MIGRATE
Create the required D1 databases and apply the included migrations.
03
BUILD
Add the product behavior that makes your SaaS unique.
04
VERIFY
Run type checks, tests, and production builds before release.
05
DEPLOY
Provision bindings and deploy the application to Workers.
// Section_06 :: Admin operations
Operate from day one. Not after launch.
The included admin dashboard is not a static SaaS template. Search users, inspect purchases and access, review Reaction executions, manage OAuth clients, process support, and trace operational logs.
DashboardOverviewINTERACTIVE PREVIEW · DEMO DATA
Overview
A live operational summary across users, billing, support, reliability, and analytics.
Users
Account growth and provider mix
Total users
1,284
+36 this week
Today registrations
9
+2 from yesterday
Google67%
GitHub22%
Email11%
Subscriptions
Recurring billing state
Active
42
Current access
Trialing
3
In trial
Canceled
2
Ended
Scheduled cancel
1
At period end
Tickets
Support workload
Pending
7
Needs review
Over 24h
1
Needs attention
Today
4
New tickets
This week
18
Total created
Traffic overview
Analytics summary for the selected range
Pageviews
18,420
+12.8%
Visitors
7,804
+8.4%
Visits
9,210
+9.1%
Bounce rate
38.2%
-2.7%
Top pages
Most viewed routes
1. /6,842
2. /pricing4,631
3. /docs2,816
This public preview mirrors the dashboard’s real navigation, page hierarchy, fields, and interaction patterns. Records shown here are illustrative only.
// Section_07 :: Comparative analysis
Use a SaaS boilerplate. Keep the product engineering.
Saavo does not replace engineering judgment. It gives your team a stronger starting line by connecting the systems a commercial SaaS still needs, while leaving the source code open to change.
FROM SCRATCHINFRA FIRST
Design identity and session flows
Wire checkout and verified webhooks
Create roles and entitlement semantics
Build admin resource operations
Add retryable Event and Command processing
Harden Cloudflare runtime boundaries
WITH SAAVO STARTERPRODUCT FIRST
Configure included auth providers
Connect products and payment provider
Declare access and Reaction behavior
Extend existing operational pages
Build only product-specific modules
Deploy on the included Cloudflare model
// Section_08 :: Target builders
A Cloudflare SaaS starter kit for builders who own the code.
Saavo is a practical fit for developers and small teams that want a production-minded foundation, full source ownership, and a codebase they can continue extending after launch.
[A.01]
Indie Hackers
Solo developers who want a serious starting point without giving up source-code ownership.
[A.02]
AI SaaS Founders
Teams that need authentication, billing, access, and operations around an AI product.
[A.03]
API Product Teams
Builders creating scoped APIs, OAuth integrations, and developer-facing products.
[A.04]
Small Teams
Compact teams that need a Cloudflare SaaS starter kit instead of another infrastructure sprint.
Suitable forMicro SaaSAI SaaSAPI productsDeveloper toolsB2B dashboardsInternal platforms
// Section_09 :: Builder feedback
A starter codebase people can understand and extend.
Builders value the connected system more than a long feature checklist: visible architecture, complete workflows, and fewer infrastructure decisions between a SaaS idea and a working launch.
“The useful part is not any single feature—it is that authentication, payments, access, and operations already share one coherent application model.”
AR
Alex Rivera
Independent SaaS builder
Cloudflare product prototype
“I can follow the payment-to-entitlement path through real services and contracts. That makes the foundation much easier to trust and extend.”
MK
Morgan Chen
Full-stack developer
Starter architecture review
“The dashboard covers the operational work that starter kits usually leave for later: users, access, purchases, retries, support, and logs.”
JL
Jordan Lee
Product engineer
Admin workflow evaluation
“The layer boundaries make it clear where business rules, persistence, APIs, and UI belong. I would not need to reverse-engineer the whole project before changing it.”
CN
Casey Novak
Backend engineer
Architecture walkthrough
“Most starters get you to a polished landing page. This one is focused on the less visible systems that determine whether the product can actually operate.”
ST
Samira Patel
Indie hacker
New product planning
Your note
Your experience could be next.
Building with Saavo Starter? Share what you are creating, what saved time, or what you would improve.
// Section_10 :: Starter license
Get the Saavo SaaS Starter Kit
One-time purchaseNo recurring feesNo trial
Buy Saavo Starter once and get entitlement-backed access to the full TypeScript SaaS boilerplate for Cloudflare Workers.
[LICENSE_01]Introductory price
Saavo Starter
Pay once to unlock the complete Cloudflare SaaS starter kit. No subscription or trial.
- Download the complete Saavo Starter codebase
- Connected auth, billing, access, dashboard, and documentation
- One-time payment with no recurring charges
Payment specification
$169.00 one-time
$199.00Save $30.00 · 15% off
Billing modeOne time
DeliveryStarter entitlement
AccessReady after payment
Documentation
Setup, architecture, and extension guidance
Account Access
Entitlement-backed delivery after payment
Source Ownership
Understand, modify, and extend the code
Secure Payment
Verified provider-hosted checkout
// Section_11 :: Frequently asked
Questions, answered.
Saavo Starter is best described as a Cloudflare SaaS starter kit and TypeScript SaaS boilerplate. Unlike a UI-only SaaS template, it includes connected authentication, commerce, access control, Reaction Events and Commands, admin operations, OAuth2, support, logging, content, and Cloudflare bindings that you can configure and extend.
// Section_12 :: Build
Skip the repeated foundation work.
Start with your product.
Use a Cloudflare SaaS starter kit with the repeated systems already connected, keep full ownership of the code, and spend your next development cycle on the product customers actually buy.
One-time purchaseConfig-driven accessCloudflare-nativeFull source code