Your pricing is stuck in your build
You want a starter tier, a pro tier, and a higher limit for one large customer. Today that means another branch, another build, another release.
Software monetization and licensing
Ship software.
Keep the revenue.
Decide what each customer gets and for how long. DYCRYPT signs that into a licence your application checks by itself — online, offline, or both.
Signed licences, verified by your own applicationWorks air-gappedJava · Node.js · Python · C++
DYCRYPT / APPLICATION FLOW
01
Set up your productWhat it grants · how long · how it’s signed
02
Pick how it’s enforcedOffline · Online · Hybrid
03
Issue the signed licenceCustomer · machine · edition and limits
SDK
Your application checks itVerify · check status · read the claims
ACTIVE · BOUND TO ONE MACHINE
The problem
Shipping the software was the easy part.
Most teams build something good, then improvise everything that happens after the download. It works fine — right up until it doesn’t.
One key, quietly everywhere
A licence meant for one machine ends up on five. Or on a forum. You find out when support hears from someone who never bought anything.
Nobody knows what’s out there
Who expired last month? Who stopped paying and is still running? Who swapped a laptop? The answers live in a spreadsheet, if they live anywhere.
Pillar one · Software monetization
Sell one build a dozen different ways.
Your product holds the rules. Each licence carries the answers. DYCRYPT doesn’t take the payment — keep whatever checkout you already use. It decides what the customer gets once they have paid.
Editions, features, and limits
Define your parameters once on the product: text, numbers, yes or no, dates, lists, or a fixed set of choices. Pick the values when you issue. Your application reads them and behaves accordingly.
Term or perpetual
Give a licence a start date and an expiry, or leave the expiry off and let it run forever. Same product, same code, different commercial deal.
A grace period, not a hard stop
A licence in grace is still valid. Your customer sees a warning instead of a locked screen, and you get a renewal conversation instead of an angry ticket.
Renewals that don’t break anything
Renewing issues a new term. The licence you already delivered stays exactly as it was signed, so nothing in the field changes underneath your customer.
Revoke and reinstate
Someone stops paying? Revoke, and their next online check fails. They come back? Reinstate, and they’re running again. No new build, no new download.
Issue from your own systems
Scoped API tokens automate product, customer, and licence work, limited to the resources and actions your integration actually needs.
Pillar two · Software licensing
One licence. One machine. Proof, not trust.
Every licence is signed before it leaves DYCRYPT. Your application verifies that signature itself and then decides what to do. No valid signature, no access.
Offline
Bind the licence to the customer’s machine before you issue it. The application verifies locally and never contacts DYCRYPT. Built for air-gapped rooms.
Online
The first successful check claims the licence for one machine. Your application keeps checking on the schedule you set, so a revocation lands right away.
Hybrid
Verify locally at every start, confirm online in the background. Your customer keeps working through a flight or an outage, inside the window you signed.
Signed your way
Sign with Ed25519, RSA, or elliptic curve. Verify with a public key, an X.509 certificate, or a keystore. On-premises customers can add HSM or PKCS#11 for hardware-backed keys.
Fingerprints that survive real life
DYCRYPT hashes five machine signals separately and matches three by default, so a new network card doesn’t lock out a paying customer. When hardware genuinely moves, release the machine and the next install claims it.
Nothing identifying leaves the machine
Each signal is hashed on the device and truncated before it is sent. Raw identifiers never leave. IP address, user name, process ID, and container ID are excluded on purpose — not omitted by accident. Your DPIA answer is one paragraph long.
Statuses your app can explain
Active, grace, pending, expired, stale, revoked, invalid, unknown. Each one tells your application whether to wait, warn, reconnect, renew, or stop — so the message your customer reads is actually useful.
Why an online check can be trusted
A licence check you can’t fake by faking the server.
Most online licence checks trust whatever answers. Point the application at a different host and it hears “yes.” DYCRYPT signs every check answer with your product’s key, so your application can tell the difference between DYCRYPT and something pretending to be DYCRYPT.
Read the receipt security model →- The receipt, not the connection, is the proof. TLS protects the request in transit. The signed receipt is what proves DYCRYPT answered.
- Your application already holds the public key. No extra infrastructure and no shared secret to leak. The same key that verifies the licence verifies the answer.
- A configurable endpoint stops being a bypass. Documented, deliberate, and closed by design.
Why both together
Two jobs, one system.
What you sell and what you protect are the same decision, made twice. Handling them in one place saves the round trip.
What that gets you
- Change your packaging without changing your code. A new edition, limit, or expiry is a value you choose at issue time, not a release you have to ship.
- Spend less time on licence support. Your app tells the customer to reconnect, renew, or wait, and you release a machine or reinstate a licence in seconds.
- Ship into any environment. Air-gapped, always connected, or somewhere in between — and DYCRYPT itself runs as SaaS or inside your own network.
Use it your way
Hosted by us, or run by you.
Start on the hosted service and skip running licensing infrastructure yourself. Move to DYCRYPT Sovereign when your security or compliance rules require your own environment and keys.
Ready when your team is
Create your organisation, set up a product, add the SDK. There is no licensing server for you to operate.
Your network. Your hardware. Your keys.
Run DYCRYPT inside your own environment and sign with your own HSM or PKCS#11 token. The private key never exists anywhere else — which means no one can mint a valid licence for your product, including us.
Explore DYCRYPT Sovereign →Quick start
From product to verified licence.
Create your organisation, set up a product, and add licence checks to your application. The Quick Start walks the whole path.
Read the Quick Start Guide →The integration path
- Create your DYCRYPT organisation.
- Define a product, a licence type, and your parameters.
- Issue the signed licence and send it to your customer.
- Verify it from your application with Java, Node.js, Python, or C++.
Coming from Cryptolens, Keygen, or LicenseSpring? See how DYCRYPT compares and what a safe, release-by-release move requires. Compare the options →
Start with the Free plan
Watch a real licence verify in your own application.
Free covers the whole workflow and your first 250 active licences in production. Wire it into Java, Node.js, Python, or C++, ship it, and upgrade when the installed base arrives.