home/store/Crypto SaaS Starter Kit

Crypto SaaS Starter Kit

The exact Next.js + Supabase + crypto-payments stack behind degenjournal.xyz — extracted, cleaned, MIT-licensed.

I built degenjournal.xyz — a crypto trading journal with magic-link auth, crypto checkout, and read-only on-chain wallet imports — and kept hitting the same wall every crypto SaaS hits: the boring 30% of plumbing that every project needs and no boilerplate does well for crypto specifically.

So I extracted it. This is the real auth, payment, and wallet-reading code that runs in production at degenjournal.xyz — genericised, documented, and MIT-licensed. Not a toy. Not AI-generated filler. The actual stack, proven by a live app you can go use right now.

$29$49launch price · first 30 days

One payment. MIT public repo + private Pro repo access (auto-invite to your GitHub) + the 40-page guide.

checkout opening soon

Living proof: degenjournal.xyz is built on this exact stack.

What's included — public MIT repo

Free and open. The $29 adds the Pro repo + guide below.

✓ Supabase magic-link auth

Passwordless email auth via @supabase/ssr — server client, browser client, middleware session refresh, and the /auth/callback exchange. Sign-in/out wired end to end.

✓ Plan-gated routes pattern

A clean free/pro/lifetime entitlements model: a single source-of-truth entitlements map, a server-side requirePro() guard, a <ProGate> client component, and a /api/account/plan endpoint.

✓ NowPayments crypto checkout

Hosted crypto checkout (USDC/SOL/ETH/BTC) — invoice creation lib, a per-plan checkout route, and an IPN webhook that verifies the HMAC signature before granting access.

✓ Helius Solana wallet read

Read-only Solana wallet reader — paste any address, pull its swap history from Helius. No wallet connection, no private keys, never touches funds.

✓ Hyperliquid wallet read

Read-only Hyperliquid perp reader against the public info endpoint — paged userFills with a polite rate cap. No API key, no signing.

✓ users table + RLS migrations

SQL migrations for a users table and row-level-security policies where the client can read its own row but only the service role can grant plan upgrades — the pattern that makes self-upgrade impossible.

✓ Pricing / signup / dashboard scaffolds

Working /pricing, /signup, and /dashboard pages wired to the auth + plan + checkout flow above, in a dark Tailwind theme you can restyle.

✓ .env.example + README

Every required key documented (Supabase, Helius, NowPayments) and a step-by-step setup README that gets you running locally and deployed to Vercel.

Private Pro repo — unlocked with purchase

Collaborator access auto-granted to your GitHub after checkout.

★ Lemon Squeezy card-payment webhook

The full signature-verified, idempotent LS webhook that's the only thing that can upgrade a user — subscription + lifetime handling, all events.

★ Plan-expiration daily cron

A Vercel cron route that expires lapsed passes so access actually ends when it should.

★ Webhook signature verification + idempotency

The constant-time HMAC verification helper and the idempotency patterns that make re-delivered webhooks safe.

★ Trade-import pipeline patterns

The reusable importer pattern: fetch → normalise → dedupe by tx → upsert under the user's id (RLS-scoped), shared across the Solana and Hyperliquid importers.

Be clear-eyed — what this is not

•It is not a no-code product — you'll need to be comfortable with TypeScript, Next.js and SQL.
•It does not include DegenJournal's product-specific UI (journal, AI sentiment scoring, scorecards) — those stay proprietary.
•Crypto checkout requires your own NowPayments account; card checkout requires your own Lemon Squeezy account. The kit wires the integration; you bring the merchant accounts.

FAQ

Is this real code or AI-generated boilerplate?

Real code. Every module is extracted from degenjournal.xyz, which is live and built on exactly this stack. The auth, crypto checkout, and wallet-reading code is the same code running in production.

What do I actually get for $29?

The public repo is MIT and free to anyone. The $29 gets you collaborator access to the private Pro addon repo (card-payment webhook, expiration cron, import pipeline patterns) plus the 40-page implementation guide PDF. Launch price; it goes to $49 after the first 30 days.

How do I get the private repo access?

At checkout you enter your GitHub username. The moment payment clears, a webhook adds you as a collaborator on the private Pro repo automatically. Check your GitHub notifications for the invite.

What's the license?

The public starter repo is MIT — use it in commercial projects, no attribution required. The private Pro repo is licensed for your own projects (not for resale as a competing kit).

Does it lock me into any vendor?

Auth is Supabase, crypto checkout is NowPayments, card is Lemon Squeezy, Solana data is Helius — all swappable. The code uses plain fetch against documented APIs (no heavy SDKs) so you can see and change every integration.

Ship your crypto SaaS this weekend, not next month.

checkout opening soon