Self-hosted license key API for indie software developers
Pain Point
Commercial billing and licensing platforms are pricey and lock you in, while open-source options are hard to deploy; indie devs lack a lightweight, controllable licensing layer.
Target User
Indie developers selling desktop apps, plugins, and self-hosted tools
Keywords
Monetization
Free up to 100 keys, then $19-39/mo tiered by key count or API calls; a $149-299 one-time self-hosted edition.
Competition
Lago is open-source and self-hostable with no lock-in, but deployment is heavy and it focuses on enterprise subscription, invoicing, and usage billing. It does not solve license key issuance, device binding, or offline validation for indie software sellers.
Project Brief
Overview
A lightweight, self-hostable or managed license key and entitlement API for indie software developers — issue, validate, bind to devices, and revoke licenses for desktop apps, editor plugins, and self-hosted tools.
Pain Point
Open-source billing stacks like Lago are self-hostable and lock-in free, but deployment is heavy and they focus on enterprise billing (subscriptions, invoices, usage, payments). They do not solve what indie developers actually face after a sale: issuing a license key, binding it to a device, limiting seats, validating offline, and revoking remotely. Commercial licensing platforms such as Keygen and Cryptlex are enterprise-oriented with pricing and docs to match. Building it in-house means dealing with signature tampering, device fingerprints, and revocation sync — slow and error-prone. The real need is not a stronger billing engine, but a frictionless licensing loop that starts after checkout.
Target User
Indie developers selling desktop software, VS Code extensions, Figma plugins, and self-hosted tools via Gumroad, Lemon Squeezy, Polar, or Stripe. Typically $500-$20k MRR with no dedicated backend engineer.
Market Opportunity
The original signal points to two things: developers want open, self-hostable, customizable, lock-in-free infrastructure, and they complain that current open-source options lack usability. Checkout and payments are already well served by Stripe, Lemon Squeezy, and Polar. The gap sits between payment success and product activation — entitlement, seats, devices, and renewal state. That is a narrow, testable wedge with clear willingness to pay.
Monetization
Tiered by key count or validation API calls: free up to 100 keys, then $19-39/mo; a $149-299 one-time self-hosted edition; white-label (custom domain and emails) as a premium tier. (Inferred — the source gave no pricing clues.)
Technical Complexity
Low to medium. Core is key generation and validation APIs, device fingerprint binding, revocation, offline signed license files (Ed25519), and webhook-based provisioning from Stripe/Polar. The real challenge is offline activation tamper-resistance and SDK consistency across languages — not scale.
Competition
- Keygen: veteran licensing API, feature-complete but enterprise-flavored UI and pricing.
- Cryptlex: commercial software licensing with trials and floating licenses; relatively expensive.
- Lemon Squeezy / Polar: issue license keys at checkout, but weak on device management and validation.
- LicenseSpring: enterprise licensing with heavy compliance and sales process. Entry barrier: medium. Technically approachable; the moat is developer trust, documentation quality, and SDK coverage — once integrated, switching costs are real.
GTM Strategy
- Primary channel: SEO (license key management api, self-hosted license server, software activation api) plus developer communities (r/selfhosted, r/SaaS, Hacker News).
- Cold-start tactic: launch as "open-source core + hosted edition" with a Show HN post and an r/selfhosted thread; the GitHub repo is the trust asset.
- Content leverage: comparison and how-to long-tail content works well — "Keygen vs rolling your own licensing", "offline licensing for desktop apps", "how to charge for a VS Code extension".
Execution Plan
- MVP core features: (1) key issuance/validation API with a three-line SDK; (2) device binding and remote revocation; (3) Stripe/Polar webhook auto-provisioning on purchase.
- What NOT to build: full invoicing, tax, multi-currency, or usage-based billing — that is Lago/Zuora territory and turns a two-week build into three months.
- Tech stack suggestion: Next.js + Supabase (Postgres) + Vercel + Stripe; Ed25519-signed license files; start with Node and Python SDKs.
- Estimated time to launch: low complexity — 1-2 weeks to a sellable v1.