Upgrade to Starter Pro
Compare browser-local Starter Free workflows with configurable Starter Pro foundations, and plan a deliberate move without an automatic migration.
OverviewLink to section
Starter Free helps you validate the product surface.
Starter Pro provides configurable authentication, billing, and database foundations.
Free already lets you create a project, view its details, rename it, and delete
it. Projects persist in this browser's localStorage when storage is available.
Use Reset demo to restore the sample projects after confirmation. This is a
local project workflow, not a connected multi-user application: there is no real
account, shared database, authorization, or cross-device synchronization.
Use sample data, not sensitive information. Clearing browser storage removes your changes. If storage is unavailable, changes last for the current visit only and the app displays a notice. Project status, member counts, update labels, and dashboard metrics remain illustrative. Try the Starter Free getting-started guide before deciding whether you need server-backed foundations.
Upgrade when the blocker is no longer the UI, but the production wiring behind it:
- real authentication
- protected routes
- Stripe Checkout
- billing portal
- webhook-driven billing state
- backend-ready product structure
Separate source, not a demo unlock
Starter Pro is separate source code to download, configure, and adapt. Buying Pro does not unlock the running Free demo or automatically migrate your app or local projects. It does not provision your services or deploy your app. You still implement your own domain data model, permissions, and workflows.
Keep your UI direction. Build on connected foundations.
One-time payment · Instant access after purchase
Simple rule
Keep Free for local product validation. Choose Pro when configurable server-backed foundations are the next useful step.
The upgrade momentLink to section
Starter Free is the right choice when your question is:
What should the product feel like?
Starter Pro becomes relevant when your question becomes:
How do I build on existing auth, billing, and database foundations?
The decision is about integration depth, not whether Free can save a local project. Compare the included scope with what your product needs; configuration and validation still belong to you.
What changes with ProLink to section
Real auth
Real billing
Protected foundation
Free vs ProLink to section
| Capability | Starter Free | Starter Pro |
|---|---|---|
| Product-shaped UI surfaces | Included, with a local project workflow | Included, with integration foundations |
| Auth screens and UX states | Mocked | Included; configure and validate auth |
| Email and password auth | Mocked | Included; configure and validate |
| Google and GitHub OAuth | Not included | Included; configure provider apps |
| Email verification | Not included | Included; configure email delivery |
| Password reset and change | Mocked | Included; configure and validate |
| Stripe Checkout | UI only | Included; configure and test Stripe |
| Billing portal | UI only | Included; configure and test Stripe |
| Webhook sync | Not included | Included; configure and test endpoints |
| Invoices and subscriptions | Mocked | Stripe-backed foundations to configure |
| Protected app foundations | No real authorization | Server-side guards to configure and extend |
| Data layer | Browser-local projects in localStorage; no shared database | Prisma + PostgreSQL foundations; implement your domain model |
| Best use case | Validate UI and local workflows | Build on configurable SaaS foundations |
Free to validate. Pro for connected foundations.
Local persistence is useful for a demo. Accounts, shared data, authorization, and payments require server-backed behavior. Pro supplies foundations, not a finished implementation of your product.
When to upgradeLink to section
Stay on Free while validating
- you are shaping the product
- you are validating UX
- you are changing the domain model
- you are preparing a demo
- you are exploring positioning
Move to Pro when launch wiring becomes the blocker
- real users
- real sessions
- real payments
- protected routes
- plan-aware product behavior
- backend-backed data
- production validation
What you keepLink to section
You can reuse your product direction and selected UI work, but there is no automatic in-place upgrade. Keep your Free source under version control before starting and work with the Pro source in a separate directory or repository.
Review what is useful to bring across:
- routes and pages
- components and layouts
- design-system customizations
- product copy and interaction decisions
Port one small UI slice at a time. Compare the actual imports, layouts, public APIs, and versions in your downloaded release rather than overwriting Pro's configured authentication or billing foundations with demo code.
Replace or implement deliberately:
- mock auth → configured real authentication
- mock billing → configured and tested Stripe integration
- mock access → server-side checks and product-specific permissions
- browser-local project data → your own domain model and server-backed workflows
Preserve your Free work
Your original Free source remains your reference. Local demo records are not imported into Pro automatically. Any data transfer needs an explicit mapping, validation, and authorization design that you implement; no migration command or automatic transfer is provided by this guide.
Upgrade flowLink to section
Preserve Free and inspect the Pro sourceLink to section
Save your Free work under version control. After purchase, use the claim email to download and unzip Starter Pro into a separate directory. Read its README and compare the delivered versions before adapting your UI. Follow delivery and Getting started for access and setup.
Configure and validate locallyLink to section
Follow the downloaded release instructions for Node.js, pnpm, dependencies, a local PostgreSQL database, and environment variables. Configure the providers you intend to exercise using the environment guide. Keep secrets private and use local development or test services, not production data. Confirm the baseline runs before porting a product-specific UI slice.
Add authenticationLink to section
Use Pro's included auth foundation instead of copying Free's mock behavior. Configure credentials, email, and the OAuth providers you need, then verify sign-in and session behavior with the auth guide. A rendered login screen is not proof that authentication works.
Protect product routesLink to section
Bring across one reviewed page or component at a time. Keep Pro's existing guards and add server-side permissions appropriate to your domain. Validate both allowed and denied access; hiding a link in the UI is not authorization.
Connect billingLink to section
Configure the included Stripe Checkout, portal, and webhook foundations. Follow billing testing in test mode and check resulting billing state, not just whether the billing page renders. The purchase of Starter Pro does not configure your own Stripe account.
Replace mock dataLink to section
Define your own project or domain model, persistence, validation, permissions, and workflows. Pro's Prisma/PostgreSQL foundations do not automatically turn Free's local projects into shared records. Treat any data transfer as a separate, explicitly designed implementation; do not point demo code at a production database or assume browser data is trusted.
After each ported slice, run the release's applicable checks and keep the last working version available for rollback. Record unconfigured integrations as unverified. Complete the production checklist before deployment; a successful local run is not production approval.
Why not build it yourself?Link to section
You can keep Free and implement the integrations yourself.
Compare that work with adopting and configuring Pro's included foundations:
- authentication
- Stripe billing
- webhook handling
- route protection
- billing-state synchronization
- database and production setup
Neither choice removes your responsibility for product logic, validation, deployment, or operation. Choose the path that fits your actual requirements; this guide does not establish a measured time or revenue saving.
An integration-depth decision
Pro is useful when its included foundations match work you would otherwise implement. Review what ships and what still needs configuration before buying.
Decision guideLink to section
Keep validating the product surface
- you are still shaping the product
- you need a credible demo
- you are validating UX and navigation
- backend work would slow learning
- payments are not required yet
Build on connected foundations
- you are preparing a connected product
- auth is becoming a blocker
- Stripe must charge customers
- routes need protection
- billing state must control access
Common concernsLink to section
Ready to move faster?Link to section
If you are still exploring, stay on Starter Free. If connected foundations are your next need, review the Pro scope and setup responsibilities before buying.
Choose the foundations your product needs.
One-time payment · Instant access after purchase