Clear allowances. Flexible licensing.
Buy 1, 3, 6 or 12 months. Pay the total once; the package starts after successful payment.
Device and API quotas reset each month. Unused quota does not roll over.
Loading plans…
How is usage beyond the allowance charged?
Device allowance
Within a purchase period, the same device for the same product is counted once. When overage is allowed:Devices beyond the allowance × device unit price, deducted from the balance in the same currency. Insufficient funds prevent new paid devices. Hard-limit plans do not allow overage.
API call allowance
Each successful activation, validation, heartbeat or deactivation counts as one call. Failures, idempotent replays and local signature checks do not count. When overage is allowed:Successful calls beyond the allowance × API unit price. The accumulated charge is deducted from the balance. Each plan shows its limits and unit prices.
Unit prices support six decimal places. Cumulative charges are rounded to cents; only the new difference is deducted. Insufficient funds reject the next paid request without recording usage. Device and API fees are separate; releasing a device does not erase recorded usage.
Without a purchased plan
Default quotas and prices use UTC calendar months. Default device fees are billed monthly; API overage is deducted immediately. Purchased plans run for one month from payment. Their API quota does not stack with the default quota. Existing price snapshots stay unchanged when an administrator edits prices.
Loading default allowances…
Each plan has its own API quota and overage price. Unlimited calls incur no overage fee. A zero quota applies the overage rule from the first successful call.
Estimate your heartbeat traffic
For 100 devices running 8 hours a day, 22 days a month, with a request every 5 minutes, heartbeats alone total 211,200 calls / month. Local signature checks do not send requests.
Adjust validation frequency and estimate usage →