Getting Started

Ektasi licensing has three moving parts:

1. Your product ships with the License Guard (see SDK Integration).
2. The License API (api.ektasi.io) verifies purchase codes, domain-locks them, and issues signed tokens.
3. Your own storefront/portal — activation, downloads and domain management call the same API. (The Envato-era buyer portal at support.ektasi.io was retired 2026-07-17.)

Quick flow

1. A buyer purchases on your platform and receives a direct code.
2. They paste the code into your product. It calls POST /api/v1/license/validate.
3. The product stores the returned license token and periodically calls home (/heartbeat).
4. Premium features are gated server-side via /entitlement — a nulled copy gets nothing.

Providers

• direct — codes Ektasi issues for its own sales (HMAC-signed, forgery-proof, revocable on refund before or after redemption). Currently the only provider.
• The registry is extensible — add Gumroad/Paddle/etc. without touching the flow. Envato was removed 2026-07-17 when that marketplace line closed; adding a provider back is one file plus one line in lib/marketplace/providers/index.ts.

Next: License API Reference · SDK Integration · Anti-Nulling