Legal Pages Work Better as Typed MDX
Policies become easier to maintain when dates, product names, and domains come from config instead of hard-coded prose.
mdxcontent
1 min read
Cloudflare-first SaaS starter
Ship a structured SaaS site on Cloudflare without turning it into a throwaway demo.
FlyStart gives you a configuration-first Astro + React foundation with shared UI, Better Auth, D1, legal pages, and content collections already wired for launch.
Astro 6 • React 19 • Better Auth • D1 • Shared UI
Built for fast launches with cleaner shared boundaries in FlyStart
Build Notes & Launch Guides
Practical notes on runtime boundaries, content collections, legal pages, and keeping a shared UI package reusable.
Ship Faster with a Real Runtime Boundary
Why this starter keeps Drizzle, auth, and Cloudflare bindings inside packages/core.
runtimecloudflare
1 min read
Content-First SaaS Front Doors
Astro collections give the public site a typed content system without custom build glue.
astrocontent
1 min read
Simple, Transparent Pricing
Choose the credit flow that works for you. Subscriptions renew access monthly, and annual billing lowers the monthly price.
Starter Monthly
300 credits each month for early-stage launch work.
$29/month
300 credits every month
Billed monthly
Hosted checkout through enabled providers
Most Popular
Prod Monthly
1,200 credits each month for active teams shipping weekly.
$79/month
1200 credits every month
Billed monthly
Hosted checkout through enabled providers
Credit Refills
One-time packs stay available alongside any active subscription.
Launch Credits
200 credits · $19 one-time
Frequently Asked Questions
The quick answers behind FlyStart: what it is, who it is for, and how much starter work it removes.
What is FlyStart?
FlyStart is a sample Cloudflare-first SaaS entry site built with Astro and React. It demonstrates how shared UI, services, runtime wiring, and site-specific configuration can live together without collapsing into a single app layer.
Who is it built for?
It is aimed at developers and teams who need to launch a SaaS site quickly while still keeping a clean monorepo structure, reusable packages, and room for future features.
What comes out of the box?
The starter already includes shared UI packages, Better Auth integration, D1-ready data access, content collections for blog and legal pages, and a configuration-first way to shape each site.
Does it only work for full SaaS apps?
No. You can use it as a marketing site, a docs-adjacent entry site, or the front door of a larger product. Feature flags let you keep only the pieces you need.
Can I reuse these blocks across other sites in the repo?
Yes. That is the point of extracting them into @fly/ui while keeping the actual copy and links in the site directory. The shared blocks stay reusable while each site keeps its own content.
Why keep this content under src/site?
Because this content belongs to fly-start itself rather than to the shared workspace. Keeping it under the app site directory makes ownership clearer and keeps template-level edits concentrated in one place.