Products · 11 · Licensing Platform
← All productsLicenceR
Simple licensing, seriously enforced. Grace periods, not outages, when the network blinks.
Register your products, decide how each licence is metered, and issue it — directly, through a reseller, in bulk, or by card from a self-service shop. Every licence becomes a signed token that your application verifies offline, refreshed by calling home. Paid orders become invoices, delivered as compliant European e-invoices through your own account.
10Licence types
4Role-scoped portals
13Built-in reports
95.9%Line coverage, enforced
The problem
Licensing is where a product company quietly leaks money and goodwill.
The licence key generator is a script one engineer wrote and nobody else understands. Renewals are tracked in a spreadsheet, so some lapse silently while others are chased twice. The reseller e-mails for a key and waits until Tuesday. And when a customer's network hiccups, your software stops working — which costs more trust than the licence was worth.
01
A key script
Issuance depends on one person, one laptop and no audit trail.
02
Silent lapses
Renewal revenue lost because nothing warned anyone in time.
03
Resellers waiting
Every partner key is a support ticket against your team.
04
Brittle enforcement
A check that fails closed on a network blink turns your licensing into an outage.
The solution
The whole licence lifecycle, and the money behind it, in one system you own.
01
Enforcement that respects reality
Licences are signed tokens your application verifies offline, with a configurable grace period carried inside the token. A customer whose connection drops keeps working; a customer who stops paying does not.
02
Types are configuration
Ten licence types run on six enforcement strategies, decoupled by design — so how a product is metered is a setting per product, not a code change and not a release.
03
The channel serves itself
Resellers issue their own licences to their own customers in their own portal. Customers buy, renew and download in theirs. Your team stops being the bottleneck.
Why it's built this way
01
Offline-first enforcement
The token is signed with your organisation's own key and verifies against the public half with no network at all — which is what lets you sell into air-gapped, factory-floor and shipboard environments where a call-home licence check would disqualify you from the tender.
02
Call-home health as an early signal
The call-home health report lists licences that have gone quiet — paid-for software that stopped phoning home. That is a churn signal, a failed-deployment signal and a tampering signal, and it arrives before the renewal conversation rather than after it.
Capabilities
01Licence engine
- Ten licence models: perpetual, subscription, fixed period, volume, concurrent seats, site, trial, evaluation, not-for-resale and OEM
- Six enforcement strategies — none, fixed date, date from activation, usage count, concurrent seats and named seats — chosen independently of the licence type
- Per-product configuration: duration, grace days, seat and usage ceilings, metric label and unit, reset period, heartbeat interval, offline allowance
- Configurable key format, generated securely with ambiguous characters removed and checked for collision
- Key rotation on renewal: keep the key, rotate with a grace window, or rotate immediately
- Append-only audit trail covering thirteen event types: issue, activation, suspension, revocation, renewal, rotation and more
- Bulk issue up to 500 licences per batch, or import up to 5,000 rows from CSV, XML or JSON with a dry-run preview
02Call-home API & integration
- Validate at start-up, returning status, entitlements and a freshly signed token
- Heartbeat carrying usage delta and cumulative usage for metered licences
- Activate against a hardware fingerprint, hostname, operating system and application version; idempotent
- Rate limits per licence key: ten validations, twenty heartbeats and sixty activations per minute
- Signed webhooks to the customer on renewal and revocation
- Integration guide with client examples in Java, Python and Node, an API explorer, and copy-paste code in eleven languages
- Specification exportable as JSON, YAML or Markdown, plus an integration brief written for a coding agent
03Portals & self-service purchasing
- Four role-scoped portals — Organisation, Partner, Customer and Platform — covering issuance, billing, reporting and administration
- Eight roles arranged in a real hierarchy, enforced on essentially every endpoint
- Customers and resellers self-serve: browse, buy, renew and download their own licences and tokens
- Each organisation connects its own payment account; the platform holds no money and takes no cut
- Orders are baskets covering several licences, products and types under one payment and one invoice
- Exactly-once settlement between the payment webhook and the returning browser, under a lock
- Operator-raised orders for phone, purchase-order and bank-transfer sales, with a visible, retryable paid-but-unfulfilled state
04Invoicing & e-invoicing
- Every fulfilled order drafts an invoice automatically, whether or not e-invoicing is connected
- Peppol BIS Billing 3.0 documents delivered through the organisation's own account
- European VAT rules validated before sending: standard, zero, exempt, reverse charge, intra-community, export and out-of-scope
- Gapless invoice numbering under a row lock, with configurable prefix, year, month and padding
- Bill-to resolution across partner and customer defaults, frozen onto the order when raised
- Four export formats, with a sent invoice exporting its stored bytes unchanged
05Delivery, alerts & insight
- Built-in SFTP server with per-customer, per-product credentials and a file browser confined to each credential's own directory
- Product releases with version, notes, checksum and a generated manifest that signals an available upgrade
- Expiry warnings at 30, 14, 7 and 1 day, with de-duplication, plus grace and usage-threshold warnings
- Thirteen built-in reports: by product, type and customer, expiring and expired, renewals due, seat utilisation, call-home health and more
- Live log console with runtime log levels, and a health screen for memory, threads and caches
- Five outbound mail providers, resolved from the organisation's own configuration or a platform fallback
■Java 21 on Spring Boot 4, with a native-image build profile
■PostgreSQL, 25 versioned migrations, 30 tables
■Server-rendered vanilla ES6 front end — no package manager, no Node in the build
■RSA key pair per organisation for signing; rotation retires rather than deletes keys
■One-command install: three containers, credentials generated on first start into a volume
■2,131 tests; enforced build floors of 95% line and 80% branch coverage
What it does
- 01Licences are signed tokens verified fully offline, with a configurable grace period — a network blink never becomes an outage.
- 02Resellers and customers issue, buy and manage their own licences in their own portals — your team stops being the bottleneck.
- 03Every fulfilled order drafts a compliant Peppol e-invoice automatically, through your own payment and invoicing account.
At a glance
For whomISVs · Engineering & Simulation Software · OEM & Channel Sales
LicenceLicenceR is licensed per installation, with no per-activation fee. The annual fee follows a marginal schedule based on your own turnover, from a €900 minimum, with any yearly increase capped at 25%. Every tranche carries unlimited users, projects and organisations inside one tenant; hosting, hardware, consultancy, setup, migration and training are billed separately.