Skip to content

How it works

From your product to your buyer’s server

DevEntitle sits between your company and the copies of your software that buyers install. Here is the full flow, step by step.

The picture

Everything talks to DevEntitle over HTTPS. Money never passes through it: buyers pay the company’s own payment account.

  • Company panelYour team
    Issue licences, upload signed releases
  • Your website, billing or CRMManagement API
    Issue and look up licences
  • Your systemsWebhook receiver
    Signed events
DevEntitle

Licences, activations, signed releases, download links

terminal.deventitle.com

  • activate · updates
    Installed productOn the buyer’s server or computer
  • Keys, downloads, move a licence, renew
    Buyer portalThe buyer
  • Verified payment issues a licence
    StorefrontThe buyer pays your own gateway
Left: the software company’s side. Right: the buyer’s side. The company’s panel and systems issue licences and upload signed releases; installed products call activate and updates; DevEntitle sends signed webhooks to the company’s systems; buyers use the portal and the storefront, which charges the company’s own payment gateway.

Step by step

  1. 1

    A software company signs up

    Free, at the sign-up page. It adds a product with a unique slug, for example acme-crm.

  2. 2

    It creates licence types

    The plans: number of sites or devices, support period (months or lifetime), whether updates continue after support ends, release channel (stable or beta), and prices per currency.

  3. 3

    Licences are issued

    By hand in the panel; by the company’s own website or billing system through the Management API; by a connected app such as a marketplace; or by DevEntitle’s own storefront checkout, paid to the company’s own Stripe, PayPal or Razorpay account.

  4. 4

    The buyer enters the key in the installed product

    The product calls POST /api/v1/activate with the key, product slug, its domain (or device ID) and its version. DevEntitle answers valid or not, with a message to show.

  5. 5

    The product checks for updates

    It calls POST /api/v1/updates. Entitled licences get the version, release notes, SHA-256, an Ed25519 signature and a 30-minute download link.

  6. 6

    The company signs each release on its own computer

    The private key never leaves it. DevEntitle checks the signature before storing the upload, and the product checks it again before installing. Nobody, not even someone who took over the server, can push a fake update.

  7. 7

    Everyone sees what they need

    The company sees where every licence is installed and which versions are running, and gets webhooks when things happen. Buyers manage their licences in the buyer portal.

Fair to buyers

A licence unlocks updates, downloads and support. It never switches off features, and when support ends the licence stays valid.

Minimal data

Products send four fields: key, product, domain or device ID, and version. Nothing from inside the product.

Never cut off

If a company is suspended or a product retired, licences already issued keep answering. Installed copies keep working if the server can’t be reached.

Add your first product today

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