Keygen Cloud vs Self-Hosted License API Pricing — what do I need to change?
Desktop and SaaS vendors implementing product licensing need to decide whether Keygen’s hosted pricing, add-ons, and API rate controls beat self-hosting CE or buying EE licenses.
Blockers
- requires_version: vendor/keygen → runtime/ruby-3.1
- requires_version: vendor/keygen → package/postgres-13
- requires_version: vendor/keygen → package/redis-6.2
Who this is for
- cost-sensitive
- low-ops
- enterprise
- small-team
Candidates
Keygen Cloud
Keygen Cloud is Keygen’s managed licensing and distribution API. As of 2026-03-27, official pricing is usage-based by active licensed users, with a free Dev tier that allows up to 100 active licensed users and 10 product releases; exact paid tier dollar amounts should be checked on the official pricing page. Standard and Enterprise hosted tiers expose add-ons including whitelabel API domains for "$995/yr per domain", premium support for "$995/mo", and Enterprise-only custom API rate limits and static IP options. Keygen Cloud also handled SOC 2 Type II compliance by 2026-01-26, which reduces compliance and ops burden versus self-hosting.
When to choose
Use this when "low-ops" and "small-team" matter more than infrastructure control, or when you want the fastest path to production licensing. It is the decisive choice if you want managed HA, backups, maintenance, and the earliest access to new Keygen features instead of waiting for self-hosted release trains.
Tradeoffs
Lowest operational burden and strongest managed security posture, but you stay on Keygen’s hosted rate controls and packaged feature gates. Enterprise-only extras such as custom rate limits, SAML/SSO, uptime SLA, and static IPs can push you into higher-cost tiers.
Cautions
As of 2026-03-27, client-side rate limiting is explicitly documented at 60 requests per 30 seconds and 500 requests per 5 minutes per token-and-IP combination; if your product performs bursty client validation, design around that or negotiate Enterprise custom limits. The official pricing page renders paid plan prices dynamically, so verify current dollar amounts directly before budgeting.
Keygen CE self-hosted
Keygen CE is the free self-hosted Community Edition. As of 2026-03-27, it is free for personal and commercial projects and is the default self-hosted edition, but support is best-effort through community channels rather than dedicated vendor support. Self-hosting requires Docker on x86_64 with SSE 4.2, and Keygen requires Ruby >= 3.1, Postgres >= 13, and Redis >= 6.2. Self-hosted releases are described as an LTS-style track, with new releases roughly twice a year after features are battle tested in Keygen Cloud.
When to choose
Use this when "cost-sensitive" dominates and you can absorb infrastructure ownership, upgrades, backups, and incident response. It is the decisive choice if you need zero software license cost from Keygen and can accept slower feature availability plus community-grade support.
Tradeoffs
No Keygen subscription cost, full hosting control, and source availability are the main benefits. The tradeoff is higher ops burden, slower access to new features, and loss of managed support, hosted compliance posture, and some enterprise-only functionality.
Cautions
Do not assume CE tracks Cloud feature velocity; the self-hosted track intentionally lags Cloud and older versions do not receive backported fixes. If you later need import/export, audit logs, SSO/SAML, or dedicated self-hosting support, that pushes you toward EE.
Keygen EE self-hosted
Keygen EE is the paid self-hosted Enterprise Edition. As of 2026-03-27, it requires a valid license key to run, can be bought as a flat-rate singleplayer license, and multiplayer licensing requires contacting Keygen; exact price should be checked on the official pricing page or purchase flow. EE adds request logs, event logs, environments, enterprise permissions, import/export for Cloud-to-EE and EE-to-Cloud migration, OCI/Docker distribution, SSO/SAML, and dedicated self-hosting support. It keeps hosting under your control while unlocking features missing from CE.
When to choose
Use this when you need self-hosting for data residency, network control, or internal security requirements, but CE is too limited operationally or functionally. It is the decisive option when you need self-hosted enterprise features such as SSO/SAML, auditability, migration tooling, or support without moving to Keygen Cloud.
Tradeoffs
You retain deployment control while getting enterprise features and vendor support. The tradeoff is that you still own infrastructure and upgrade work, and exact license cost is less transparent in the accessible docs than the hosted packaging overview.
Cautions
As of 2026-03-27, self-hosted Keygen follows the same slower release cadence as CE, so EE does not eliminate version lag versus Cloud. Multiplayer mode is not a default self-hosted capability; it requires a Keygen EE license with the relevant entitlement and vendor coordination.
Try with your AI agent
$ npm install -g pocketlantern $ pocketlantern init # Restart Claude Code, Cursor, or your MCP client, then ask: # "Keygen Cloud vs Self-Hosted License API Pricing — what do I need to change?"