See the path.
Before you buy the kit.

Your account checklist.

The starter is source code you run in your own accounts. Use Node.js 22 and a coding agent or terminal. GitHub, Supabase, Stripe and hosting accounts are required for the full path.

• GitHub Receive and clone the repository.
• Supabase Create a project for your database and authentication.
• Stripe test mode Configure test subscriptions, checkout and webhooks.
• Vercel Deploy your application with the included guide.
• Resend (optional) Verify a domain for transactional email.

Provider pricing, commercial-use eligibility and account approval are separate from the kit. Review each provider's current terms before choosing a plan. A custom domain and production email setup add their own steps.

One place to begin.

Open your copy of the repository in your coding agent. The included AGENT_DEPLOY.md is the detailed runbook, with provider-specific instructions and verification steps.

Read AGENTS.md and AGENT_DEPLOY.md before changing this repository. Help me configure and deploy the subscription-first starter using the documented path. Start with npm run setup:init, then npm run setup:check. Tell me which provider pages to open and which settings I must supply locally. Never print, record or send my secret keys in chat. Follow AGENT_DEPLOY.md for the complete node scripts/setup-stripe.mjs command, including the required --site-url, --name, --monthly and --yearly options. Use my test deployment URL and agreed app subscription prices, then preview the command without --apply-test. Do not create anything until I explicitly authorize the test-mode --apply-test step. Use test payments first. Stop for account approvals, new permissions, paid resources and live payment activation. Check configuration, run the documented tests and build, then verify signup and a test checkout on the deployed URL. Report any unverified steps honestly. Do not remove tests or weaken security to make checks pass.

Set it up.
Check what's missing.

Install dependencies, create your local configuration, and run the checker. Fresh setup selects a personal subscription app; advanced usage credits and organizations can be enabled later.

npm ci
npm run setup:init
npm run setup:check

Supply the values requested by the runbook in your local environment file and hosting settings. Keep secret keys out of chat, screenshots and git. The checker reports configuration issues; it is not proof that a payment has succeeded.

Preview before creating.

The Stripe helper defaults to a dry run. Review the proposed test configuration first. Its apply option is test-mode only; it does not activate live payments.

node scripts/setup-stripe.mjs --site-url https://your-test-app.example --name "My app" --monthly 1900 --yearly 19000
# After reviewing and authorizing the test setup:
node scripts/setup-stripe.mjs --site-url https://your-test-app.example --name "My app" --monthly 1900 --yearly 19000 --apply-test

Replace the example URL and app name with your test deployment. The amounts are your app's subscription prices in the smallest currency unit: 1900 means $19 in the default USD currency. They are separate from the LedgerStack purchase price.

Your agent must follow the helper's output and the runbook for the required settings, products and webhook configuration. Never substitute a live secret key to get a test step to pass.

A URL is the start.
Check the whole flow.

Follow docs/DEPLOY-VERCEL.md: apply migrations, configure the hosting environment, deploy, then set the auth redirects and Stripe webhook for your deployed URL. A Render guide is also included.

• Run the documented tests and production build.
• Create an account on the deployed app and finish email confirmation if enabled.
• Check that the session reaches the dashboard and protected pages stay protected.
• Complete a Stripe test checkout and confirm the webhook updates the subscription.
• Open the customer portal and verify the relevant billing state.

Account approvals, DNS, email delivery and provider setup vary. Keep any failed or untested step clearly marked until it is verified.