Short answer: Soracom sells cellular data access for devices — a SIM and eSIM catalog, over-the-air provisioning, fleet dashboards, per-megabyte or pooled metering — and every channel a fleet team touches lives on a second platform. Devotel Orbit ships that same connectivity surface honestly (the bearer carries data only, never voice or text) and puts the account's communication channels next to it: phone numbers, number lookup, programmable SMS and WhatsApp, email, voice, AI agents, and a built-in contact center on one pay-as-you-go bill. This head-to-head scores the named vendor on the same rows the public /compare/soracom page publishes, and says plainly where each side wins.
1. What Soracom sells, and where the catalog stops
Soracom is a cellular IoT connectivity provider: you buy SIMs or eSIMs, activate them over the air, manage the fleet from a dashboard, and meter data per megabyte or through a pooled plan. That surface is complete and honest — and it ends at the data bearer. Soracom does not publish a voice, messaging, email, video, or contact-center product on the account, so any communication the fleet operation needs arrives as a second vendor.
Orbit's NaaS pillar answers the same connectivity surface: a data-only esim or iot-sim catalog filterable by country and form factor, over-the-air provisioning with a GSMA-standard pairing code per ICCID, per-SIM quota caps, a fleet-wide usage rollup, and a per-plan cost estimate that returns the estimated usage total plus the monthly platform fee before any device order lands. The bearer decision stays parity. The account decision is the whole comparison.
2. The deviations that decide the evaluation
The named-vendor comparison opens where the generic archetype comparison could not go — into the specific patterns a Soracom shortlist weighs:
- Metering model. Soracom publishes per-megabyte and pooled tiers. Orbit's catalog discloses the metering model on every plan entry — per-megabyte rate or pooled data, plus any monthly platform fee — so the cost comparison runs against your fleet's actual usage curve, not a sticker rate.
- Lookup patterns. A connectivity-only account has no numbering layer, so "validate this coordinator's phone number" becomes a hard lookup — a full HLR dip — on a second vendor's account. On Orbit the same account runs phone numbers and number lookup (validity, carrier, line type, porting history, SIM-swap signal), so one lookup call cleans one sending list across every channel the fleet uses, and soft validation (cached line-type checks before a first send) never has to leave the account.
- The second vendor. The pattern repeats across fleet evaluations: the device team concludes "our comms platform doesn't need IoT data," buys SIMs from Soracom, and books connectivity as solved. Then the field operator needs an SMS when a tracker goes dark, the delivery recipient needs a WhatsApp notification, the support line needs an AI voice agent after hours — and every channel arrives as a second vendor, a second account, a second bill, a second provisioning contract.
Orbit's eSIM and IoT data plans sit in the same pay-as-you-go wallet as SMS and voice: one account, one usage bill, one contract. A fleet that already crosses channels removes the second vendor instead of stacking it.
3. The evaluation matrix: honest rows from /compare/soracom
The rows below mirror the public comparison table (retrieved September 2026). Where Soracom genuinely matches, the cell says yes on both sides; the split only opens above the connectivity core.
| Criterion | Devotel Orbit | Soracom |
|---|---|---|
| Data-only eSIM / IoT SIM catalog (filterable by country & form factor) | Yes | Yes |
| Over-the-air eSIM provisioning (GSMA pairing code per ICCID) | Yes | Yes |
| Per-SIM quota controls with a fleet-wide usage rollup | Yes | Yes |
| Coverage and cost estimate checked before a device commitment | Yes | Yes |
| Per-megabyte and pooled metering models, platform fee disclosed | Yes | Yes |
| Data-only plans by contract (no voice/SMS over the cellular bearer) | Yes | Yes |
| Phone numbers (provision, port, manage) on the same account | Yes | No |
| Number lookup (HLR, SIM-swap signal) on the same account | Yes | No |
| Programmable SMS and messaging on the same account | Yes | No |
| WhatsApp, RCS, and email channels on the same account | Yes | No |
| Voice, AI agents, and a built-in contact center on the same account | Yes | No |
| One pay-as-you-go bill across connectivity and communications | Yes | No (connectivity only) |
The Soracom alternatives buyer's guide weighs Soracom against Hologram, EMnify, and 1NCE one by one on metering model, coverage, and form factor. This head-to-head is the named-vendor page that guide and the generic /compare/connectivity-iot-provider archetype both point into.
4. An IoT fleet case study: the delivery tracker operation
Take a last-mile delivery fleet: two thousand trackers, a field operations team, a recipient-facing notification layer. On Soracom the trackers report over the data bearer — complete. The moment a tracker goes dark, the field operator gets an SMS from a second vendor's account; the recipient's delivery-window WhatsApp comes from a third; the after-hours support line forwards to a fourth. Four vendors, four invoices, four provisioning contracts, and a number-validation step that runs against whichever vendor the coordinator console was wired to.
On Orbit the trackers run the same data-only SIMs. The operator SMS, the recipient WhatsApp, and the AI voice agent answering the support line all run on the same account the SIMs live on — and the number lookup that validates each recipient's phone number before the first notification is one API call against the same account, not a hard lookup routed through a second vendor's console. The consolidation is worth exactly as much as the second vendor it removes: this fleet removed three.
5. Limits: what this comparison does not claim
Two boundaries stay honest. First, Orbit's data plans are data-only by contract — voice: false and sms: false on the bearer, the same honesty rule Soracom publishes — so the comparison never claims a bearer capability gap on either side. Second, the per-plan costs this page cites come from the plan catalog's own disclosed entries and the NaaS pillar cost-estimate surface; the page makes no coverage claim beyond what the catalog's per-country flags return, and Soracom's published tiers change at the vendor's discretion. Run the cost-estimate call with your fleet's megabyte volume and country before the decision, not after.
6. The verdict — one account, or a data plan that stays a data plan
Pick Soracom when the fleet genuinely never communicates: sensors that only report, trackers that only transmit, a backup link that only fails over — and no operator, recipient, or support channel ever needs a number behind it. A dedicated connectivity vendor serving a fleet that will never leave the data plane is a defensible shape, and on some metering curves the cheapest honest answer.
Pick Devotel Orbit when the fleet operation already crosses channels, or will: the tracker fleet's data plus the SMS to the field team, the WhatsApp notification to the recipient, the AI voice agent answering the support line, and the SIM-swap-safe number lookup validating the contact before the first send — all on one account, with tenant-configurable consent, quiet hours, and retention policies applied per channel, and one pay-as-you-go bill. The deal-breaker test is the second vendor: if one exists today, the one-bill shape is what the evaluation should settle.
Frequently asked questions
Does Soracom run voice or SMS on the SIM itself?
No — and that boundary holds on Orbit too. Every plan in Orbit's catalog is data-only by contract: the cellular bearer carries data, never voice or text. When a fleet needs reachability, it runs through Orbit's messaging and voice pillars on real phone numbers, on the same account, rather than a cellular-SMS hack on the data bearer.
How is the Soracom head-to-head different from the generic connectivity archetype page?
The archetype page (/compare/connectivity-iot-provider) deliberately names no vendor: it scores connectivity-only versus connectivity-plus-communications as a class. This page is the named-vendor twin — Soracom's public SIM/eSIM catalog, over-the-air activation, and published data tiers weighed row by row — so the "Orbit vs Soracom" query gets a page that answers it directly instead of a generic archetype that happens to include Soracom's shape.
Can Orbit replace a hard number lookup with a soft one?
On the same account, yes. A hard lookup — a full HLR dip — costs a real lookup call every time. Because Orbit runs phone numbers, lookup, and the messaging channels themselves on one account, a soft check (cached line-type and porting-validation data Orbit already holds) can clean a sending list before the first message, and the hard lookup is reserved for numbers the soft check cannot resolve. Either way the lookup never leaves the account.
How does Orbit price eSIM and IoT data compared to Soracom?
Orbit prices per megabyte, plus a monthly platform fee where a plan carries one — and the plan catalog's cost-estimate endpoint returns the estimated usage cost plus the platform fee for a given megabyte volume and country before any SIM ships. Soracom publishes its own per-megabyte and pooled tiers; the honest comparison runs against your fleet's usage curve, with both vendors' disclosed rate cards in front of you. Every Orbit channel bills to the same pay-as-you-go account, so a team replacing Soracom plus a messaging vendor plus a voice vendor trades three invoices for one.
Published 21 September 2026.