Licensing your own software
Take the payment, mint the keys, deliver them, and answer the question your software actually asks - is this user licensed right now - including on machines that never touch the internet.
Point your Buy button at a hosted page that shows your product, your price and what one unit covers. There is nothing to host, no cart to build, and no webhook to write - the licence and its codes exist the moment the payment clears.
The checkout session is created on your own connected account, so funds settle to you and our fee rides on top as an application fee rather than us collecting on your behalf. The fee is per account and negotiable.
Codes are minted per unit at payment, hashed at rest, and shown exactly once. Your customer activates on a page we host - which you can put in an iframe on your own site - or against the public redeem call from your own installer.
Is this user licensed, is this machine covered, is this build covered. The console generates that exact call for your product in Node, Python, C# or curl, with your identifiers filled in and its advice matched to the term you actually sell.
Mint a short-lived signed certificate once, on a machine that has a connection. Your software verifies it with an Ed25519 public key baked in at build time, with no network and no call back to us, ever - and it can never outlive the licence behind it.
A code can bind to a device on first use, so a leaked code stops working while the person who already installed it keeps working. Hardware dies, so a bounded number of rebinds needs nobody's permission, and you can rebind past that yourself.
A perpetual licence keeps working forever while covering only the builds released inside its maintenance window. The answer reports both facts separately, and the ceiling comes from the releases you declared rather than from comparing version strings.
A hosted purchase page you link at from your own site, payment taken on your own Stripe account, and one redemption code minted per unit the moment the payment clears - emailed to the buyer without you writing a webhook. Inside your software, one authenticated request answers whether a given user is licensed right now. Your customer activates their code on a page we host, or on your own. There is nothing to host and no billing code to write.
You do. The checkout session is created on your own connected Stripe account, so the funds are yours and settle to you, with our fee riding on top as an application fee rather than us collecting on your behalf. That fee is per account and negotiable, and an account set to zero pays zero.
Yes. You mint a short-lived certificate on a machine that does have a connection, and your software verifies it with an Ed25519 public key baked in at build time - no network, and no call back to us, ever. The certificate expires, and it can never outlive the licence it was minted from. It also carries its own audience value, so a token issued for something else cannot be replayed at your licence check.
Yes. A redemption code can bind to a device fingerprint on first use, after which that seat only answers for that machine - so a code that leaks stops working while the person who already installed it keeps working. Hardware dies, so a bounded number of rebinds is allowed without anyone contacting support, and you can rebind past that limit yourself.
Yes. A perpetual licence with a maintenance window keeps working forever while only covering builds released inside that window, and the entitlement answer tells your software both facts separately - still licensed, and whether this specific build is covered. You declare releases as you ship them, and the ceiling is read from what you declared rather than from comparing version strings, so 4.10.0 is correctly newer than 4.9.0.
The licence suspends rather than ends. Codes and seats survive untouched, so a billing hiccup never forces your whole customer base to re-activate, and a later successful payment extends the term and restores access in one step. Ending a licence is a separate, deliberate act.
No, and they are easy to confuse. An enterprise agreement buys Connections' own usage in bulk at a negotiated price. Licensing is you selling your own software to your own customers, using our billing, code delivery, and entitlement checking. They share one underlying idea - seats - and nothing else.
The selling half is a link, so it takes as long as pasting one. The enforcement half is a single request from inside your software, and the console generates that call for your specific product in Node, Python, C# or curl, with your identifiers already filled in and its advice matched to the term you actually sell.