You pay for traffic, not for seats.
Numbering, wireless and orbital rates are set per jurisdiction and per site, so a single published number would be wrong for most people reading it. What does not change is how the charging works.
Everything here meters what it does — a minute, a message, a gigabyte, a terminal-month, a token. No seat licences on infrastructure, and no charge for capacity sitting idle.
A volume commitment lowers the unit rate. It is optional, it is not required to get support, and it does not gate a feature.
Where a jurisdiction requires a fee to be collected, it is collected and shown as itself. It is not folded into the rate to make the rate look lower.
A standby wireless or orbital path costs the terminal, not the capacity. You pay for the traffic on the day it is needed.
Engineering support comes with the account. A paid tier buys response times and a named engineer, not the right to open a ticket.
| Service | Unit | Notes |
|---|---|---|
| Numbers | Per number, per month | Plus per-minute or per-message usage. Rates vary by country and by range type. |
| Voice and messaging | Per minute · per message | Destination-based. Volume tiers apply automatically. |
| Wireless | Per SIM, per month + pooled data | Data pools across the fleet; unused capacity is not stranded per device. |
| Orbital | Per terminal, per month + capacity | Quoted per site: coordinate, capacity commitment and service level. |
| Inference and speech | Per token · per second of audio | Region-pinned. In-region pinning does not carry a surcharge. |
| Edge compute and storage | Per invocation · per GB-month | Storage billed in the region the data was written. |
Send us the shape of your traffic.
Countries, volumes and coordinates. A quote comes back with the rate, the service level and the provisioning time for each one.