Iridium pricing that rewards real usage

Satellite telemetry pricing built to be clear, scalable, and easier to trust.

Our pricing model is designed to match how your devices actually transmit data. You get a monthly service plan for each device, a clear included data allowance, and smooth overage pricing that scales with usage instead of punishing small changes with rigid pricing cliffs.

How usage is calculated

Transmit rate

How often each device sends a message.

Payload size

The number of bytes in each message, subject to the plan’s minimum billable size.

Deployment duration

How long the devices remain active during the billing period.

Included allowance

The plan’s baseline data is consumed first before any overage is charged.

This approach keeps pricing aligned with real telemetry behavior instead of abstract assumptions. It also makes it easier to model how changes in interval, payload size, or fleet size affect cost.

Why this beats rigid tier pricing

A common competitor-style approach is to place customers into fixed usage brackets. That can work until a small increase in telemetry pushes you over a boundary and creates a sudden change in effective cost. Our model is designed to avoid those pricing cliffs.

ModelUsage RangePrice BehaviorCustomer Impact
Rigid tier style0–25kPrice AGood until a small change in payload or interval suddenly pushes you higher.
Rigid tier style25k–100kPrice BCosts can jump at thresholds even when real-world usage changes only slightly.
Rigid tier style100k+Price CYou are forced to adapt your deployment to pricing brackets instead of the reverse.
Our smooth modelAny usage levelContinuously adjusted effective rateNo pricing cliffs. Your cost scales more naturally with actual telemetry behavior.

Our IMT (9704) plan details

Monthly pricing below reflects each IMT service plan.

PlanIncluded DataMonthlyMinimum Message SizeTypical Best Fit
IMT-0P0 kB$1575 bytesDevelopment, bring-up, sparse telemetry
IMT-25P25 kB$1925 bytesLow-frequency monitoring
IMT-50P50 kB$2325 bytesPilot deployments and periodic reporting
IMT-100P100 kB$2725 bytesGrowing sensor deployments
IMT-250P250 kB$3025 bytesLarger sensors and more frequent updates
IMT-500P500 kB$3825 bytesFleet deployments and richer payloads
IMT-1MBP1,000 kB$4525 bytesHigh-volume telemetry and image/audio bursts
IMT-2MBP2,000 kB$6825 bytesDense fleets and production-scale deployments

IMT overage pricing that improves with scale

Most telemetry providers rely on rigid pricing brackets. We do not. Instead, our effective overage rate trends downward as usage grows. That means you can increase sampling frequency, add richer payloads, or expand your device count without feeling forced into abrupt pricing jumps.

Monthly OverageIMT-0P to IMT-100PIMT-250P to IMT-2MBPWhat it means
No overage$0$0Stay within included data and pay only the monthly plan price.
0 to 2,500 bytes$0.50/kB (max)$0.30/kB (max)Light overage is billed at a standard rate with no sudden plan change required.
2,501 bytes to 25 kBLinearly decreases to $0.30/kBLinearly decreases to $0.18/kBAs usage grows, your effective overage rate drops instead of jumping to a harsher tier.
25 kB to 250 kBLinearly decreases to $0.27/kB (min)Linearly decreases to $0.16/kB (min)Heavy usage trends toward your lowest effective rate for better fleet economics.

Example scenarios

Simple examples customers can quickly understand.

Example Scenario 1

Small Device Deployment

Device transmits 10 kB above IMT-25P

10 kB × $0.425 = $4.25

Perfect for low-frequency or pilot deployments that only occasionally exceed the included allowance.

Example Scenario 2

Moderate Sensor Deployment

Device transmits 80 kB above IMT-100P

80 kB × $0.29 = $23.20

As data grows, the effective overage rate softens, helping avoid expensive jumps.

Example Scenario 3

Large Fleet Deployment

Device transmits 500 kB above IMT-1MBP

500 kB × $0.16 = $80.00

Large deployments get fleet-friendly economics that remain competitive as usage scales.

Our SBD (9602) plan details

Monthly pricing below reflects each 9602 SBD service plan.

PlanIncluded DataMonthlyMinimum Message SizeTypical Best Fit
Plan A0 bytes$15.0030 bytesVery low usage devices with infrequent transmissions.
Plan B12,000 bytes$20.0010 bytesLight-use deployments that need a small included data bucket.
Plan 1717,000 bytes$23.0010 bytesModerate telemetry usage with a bit more included headroom.
Plan 3030,000 bytes$38.0010 bytesHigher-usage SBD deployments that benefit from larger included data.

SBD overage pricing that improves with scale

Most SBD pricing models rely on hard thresholds or flat markups that do not reward growth very well. Ours is different. As monthly overage increases, the effective margin decreases smoothly across defined inflection points. That means you can transmit more often, send richer payloads, or scale your fleet without getting punished by sudden pricing jumps.

Monthly OverageMost SBD MarginsPlan 17 MarginWhat it means
0 to 2,500 bytesStandard telemetry pricing $1.50/kB (max)Standard telemetry pricing $2.00/kB (max)For very small amounts of overage, pricing carries the highest margin. This keeps low-volume deployments simple while still covering the operational cost of very small billing increments.
2,501 to 25,000 bytesLinearly decreases to $0.90/kBLinearly decreases to $1.20/kBAs monthly overage grows through this range, the effective markup steadily drops. This rewards moderate growth instead of penalizing you with abrupt pricing cliffs.
25,001 to 250,000 bytesLinearly decreases to $0.79/kbLinearly decreases to $1.05/kBAt larger overage volumes, pricing becomes much more efficient. This is where higher-frequency telemetry, richer payloads, and larger fleets start benefiting from real scale economics.
250,000+ bytes$0.79 (min)$1.05 (min)Once usage is consistently high, the markup reaches its floor and remains stable. That gives large deployments predictable pricing and protects customers from runaway marginal cost increases.

Choosing the right plan

Because telemetry behavior varies from one deployment to another, we evaluate your device count, payload size, and transmit frequency to recommend the plan that minimizes total cost while still supporting your operational needs.

The result is a pricing structure that adapts to your deployment instead of forcing your deployment to adapt to the pricing model.