Two primary usage meters, both measured at our own edge so they can't be gamed. Direct connections, pure peer-to-peer, and self-hosting the whole fabric are free. No per-seat tax: you pay for the backbone we actually carry and the telemetry we actually collect. Secondary dimensions (egress and mailbox storage) apply only when traffic leaves the mesh or is held past your free allowance.
Not on the device, not self-reported. We bill only what crosses our infrastructure, which is also the only thing that costs us anything.
We carried a bundle across the relay fleet and delivered it to someone who was offline. This is the thing Hop uniquely does, and the only message traffic that ever bills. Measured at the relay, on proof of delivery.
We collected your device stats over the mesh, translated our compact wire format to true OTLP, and forwarded them to your stack or our console. Priced per record, so it scales with how chatty a device is. No tiers to classify.
Start from a use case or drag the inputs. Live, using the exact rate card above. Reach is driven by the share of your fleet that has no connectivity, the people only the backbone can reach.
Model covers primary Reach and Telemetry usage. Internet egress at $0.15 / GB and mailbox storage at $0.40 / GB-month apply only past your included allowance. Active devices (MAD) are counted for tenant auth, never as a per-seat fee. Figures are illustrative, the model we're finalizing for general availability, and move with your fleet's connectivity and telemetry cadence.
Run the relay and telemetry collector yourself. The hosted services are source-available under FSL-1.1-ALv2, with a non-compete on commercial hosting that converts to Apache-2.0 after two years. The protocol core, SDKs, bearers, and drivers they embed are licensed outright under Apache-2.0, with no restriction on embedding or running them for your own use.
We run the fabric. You pay the two meters and get what self-host doesn't, which is the actual reason to pay.
Billing observes the network, it never gates it. A spending limit can't take your delivery down, which is exactly what a safety or field deployment needs to hear. Metering is asynchronous and downstream, so it physically cannot stop a live message.
The paid backbone is the only thing that can ever pause, and it pauses up to free, never below.
We alert you, keep delivering, and bill the overage or let you raise it. Never a kill-switch.
The relay stops carrying your traffic, but P2P and direct connections keep working. You land on exactly the free tier, never less.
Bundles already accepted or spooled keep being carried under the same at-least-once lifetime rules as any other bundle. Account suspension only halts new acceptance; it does not purge in-flight traffic.
P2P and direct connections are always free. Start on the SDK, add the managed backbone when you need to reach the disconnected.
By starting free or using Hop, you agree to our Terms of Service and Acceptable Use Policy.