How to license and sell a Godot game
Install the native GDScript add-on, require a key for your exact product, protect paid features, and connect your game or editor tool to your branded Store.
Copy addons/permitcore from the SDK ZIP into res://addons/permitcore
extends Node
# Copy addons/permitcore into res://addons/permitcore first.
const PermitClient = preload("res://addons/permitcore/permitcore_client.gd")
var client = PermitClient.new("http://localhost:5127", {
"trusted_public_keys": ["YOUR_TENANT_SPKI_BASE64_PUBLIC_KEY"],
"cache_directory": "user://permitcore"
})
func can_use_pro_features(key: String, product_id: String) -> bool:
var result = await client.validate(key, "1.0.0", product_id)
return result.is_valid and result.has_feature("pro")
func register_installation(key: String, product_id: String) -> bool:
var result = await client.activate(key, "", "My Godot app", "1.0.0", product_id)
return result.is_validFrom product record to paid customer
Use PermitCore for the licensing layer and Store checkout. Verified paid evidence triggers the configured license issuance and queues the delivery email; test actual delivery before launch.
- 01Create
Create the product and license policy
In Products, create the software your key unlocks. Choose its activation limit, validity, offline grace period, version range, and feature flags.
- Create the game or editor-tool product
- Choose activation limits and optional offline grace
- Add your paid feature flags, such as pro
- Copy the product ID and trusted public verification key
- 02Implement
Install the Godot SDK and scope the key
Put license activation in the first-run flow and validation at startup. Pass your product ID so a valid key for another product cannot unlock this one.
These are application fragments: supply your own key/product variables and UI or host flow. A validation call does not register a device or reserve a floating session. Check failure before protected work. Offline use needs explicitly configured trusted public keys; follow the SDK offline setup. For C++, use the vcpkg registry and pinned baseline in its installation reference, rather than assuming a built-in public port.
Copy addons/permitcore from the SDK ZIP into res://addons/permitcore- Download the Godot SDK ZIP and copy its add-on
- Await validation without blocking the game loop
- Pass the exact product ID and current app version
- Activate devices explicitly and configure trusted offline public keys
- 03Verify
Test the real validation path
Run the included project in the Godot editor and test an exported build on every supported target. Verify valid, expired, revoked and wrong-product keys, device activation, feature flags, and disconnected behavior with a signed proof. A validation result alone does not reserve a floating seat.
- 04Sell
Publish the product in your Store
Connect your chosen Stripe, Paddle or Lemon Squeezy account, add the product to your branded PermitCore Store, and publish. Account credentials, matching catalog prices and signed webhook configuration are required. PermitCore processes the verified payment and handles Store license fulfillment.
- Publish your tested game builds
- Add the product and downloads to your Store
- Connect your chosen Store payment provider
- Test checkout, issuance and actual delivery with your own test customer
Verified payment triggers license issuance and the delivery email queue.
Godot production checklist
The sample is intentionally small. Add these safeguards before making licensing part of a paid release.
Watch the native Godot walkthrough on YouTube for the real editor integration and desktop demo. Read the companion guide for the tested scope and offline trust policy.
- Ship public verification keys only; keep Admin API credentials outside the game.
- Keep entered license keys out of logs, recordings and source control.
- Check is_valid and the required feature before protected work; handle failed activation separately.
- For floating licensing, check out a seat and schedule heartbeats; validation does not create a session.
- Re-verify signed offline proof and its product/device/deadline context. Untrusted cache files cannot grant access.
- Test editor and exported builds on every platform you promise. Web exports require separate acceptance.