Get startedUpdated 2026-11-05View as MarkdownEdit on GitHub

Keyvane documentation

Keyvane is the monetization access layer for independent software. It sits between your payment provider and your product and answers one question reliably: what is this customer allowed to do right now?

 ┌──────────────┐  signed webhooks   ┌──────────────┐   SDK / REST API   ┌──────────────┐
 │    Stripe    │ ─────────────────▶ │  Keyvane   │ ◀───────────────── │   Your app   │
 │ payments,    │                    │ plans, keys, │   "can user_42     │ web, API,    │
 │ invoices,    │                    │ entitlements,│    export?"        │ desktop, CLI │
 │ taxes        │                    │ usage, audit │                    │              │
 └──────────────┘                    └──────────────┘                    └──────────────┘

Keyvane is not a payment processor, Merchant of Record or tax engine. Your payment provider keeps doing that job. Keyvane turns its commercial events into product access.

Start here

  1. Quickstart: run Keyvane, define plans and make your first entitlement check in about 10 minutes.
  2. Core concepts: projects, products, plans, features, customers, licenses and how access is decided.
  3. Stripe integration: connect a webhook, map prices to plans and tell Keyvane who paid.
  4. License keys & devices: sell desktop software and CLIs with keys and activation limits.

Guides by stack

Reference

Examples in this repository

Example What it shows
examples/pdf-analyzer A web app with Free / Pro / Business plans, a metered feature, a Pro-only feature and Stripe upgrades
examples/license-cli A CLI licensed with keys, device activations and an offline grace period