Questions
Why a merchant of record instead of a plain payment processor?
Because with a plain processor you are the seller, which means you are the one who owes VAT in every country your customers live in — and the EU charges it on digital goods from the first euro, with no threshold. With a merchant of record, they are the legal seller and that obligation is theirs. You pay a higher percentage and you stop thinking about tax registration. If you would rather use a plain processor, the billing code is one file and one route: swap it.
Is there a demo?
The starter is itself a running app: the signup, dashboard, pricing and billing pages you get are the ones described here. Buy it, run npm run dev, and you are looking at the demo on localhost in about five minutes.
Does it use TypeScript?
No. Plain JavaScript with JSDoc where a type helps. Adding TypeScript on top is straightforward if you want it; taking a build step out of a starter kit is not.
Does it use React?
No. Server-rendered HTML from functions that return strings. If your product needs a rich client, add one to the pages that need it — nothing here stops you.
What database?
PostgreSQL, through the pure-JavaScript pg driver, so npm install never compiles anything. Neon, Supabase, Railway and RDS all work, as does one you run yourself.
Can I use it for client work?
Yes. Build as many end products as you like, for yourself or for clients. What you cannot do is redistribute the kit itself as a starter kit, template or course material. Sell what you build with it, not the thing itself.
Do I get updates?
Yes, for the version line you bought, at no extra cost.
What if it is not for me?
Fourteen days, no questions asked. Email support and the refund is issued. You keep nothing but the lesson, and we do not ask you to prove anything.
Something not answered here? Ask.