Plans & Billing
Every Admiral plan runs the full fleet platform. Telemetry is an add-on that an organisation switches on from Billing, security and compliance controls come with an Enterprise account, and AirDetect and Registry fallback are enabled per fleet and billed on usage.
How Pricing Works
Admiral is billed per device, per month, on a graduated scale: the first 5 devices on every account are free, and the per-device rate falls as the fleet grows. Current prices are on the pricing page. Telemetry is billed on top as an add-on, and AirDetect and Registry fallback are billed on usage.
An Enterprise account adds the security and compliance controls listed below, and can have custom pricing and invoicing terms. Contact sales.
The Billing Page
Open Billing (https://app.admrl.co/billing) from the sidebar. It has five tabs:
| Tab | What it shows |
|---|---|
| Overview | Progress through the current billing period (or trial) and the estimated next bill. |
| Plan & add-ons | Your per-device pricing, the add-ons switched on for the organisation, and the Registry fallback price with the fleets that have it on. |
| Usage | Usage for the period, broken down into devices, the Telemetry add-on, AirDetect, Registry fallback (with a per-fleet breakdown), and other usage. |
| Invoices | Past invoices with amount and status. |
| Payment & details | Payment methods, legal entity name, tax ID / ABN, and billing address. |
What Is Included
| Capability | Availability |
|---|---|
| Fleet management, configurations, system updates, rollouts, maintenance windows | Included |
| Real-time device logs, diagnostics and workload remote access | Included |
| Platform API, API tokens, service accounts and event webhooks | Included |
| Passkeys, 2FA, users, groups and IAM policies | Included |
| Device and fleet health (CPU, memory, disk, temperature) for the last 24 hours | Included |
| Built-in platform alerts, notified in the app | Included |
| Metric and log history beyond 24 hours, and the MetricsQL explorer | Telemetry add-on |
| Log search across several devices or a whole fleet, with live tail | Telemetry add-on |
| Custom alert rules | Telemetry add-on |
| Webhook delivery of alerts (platform alerts and your rules) | Telemetry add-on |
| Telemetry API with API tokens and service accounts | Telemetry add-on |
| Image signature policies (organisation, fleet and configuration) | Enterprise |
| USB policies (fleet and device) | Enterprise |
| Organisation audit log | Enterprise |
| AdmiralAI assistant | $5 of usage included each billing period, then usage-based |
| AirDetect presence detection | Enabled per fleet, usage-based |
| Registry fallback (image pulls through Admiral Cloud for restricted networks) | Enabled per fleet, usage-based |
See Telemetry, Alerts & Alert Rules, Account Security & Audit and AirDetect and Registry fallback for each feature.
Turning an Add-on On or Off
- Open Billing (
https://app.admrl.co/billing). - In Add-ons, switch on Telemetry.
Changing add-ons requires the Manage billing capability (billing.admin), held by users with the Billing manager or Administrator role. Other members see what is enabled, and locked features in the dashboard prompt them to contact a billing manager. Add-ons apply to the whole organisation. Billing must be set up for the organisation before an add-on can be enabled.
Signature policies, USB policies and the audit log are not self-serve: they come with an Enterprise account, which Admiral sets up. Contact sales to upgrade.
Usage-Based Services
AirDetect and Registry fallback are not organisation-wide add-ons. Each is switched on for a fleet and billed on what it is used for, so a fleet that has it off costs nothing.
| Service | Switch it on | Billed on |
|---|---|---|
| AirDetect | The fleet's AirDetect pages (Enable AirDetect) | Detected presence |
| Registry fallback | Fleet > Deploy > Configuration > Registry fallback | GB of image data delivered to devices |
Switching Registry fallback on requires the Manage billing capability (billing.admin), held by users with the Administrator or Billing manager role. The confirmation shows the price. Usage appears under Billing > Usage, and the invoice line is Registry Fallback Data Transfer. Prices for usage-based services are on the pricing page. See Registry Fallback Through Admiral Cloud for how it behaves.
AdmiralAI Assistant Usage
AdmiralAI, the assistant in the dashboard, is available to every organisation with no setup. Using the Admiral-hosted AdmiralAI is metered by tokens; using your own model endpoint is not billed by Admiral.
- Included: every organisation gets $5 of AdmiralAI usage per monthly billing period.
- Trials and no payment method: usage during a trial is free, but AdmiralAI stops when the $5 is used. Add a payment method to continue.
- Paying organisations (with a payment method or invoice terms): usage beyond the $5 is billed per token until total usage for the period reaches a monthly cap (default $50, including the $5). When the cap is reached AdmiralAI stops until the next period. Ask Admiral support to change the cap.
- Token classes: input, cached input, cache write, and output, each priced per 1 million tokens. Usage appears on the invoice; ask Admiral support for the current rates.
- On the invoice: the usage appears as its own lines, and an Included Assistant usage credit line takes off the first $5 (or less, if you used less). The credit never reduces anything else on the invoice.
- Fair use: a daily fair-use allowance per user and per organisation keeps the service responsive. Normal use does not reach it, and it resets at 00:00 UTC.
- In the dashboard: AdmiralAI shows where you are in the period, for example "$1.20 of $5.00 included this month".
See AdmiralAI for the rate limits and data handling.
When a Feature Is Not Enabled
The dashboard shows the feature as locked, with what the add-on includes and a link to Billing (or Contact sales for Enterprise). Everything that is included keeps working.
| Feature | Without it |
|---|---|
| Telemetry | Charts, metric queries and log searches reach back 24 hours; longer ranges are locked. Log search covers one device at a time. New alert rules cannot be created or edited, and existing rules stop being evaluated until the add-on is on again (they are kept, and can still be deleted). Alerts are not delivered to webhooks; platform alerts still notify in the app. API tokens and service accounts cannot query telemetry. |
| Signature policy (Enterprise) | Signature policies cannot be viewed or set, and devices do not enforce one. Saved policies are kept and apply again when the account is Enterprise. |
| USB policy (Enterprise) | USB policies cannot be viewed or set, and devices run with no USB policy. The list of attached USB devices is still shown. Saved policies are kept and apply again when the account is Enterprise. |
| Audit log | The audit log is not available. Actions are still recorded. |
| AirDetect | The fleet's AirDetect pages offer Enable AirDetect. |
Turning an add-on on or off, or a change of Enterprise status, takes effect within about a minute. Devices receive the new signature or USB policy on their next update from the platform.
For API Users
A request for a feature the organisation has not enabled returns HTTP 402 Payment Required, with the header X-Admiral-Billing-Required naming the feature and a body like:
{
"success": false,
"code": 402,
"msg": "History beyond the last 24 hours requires the Telemetry add-on.",
"data": {
"error": "billing_required",
"feature": "telemetry",
"reason": "telemetry_window",
"self_serve": true,
"free_window_hours": 24,
"upgrade_url": "/billing?feature=telemetry",
"message": "History beyond the last 24 hours requires the Telemetry add-on."
}
}
feature | Meaning |
|---|---|
telemetry | Telemetry add-on |
signature_policy | Enterprise account (self_serve is false) |
usb_policy | Enterprise account (self_serve is false) |
audit_log | Enterprise account (self_serve is false) |
airdetect | AirDetect is not enabled on the fleet, or the account is suspended |
reason | Meaning |
|---|---|
feature_not_enabled | The add-on is off. Enable it in Billing. |
telemetry_window | The query reaches further back than the last 24 hours. |
telemetry_scope | The query needs the add-on, for example a log search across more than one device. |
telemetry_api | Telemetry was queried with an API token or service account. |
enterprise_required | The feature needs an Enterprise account. |
feature_fleet_scoped | Enable the feature on the fleet. |
account_suspended | The account is suspended for billing. |
Read and change add-ons with:
| Endpoint | Purpose |
|---|---|
GET /v1/billing/features | What is enabled for the organisation, whether it is Enterprise, and the free telemetry window. |
PUT /v1/billing/features/{feature} | Turn telemetry on or off with {"enabled": true}. Requires the Manage billing capability (billing.admin). Enterprise features answer 400. |