Question 1

What exactly do I get?

Accepted Answer

The full source code of SarvStack: TanStack Start app, Supabase auth + RLS patterns, one-time and subscription Polar billing wiring (with entitlements), a server-side AI module on the Lovable AI gateway with usage metering and quotas, transactional emails via Resend, a private-bucket file storage pattern (avatar upload with per-user RLS), a user_roles + SECURITY DEFINER pattern with a role-gated admin area, Playwright smoke tests with GitHub Actions CI, a trilingual UI (EN/DE/ES), the shadcn/ui design system, and the CLAUDE.md convention guide — delivered as access to a private GitHub repository.

Question 2

What's the license?

Accepted Answer

One license per developer. Use it in unlimited products of your own — commercial, client work, or side projects. Resale or redistribution of the source code is not permitted.

Question 3

How is delivery handled?

Accepted Answer

After purchase you receive a receipt from Polar with a link to your customer portal. Connect your GitHub account there and you'll be invited to the private SarvStack repository within seconds. Your license key is issued automatically.

Question 4

What is the license key for?

Accepted Answer

Your license key is your proof of purchase — one key per developer license. You don't need to activate anything: repo access is delivered separately via the GitHub invite. Keep the key for support requests, and if you build products that need license keys yourself, the same Polar API that issued yours can power them. You can try the live validator at /verify-license.

Question 5

Why Polar as merchant of record?

Accepted Answer

Polar is the legal seller on every transaction and handles VAT, sales tax, and remittance for you. As the buyer, you receive a proper invoice — no manual tax paperwork on either side.

Question 6

How do updates work?

Accepted Answer

Dependency refreshes and improvements ship roughly quarterly and are included with your license. You pull updates from the repository at your own pace.

Question 7

Does it work with AI coding agents?

Accepted Answer

Yes — that's a core feature. CLAUDE.md documents folder structure, naming, how to add routes, how auth works, and the RLS pattern, so Claude Code and Cursor can extend the codebase safely.

Question 8

Do I need any paid APIs?

Accepted Answer

No paid APIs are required for local development — the kit runs end-to-end without them. For production you'll want a Polar account (free to set up, Polar takes a small fee per sale as your merchant of record), an optional Resend API key if you want transactional emails to actually send (missing key = no-op, never crashes), and AI gateway usage billed via Lovable Cloud if you deploy there — or swap the model call to your own provider (OpenAI, Anthropic, etc.). All three are optional switches, not blockers.

Question 9

What's the refund policy?

Accepted Answer

Because you receive the full source code immediately, all sales are final. If something is broken, open an issue and we will fix it.

Question 10

How does support work?

Accepted Answer

Documentation first, then GitHub issues for bugs and questions. No SLA — this is a boilerplate, not a managed service.

Question 11

Can I add GitHub sign-in?

Accepted Answer

GitHub sign-in ships as a pattern for BYO-Supabase setups. Lovable Cloud's managed OAuth broker doesn't yet include GitHub, so the button is hidden by default. If you're using your own Supabase project, enable a GitHub OAuth app in Supabase Auth settings and pass `providers={['google', 'github']}` to the `OAuthButtons` component — the wiring is already in place.

Frequently asked questions