LicenseManager
Paddle Billing integration

Selling with Paddle? Add license keys.

Paddle Billing handles checkout and taxes, but no longer generates license keys. Connect it to LicenseManager.dev: each completed transaction creates a license and emails the key to your customer, ready to activate in your app.

Free up to 100 active users. No credit card required.

checkout.js · main.ts
// Your website: Paddle Checkout, as you use it today
Paddle.Checkout.open({
  items: [{ priceId: "pri_01hv8x…", quantity: 1 }],
});

// Paddle completes the transaction, LicenseManager.dev
// creates the license and emails the key to your customer.

// Your app: the customer pastes the key
import { LicenseManager } from "@licenseman/electron";

const license = new LicenseManager({
  productId: "x7Kp2QaZ",
  publicKey: PUBLIC_KEY,
});
await license.setLicenseKey(key); // "ACTIVE"

Your customer pastes the key, your app unlocks

Paddle Billing

Paddle sells your app. It no longer licenses it.

Keep everything Paddle does well. LicenseManager.dev adds what Paddle Billing left out.

TopicPaddle Billing alonePaddle, with LicenseManager.dev
Checkout, taxes, invoicesYes: Paddle is your merchant of recordUnchanged: still Paddle
License keysNo: deprecated, only Paddle Classic had themOne per unit bought, emailed to your customer
Activations and machine limitsNoPer policy: 1 Mac, 3 machines, unlimited…
Offline checksNoSigned tokens, verified in your app
Desktop SDKsRemoved: the Windows SDK is gone, Mac only on ClassicElectron, Tauri and Swift
SubscriptionsBilling onlyA license valid while it's paid, with a grace period
Money back guaranteeRefunds from the dashboardCustomers cancel in a portal, the refund is requested for you

Setup

From a Paddle sale to an activated app

No webhook handler to write, no database of keys to keep. A few minutes in the dashboard, and the SDK in your app.

  1. 1

    Connect Paddle

    Create an API key in Paddle with read permissions, paste it, and LicenseManager.dev creates the notification destination. A sandbox key for your test products.

  2. 2

    Map your prices

    Choose which Paddle prices create licenses, and with which policy: a perpetual license on 3 machines, a yearly one, a monthly subscription…

  3. 3

    Sell with Paddle Checkout

    Nothing changes on your website. When a transaction is completed, the licenses are created and the keys emailed to your customer.

  4. 4

    Activate in your app

    Your customer pastes the key. The SDK activates it on their machine, stores it safely, and keeps checking it, online or offline.

Anti-piracy

Sold to one customer, used by one customer

Paddle collects the payment. LicenseManager makes sure the key it pays for only unlocks the machines it was sold for, and that the license in your app can't be faked or stretched.

Node locking stops key sharing

Each license runs on the number of machines you sold, recognized by a fingerprint of their hardware. A customer's new computer takes the place of their old one. But when two computers in use keep taking turns on the same key, LicenseManager spots it and locks the newcomer out, for good.

Code that runs on your customer's computer is never 100% safe from piracy: someone determined can always modify it. LicenseManager raises the bar well above casual sharing and tampering, the piracy that costs you the most.

Paddle integration

The hard parts are already written

Everything that happens after a Paddle sale, from the email with the key to the refund of a canceled license.

Pricing

Free for your first 100 active users. Then €29 a month.

Every feature, no time limit, no credit card. Only licenses used in the last 90 days count, and €29 / month covers 1,000 of them. Customers pay you on your own Stripe or Paddle account, and we never take a cut.

Say you sell 300 licenses at €49 this month:

Your sales
€14,700
A 5% cut
€735
LicenseManager
€29

FAQ

Questions before you start

Paddle Classic did. Paddle Billing, the version every new account uses, lists license key generation and activation as deprecated, and Paddle's Windows licensing SDK was removed. Paddle's advice is to build your own fulfillment from its webhooks: LicenseManager.dev is that fulfillment, already built.

No. Paddle stays your merchant of record: checkout, taxes, invoices, receipts and payouts don't change. LicenseManager.dev only reads your transactions, and writes nothing to Paddle except the refunds and subscription cancellations you allow.

Read access to transactions, customers, prices and products, and write access to notification settings. Subscriptions, refunds and the customer portal need their own permissions, all optional. See the permissions.

Yes. Connect a sandbox key from a test product, pay with one of Paddle's test cards, and you get test licenses. Live and sandbox stay apart. In the Paddle sandbox checkout, use 4242 4242 4242 4242 for a payment without 3D Secure, 4000 0038 0000 0446 for one with a 3D Secure challenge, or the Visa debit card 4000 0566 5566 5556, with the CVC 100 and any future expiration date. See Paddle's test cards for the full list.

The license is canceled at once, and shows its refund as pending until Paddle approves or rejects it. Your customer is told a refund was requested. See refunds.

Yes. Connect both: each one maps its own prices, and the licenses look the same in your app.

Any. There are SDKs for Electron, Tauri and Swift, and any other app validates a key with one HTTPS request, POST /v1/products/{productId}/validate-key, that needs no secret.

Something else? Write to us, a developer answers.

Your next Paddle sale could come with a key

Create a free account, connect a Paddle sandbox account, and buy your first license with a test card.