Clavem

Selling and licensing an indie game directly with Stripe

Selling a game directly means a key at purchase, a download for each platform and a launch-time check that never stops a single-player game from starting when the player is offline. Clavem issues the key and hosts the builds; the game keeps a signed token and verifies it locally.

Where this fits next to Steam and itch.io

Steam and itch.io are stores. They find buyers, take payment and deliver builds. If a store can do that for you, it may be the better choice, and you can also sell direct alongside it. itch.io’s creator FAQ says it does not impose DRM: it “lets users download the games exactly as you uploaded them”, and it offers download keys you can generate for your own customers. Steam has its own keys and its own distribution tools; see its Steamworks documentation for the terms.

Selling from your own site fits when you want the customer relationship and an email list, the full price minus Stripe’s fee, a launcher or website you control, or a way to sell a build to people who are not on a store, such as a school, a library or a convention. Clavem covers the part a store would do: the key, the device limit, the downloads and the updates. The blog article on selling games outside Steam covers the wider decision.

What is specific to games

Offline single-player. A single-player game that will not start without a connection invites refund requests. Design for the offline path first. At activation, store the key, the instance id and the signed token. At launch, try validate with a short timeout; if it fails, verify the token’s signature and refresh_by, and start the game. Only after the 14-day window ask for one online check, and even then offer a few more days of play.

Gentle enforcement. Ask for the key once, at install or first launch. A check on every level load, an always-online requirement or a game that locks after a week of travel makes paying customers worse off than pirates. Check at launch, then leave the player alone. The piracy article argues this at length.

Where to put the check. In a game engine, put it in the launcher or the title screen, not in the gameplay loop. The Unity, Godot and Unreal guides show where. Do it on a background thread so a slow response does not freeze the menu.

Device names. Players recognize ADA-GAMING-PC and Steam Deck, not hashes. Send the computer’s name as instance_name, so the device page is readable when they need to free a seat.

Demo builds. Do not put the key check in the demo. Ship it as a separate build or a separate product with no license, and keep the key for the full game.

Large builds and storage

Game builds are big, and Clavem’s file rules are specific. Each file can be up to 5 GiB, and each plan has a storage total: 1 GB on Free, 10 GB on Indie, 50 GB on Studio. Downloads are not metered.

As a worked example, take a game with a 2.5 GB build for each of Windows, macOS and Linux. One version is 7.5 GB. On Indie, with 10 GB, that fits once; a patch release that uploads a second full set would need 15 GB, so you would delete the previous build, or move to Studio. The size you declare when an upload starts is reserved until it finishes, and an upload that does not fit is refused before it starts. Smaller games, or builds split into an installer and a separate data pack, fit more easily. If your builds are far larger than this, host them on a CDN and use Clavem only for keys and for gating the download link.

Label each file windows, macos or linux, and let a launcher ask GET /v1/releases/:productId/latest?platform=windows with the player’s key. The response gives a signed download link, valid for an hour, only to a valid key. See releases and downloads.

Setting Suggested value Why
License type Perpetual Matches how a game is sold: pay once, play indefinitely
Device limit 3 to 5 Desktop, laptop, handheld, and reinstalls
Trial A free demo build, not a key A demo needs no check
Updates The launcher checks the releases endpoint Patches go to valid keys only

For DLC, create a second Clavem product and map it to its own Stripe price. A checkout with both a base game and a DLC mapped issues a key for each.

Doing this with Clavem

Create a product, connect Stripe, map the price. A buyer gets an email with the key and an order page with the builds. The game calls activate once, then validate at launch. Clavem is not a merchant of record, so VAT and sales tax on game sales are yours to handle through Stripe. That is general information, not tax advice.

Guides to follow

Questions

Should a single-player game need an internet connection to start?

No. Activate once, store a signed token, and verify it on the device. Ask for a connection only after the token's 14-day refresh window has passed, and even then let the player continue for a stated grace period.

How many devices should a game key allow?

Three to five is a sensible range. Players own a desktop and a laptop, may add a handheld PC, and reinstall often. Too low a limit creates support mail; too high invites sharing.

Sources

  1. itch.io creator FAQ, DRM and download keys (checked November 2026)