Getting access

Delivery is a private GitHub repository. There is no download link and no licence key, because the repository access is the licence: it is what gives you the code and what keeps giving you every update after.

There are two ways the invitation reaches you. Which one you see on the thank-you page depends on whether instant delivery is switched on for this deployment — if it is not, or anything about it fails, the 24-hour manual promise below still holds. Nothing on this site promises faster than that guarantee.

1. You pay

Checkout runs on Dodo Payments, which is the merchant of record for the sale. Card, currency and local tax are Dodo's side of the transaction. You do not create an account on this store, because this store does not have accounts.

2. Your receipt arrives

Dodo emails the receipt as soon as the charge clears, usually within a minute. It names the kit and the tier you bought. If it has not appeared after a few minutes, check spam before writing in.

3. Claim your invite

Instant, when it is switched on. Dodo redirects you back to this store's thank-you page after checkout. If a claim form is there, enter your GitHub username and submit it: the server re-verifies the payment with Dodo, then invites that username as a read-only collaborator on the kit repo. The invite typically lands in seconds. octocat, not github.com/octocat — use the username, not the profile URL.

Manual, always available. No form, no dashboard to log into. Reply to the receipt email, or write to abhimanpanwar6@gmail.com if the reply does not go through, with the GitHub username you want invited. On the Team tier, send up to five usernames in the same reply — the instant form only ever claims one seat per submission, so a team buyer sending the rest by email is normal, not a fallback for something broken.

4. The invitation arrives

Through the instant path: GitHub emails you the invitation immediately and it also appears at github.com/notifications. Accept it and the repository shows up in your account.

Through the manual path: a person reads the reply and sends the collaborator invitation by hand, normally well inside the promise but the promise itself is 24 hours, not a minute — fulfilment is manual outside the instant path, and promising faster than that everywhere would be the wrong way to run a store. GitHub emails the invitation the same way either path gets there, and it appears at github.com/notifications too.

5. First run

git clone git@github.com:<org>/kroszkit-web.git my-product
cd my-product
npm install
npm run setup        # copies .env.example -> .env.local, prints a checklist
npm run dev

Open http://localhost:3000. The site renders with nothing configured: no database, no Dodo account, no email provider. Every integration is off and nothing throws. That is deliberate, so you can read the code running in front of you before you sign up for anything.

Then fill in .env.local one section at a time. npm run setup prints the checklist, the dashboard renders a live version of it, and each variable you add turns its feature on by itself. Run npm run db:migrate once DATABASE_URL is set.

Two files are worth editing first: src/lib/site.ts for the brand, and src/lib/pricing.ts for your tiers. Between them they drive the header, footer, page titles, OG cards, sitemap, pricing table and checkout links.

Updates, for as long as the kit is maintained

Your invitation is to the live repository, so an update is a git pull. The usual setup is to keep the kit as a second remote on your own project:

git remote add kit git@github.com:<org>/kroszkit-web.git
git fetch kit
git merge kit/main        # or cherry-pick just what you want

Pull when you want what has landed since, and merge on your own schedule. If you have rewritten half of it by then, cherry-pick instead. Nobody minds.

There is no licence server, no renewal date and no subscription. Once you have the grant, you keep it.

If something goes wrong

Write to abhimanpanwar6@gmail.com.

• No receipt after ten minutes. Send the email address you paid with and the approximate time.
• The instant claim form errored. It falls back to the same 24-hour promise automatically: reply to your receipt with your GitHub username and it goes out by hand instead. No need to retry the form first.
• No invitation after 24 hours. Reply on the same thread rather than starting a new one, so the username is already in the history.
• The invitation expired. GitHub invitations lapse after seven days. Ask and it gets resent.
• A bug in the kit. Report it. Bugs in the kit itself get fixed, and the fix reaches you the same way everything else does.
• Wrong tier, or you need more seats. Say what you meant to buy. It is easier to fix before you have five people cloning it.

Refunds

Dodo is the merchant of record, so refunds run through Dodo rather than through us. Write to abhimanpanwar6@gmail.com first, though: most refund requests turn out to be something broken or unclear in the kit, and those are worth fixing for everyone.