Developer docs
Integration checklist
Everything a developer does to take a product live on DevEntitle, in order, from sign-up to your first published release.
1. Create your account and company
Create a free account and your company. Set your support email in Company settings: it appears in licence messages and emails to your buyers.
2. Add your product
Choose the slug carefully (for example acme-crm): your software sends it and it can’t change. Choose how licences are counted: per website domain, or per machine ID.
3. Add licence types
Number of sites or devices, support period (months or lifetime), whether updates continue after support ends, channel (stable or beta), and prices if you’ll sell on DevEntitle.
4. Create a signing keypair
Use the Release Kit. Paste the public key on the product and build it into your product. Keep the secret key offline.
5. Add the licence screen to your product
A key field, and calls to activate, deactivate and updates (see the client code). Show message as it is. Never disable features.
6. Add update installation
Download, verify the SHA-256 and the signature, then install. Ask for a fresh download link just before installing: links last 30 minutes.
7. Test with a real licence
Issue a test licence in the panel. Test on a development host (it doesn’t use a seat) and on a real domain. Try the limit-reached message and deactivating.
8. Ship your first release
Sign and upload your first release, publish it, and check that an installed copy sees it and installs it.
9. Optional extras
An API token for your website or CI, webhooks for your CRM, the storefront with your own payment gateway.
Before you ship
Check the rules for products once more: features never depend on the licence answer, 5xx means “try later”, and checks happen on demand or once a day.