It's a boilerplate, but built for a different goal. Most starters optimise the first demo; CleanFrame optimises the tenth feature — one set of conventions, strict types and documented placement, so the codebase stays reviewable as it grows.

Not really. It assumes you're comfortable with TypeScript, React and shipping real apps. If you're still learning the basics, a tutorial will serve you better. If you deliver client work and want to stop rebuilding the same foundation, it's for you.

No. The AWS decisions — Amplify Hosting, CDK resources, Cognito, caching — are already made and wired. You deploy on them and pick up the pieces you need as you go. Deeper AWS knowledge helps later, but it isn't required to ship.

Those are strong for launching a SaaS fast, often around a specific stack. CleanFrame targets a different buyer: freelancers and studios delivering serious B2B apps on Next.js + AWS, where maintainability across many features matters more than a five-minute launch. Pick the one that matches how you actually ship.

You can generate a first version with AI — but without enforced conventions, AI multiplies patterns instead of following one, and the repo degrades fast. CleanFrame is the opposite: a fixed structure and written rules that keep AI-assisted work consistent. That's what makes AI faster here, not messier.

Yes. Solo covers client work for a single developer; Studio covers unlimited client projects across a team, with reuse rights between projects. See the license tiers for the exact terms.

One seat, full source code, commercial use for your own products, client work for a solo developer, unlimited personal projects, 12 months of updates, basic support, and lifetime access to the version you purchased.

Up to five seats, full source code, unlimited client projects, commercial client work, reuse rights across client projects, 12 months of updates, priority support, and lifetime access to the version you purchased.

Your license doesn't expire. You keep lifetime access to everything released during your update window, and the app keeps working. After 12 months you simply stop receiving new updates — a renewal may be offered, but nothing you already have is taken away.

A tagged snapshot of the codebase at the version you purchase, plus 12 months of subsequent updates. Final delivery details are confirmed at checkout; during early access, scoping is handled manually via /contact.

Yes. Billing providers sit behind one interface and are gated by feature flags. Run Stripe only, Paddle only, both, or remove billing entirely — the rest of the app doesn't depend on a specific provider.

The backend is built for AWS (Amplify + CDK), so that's where it runs best. But it's your AWS account and your source code — no proprietary platform sits between you and it. Moving parts off AWS is work, not a locked door.

Because this is a source-code product, purchases are final once repository access has been granted — there's no blanket money-back guarantee. Before buying, inspect the live demo, the walkthrough, the docs and the feature list, and ask any pre-sales question. Exceptional cases may be reviewed manually at our discretion.

Yes — the boilerplate ships with a password reset flow. Adapt this answer to match your support process.

Point users to the contact form or your configured support channel.

Describe the feature availability for each of your plans here.

Yes — buyers can change plan from the account billing screen. Proration follows your billing provider's rules.

Refund policy is set by you. Describe yours in this answer.

Yes — yearly billing is supported and automatically applies the savings configured on each plan's yearly price.

Describe your project creation flow in this answer.

Team invitations are supported. Describe your invite flow and available roles here.