Upgrade when the business layer becomes the bottleneck

Starter Free helps you validate the product surface.

Starter Pro helps you wire the product for real users, real billing, and a stronger path to launch.

Starter Free is the right choice when you want to move quickly on:

• routes
• screens
• UX states
• product structure
• interface credibility

Starter Pro becomes the right choice when your bottleneck is no longer the surface, but the business layer:

• authentication
• billing
• protected routes
• backend contracts
• production setup

You can stay on Starter Free as long as you want.

Upgrade when your product needs real wiring, not more mock structure.

What this page helps you decide

• when Starter Free is enough
• when Starter Pro becomes the better choice
• what Starter Pro adds
• how migration works
• why the upgrade is about leverage, not lock-in

The simple mental model

Starter Free validates the product. Starter Pro prepares the product for users, billing, and growth.

That is the core difference.

Starter Free is not incomplete by accident.

It is intentionally focused on product-shaped validation.

Starter Pro is not “more screens”.

It is the layer that removes the engineering work that usually delays launch.

When should you upgrade?

Upgrade when you start needing real infrastructure.

You likely need Starter Pro when your product requires:

• real user authentication
• session protection
• email verification
• password reset and password change flows
• Google and GitHub OAuth
• Stripe Checkout
• billing portal access
• invoices and subscription state
• protected app foundations
• plan-aware product behavior
• production data flows
• backend contracts and scalable app structure

Starter Free gives you the surface.

Starter Pro gives you the wiring.

A more practical rule

Stay on Starter Free when your current question is:

“What should the product feel like?”

Move to Starter Pro when your current question becomes:

“How do I launch this without spending weeks wiring auth and billing?”

That is usually the point where the upgrade starts paying for itself.

Free vs Starter Pro

What Starter Pro adds

Real authentication

Starter Pro adds the layer that turns auth UX into a real product system.

Typical additions include:

• credentials authentication
• Google OAuth
• GitHub OAuth
• email verification
• forgot password
• reset password
• password change
• connected accounts handling
• safer provider disconnect rules
• rate limiting foundations

This is usually one of the biggest time and risk sinks in a real SaaS launch.

Real billing

Starter Pro adds monetization foundations that Starter Free intentionally leaves mocked.

Typical additions include:

• Stripe Checkout
• billing portal flow
• subscription lifecycle handling
• invoices
• webhook synchronization
• plan-aware product behavior

This is the layer that helps the product move from “good-looking app” to “something you can actually charge for”.

Stronger protected app structure

Starter Pro is not only about integrating providers.

It also adds stronger foundations for:

• protected routes
• billing-aware areas
• settings foundations
• clearer domain boundaries
• production-shaped app structure

That matters because many products do not fail at the design layer.

They fail when the architecture becomes fragile during launch.

A shorter path to revenue

The real value of Starter Pro is not “more code”.

The value is removing repeated work in the areas that most often block shipping:

• auth
• billing
• protection
• state synchronization
• production setup

That is why the upgrade is fundamentally a time-to-revenue decision.

What you keep when you upgrade

Upgrading is designed to be incremental, not destructive.

You keep your:

• routes
• pages
• components
• layout structure
• design system usage
• product surface

You do not need to throw away what you built with Starter Free.

The goal is to preserve the product-facing layer and upgrade the wiring underneath it.

What changes when you upgrade

You progressively replace:

• mock auth → real authentication
• mock billing → real Stripe billing
• mock data → real data layer
• mock access states → protected routes and sessions

The interface does not need to be reinvented.

The business layer becomes real.

Typical upgrade flow

Most projects upgrade in an order like this:

1. add authentication provider
2. add session protection
3. introduce the database layer
4. wire billing and subscriptions
5. replace mock data progressively
6. tighten protected product behavior

This happens feature by feature, not all at once.

That matters because it keeps migration realistic.

Why not wire everything yourself?

You absolutely can.

Starter Pro is not trying to replace engineering judgment.

It exists to reduce the cost of repeated implementation work in areas that are:

• time-consuming
• risk-sensitive
• easy to get partially wrong
• often required before revenue

So the question is not:

“Can I build this myself?”

The better question is:

“Is rebuilding this the best use of my time right now?”

For many products, the honest answer is no.

Common concerns

“Will I lose my changes?”

No.

Starter Free and Starter Pro are part of the same product path.

Your routes, pages, components, and interface structure remain useful.

The point is to preserve your surface and improve the wiring.

“Can I upgrade later?”

Yes.

Starter Free has no lock-in.

You can stay there as long as your product is still in the validation phase.

Upgrade when real auth, billing, and production foundations become necessary.

“Do I need to migrate everything at once?”

No.

Migration is incremental.

A common path is:

• auth first
• protected routes second
• billing after that
• data layer progressively

You can move in layers.

“Is Starter Pro meant for real commercial SaaS products?”

Yes.

Starter Pro is designed to become the base of a real product, not just a demo repository or UI showcase.

That is the point of the upgrade.

“Why not stay on Starter Free forever?”

You can.

But once your product needs:

• real users
• real sessions
• real billing
• real protection
• real launch confidence

then the cost of staying on a mocked foundation usually becomes higher than the cost of upgrading.

How to decide today

Use this rule:

Stay on Starter Free if:

• you are still shaping the product
• you want to validate interface credibility
• you want to test layout, navigation, and core flows
• backend work would slow learning down

Move to Starter Pro if:

• you are serious about launching
• auth and billing are now the blocker
• you want a stronger production baseline
• you want less uncertainty between product and revenue

Recommended next step

If you are still exploring the product, keep building with Starter Free.

If the business layer is now the thing slowing you down, move to Starter Pro.

The product path is designed to make that transition feel natural:

validate first, wire later, launch stronger.