Skip to content

Features

Everything a licence server needs

Licence keys, activations and signed updates for self-hosted software, with the tools around them: an API, webhooks, a storefront if you want one, a buyer portal and team roles.

Licence keys and activations

  • Keys like ACME-7KQ2M-X9PTR-4HWBN-C8ZVD: a prefix per licence type, four groups of five, no easily confused characters (about 98 bits of randomness)
  • Counted per website domain (web apps) or per machine ID (desktop apps, CLI tools)
  • Development hosts never count: localhost, *.test, *.local, private IP addresses and more
  • A limit of 0 means unlimited; a licence can override its type’s limit
  • Clear limit messages that name the other sites; buyers move licences themselves
  • Keys stored as a hash plus an encrypted copy, never logged, never in webhooks or exports

Licence types and support periods

  • Sites or devices per licence, support period in months or lifetime, stable or beta channel
  • Prices per currency for storefront sales
  • When support ends the licence stays valid; buyers keep every release published before that date
  • Optionally let updates continue after support ends (only help stops)
  • Renewals move support forward from today or the current end date, whichever is later; the key stays the same

Signed releases

  • Ed25519 signatures made on your own computer; the private key never reaches DevEntitle
  • SHA-256 and signature checked on upload, and again by your product before installing
  • Drafts, publish and unpublish; stable and beta channels; newest by version number
  • Download links that expire after 30 minutes, re-check the licence and support resuming
  • Release notes in Markdown, shown in your product before updating
  • The Release Kit: a free single-file signing tool for PHP or Node
  • Upload from the panel or from CI through the Management API

Developer tools

  • Licence protocol: three POST endpoints, four fields, nothing else sent
  • Management API with scoped tokens, cursor pagination, idempotency keys and an OpenAPI 3.1 file
  • Connected apps through OAuth 2 with PKCE, for marketplaces and resellers
  • Signed webhooks for eight event types, with retries over about two days and a delivery log
  • Copy-paste client code for PHP, Laravel, Node.js and Python

Selling (optional)

  • A storefront page per product with plan cards, prices and a currency switch
  • Checkout paid to your own Stripe, PayPal or Razorpay account; DevEntitle takes no fee
  • A licence is issued only after a verified payment
  • PDF receipts numbered without gaps, VAT/GST and any other tax, coupons, refunds and renewals

Buyers, teams and reports

  • One buyer portal for licences from every company, with emailed sign-in links
  • Branded emails sent as “Your company via DevEntitle” with your support address as Reply-To
  • Four team roles (owner, admin, developer, support), two-factor sign-in, a full audit log
  • Dashboards with live installs and the versions running in the wild; CSV exports
  • GDPR tools: export or erase everything about a buyer

What DevEntitle does not do

  • It never switches off features of your product. A licence covers updates, downloads and support.
  • It never holds your money or takes a fee. Buyers pay your own payment account.
  • It doesn’t collect data from inside your product. Four fields, nothing else.
  • It isn’t sold or self-hosted. It’s a free hosted service.

Read more

Add your first product today

Free for software companies. No fees on sales. Your buyers pay you directly.