Does Onomondo have coverage in Spain?

Yes, Onomondo offers Spain coverage through its partner network. The operational difference vs iot.cards isn't "yes or no coverage" but the model: Onomondo abstracts the underlying carrier under its "single network", whereas iot.cards publicly exposes Movistar, Vodafone and Orange with documented multi-IMSI. If your integrator needs to audit which carrier serves each SIM, or configure per-carrier preference policy, iot.cards does that natively. If you'd rather not worry about it, Onomondo simplifies.

Which has the better network abstraction?

Onomondo has made the "single global network" abstraction its main proposition. It's very useful for teams that don't want to think about individual carriers. iot.cards prefers transparency: the list of underlying carriers is documented, per-SIM preference policy is configurable, and the portal shows it. They are two legitimate philosophies — abstraction vs control — and the decision depends on what your operations team prefers.

What about regulated metering?

Here iot.cards has a clear advantage from documented operational experience in PRIME, G3-PLC and Meters & More deployments, ICCID-keyed traceability for regulatory reporting, dedicated private APN to the DSO, private static IP per meter. Onomondo doesn't publish that specific operational experience in the Spanish market. For a Spanish electricity distributor under regulator scrutiny, it matters.

What about private APN / static IP?

Both offer them but with different positioning. iot.cards offers them as a standard layer contractable from the first SIM (no enterprise committee), whereas in Onomondo private APN and static IP are enterprise products. For integrators who want to validate private APN on a 5-SIM pilot before scaling, iot.cards reduces commercial friction. For large fleets with annual commitment, both are viable.

Does Onomondo invoice include Spanish VAT?

Onomondo invoices from Denmark. For Spanish companies that need an invoice with Spanish VAT charged (not the EU intra-community reverse-charge scheme), iot.cards (Kore Logic SL, Spanish CIF) issues a local invoice. For companies with a finance department comfortable with the European intra-community scheme, it's not a problem. For Spanish SMBs with local accounting advisors, it simplifies things.

Spanish-language support?

Onomondo operates in English (and Danish). iot.cards has an engineering team in Seville responding in Spanish by phone and email, with technical onboarding included from the first SIM. For Spanish integrators with non-English-speaking teams, it matters.

When should I NOT pick iot.cards?

If your deployment is 80% Netherlands, Belgium, Germany, Denmark and only 20% Spain, Onomondo has better cultural and market fit. If your team works in English and the "single network" abstraction is what you value most (vs granular per-carrier control), Onomondo scores higher. If your end client is a European multinational with no Spain-vendor requirements, both deliver and the decision goes on DX, abstraction and price.

Can I migrate between Onomondo and iot.cards?

Technically yes, but it requires a physical SIM swap (different IMSI). If in doubt, we recommend starting with a 5-10% pilot at each vendor to validate the real usage profile (per-location coverage, latency, billing) before mass deployment. Especially with solderable MFF2, migration costs field time.

Commercial comparison

Onomondo vs iot.cards

How to choose between Onomondo's cloud-native IoT SIM and iot.cards' multi-carrier IoT SIM. Both are modern IoT MVNOs with REST API and dashboard. The real difference is the model: Onomondo is Danish, operator-agnostic and sells its "single global network" as an abstraction; iot.cards is Spain-native and publishes the underlying national carriers (Movistar, Vodafone, Orange) for transparency. Here's when each one fits.

Request trial SIM Talk to an expert

Quick summary

Onomondo fits if you value a "single global network" abstraction without thinking about which carrier sits underneath, your deployment is pan-European or multi-region with no specific Spain focus, and you prefer not to know which carriers the SIM uses. iot.cards is the reasonable choice if you deploy in Spain and need documented tri-carrier multi-IMSI (Movistar+Vodafone+Orange) as a commercial differentiator, private APN or static IP as a standard layer, engineering support, or if your vertical (regulated metering, Telefónica/Iberdrola partnership) requires a vendor with legal and operational presence in the Spanish market since 2013.

Side-by-side feature comparison

Same modern cloud-API approach; different market focus, operator transparency and support stack.

	Onomondo	iot.cards
Origin and focus	Danish IoT MVNO (Copenhagen). Cloud-native and operator-agnostic positioning; sells the "single network" abstraction.	Spanish IoT MVNO (Seville). Spain-native positioning with public operational relationships with Movistar, Vodafone and Orange since 2013.
Spain coverage	Spain coverage available via partners. Onomondo doesn't publish a tri-carrier agreement with Movistar/Vodafone/Orange as a commercial differentiator.	Multi-IMSI with documented access to Movistar, Vodafone and Orange in Spain. Automatic switching between the three national networks, per-SIM preference policy.
Carrier transparency	"Single network" model — the customer typically doesn't see which underlying carrier serves each SIM. Good for abstraction; less good for per-carrier coverage audit.	Public list of underlying carriers per country. Per-carrier preference and exclusion policy. Traceable in the portal and via API.
Commercial model	Pay-per-MB in EUR. No lock-in. Public pricing in the dashboard.	Pay-as-you-go (€0.005/MB at low usage), volume-discounted bundles, and enterprise tariff with SLA. No lock-in, no per-SIM minimum.
Private APN	Available under enterprise plan.	Dedicated APN with your CIDR range + IPSec/WireGuard tunnel into your VPC, contractable as a standard layer (not gated behind enterprise sales).
Static IP	Available under enterprise plan.	Static IPv4 (public or private) per SIM, contractable from the first unit as a per-SIM add-on.
Developer experience	Modern dashboard, documented REST API, webhooks, clean cloud-API focus. Good English documentation.	Documented REST API with HMAC-signed webhooks and ICCID idempotency. Bilingual ES/EN management portal. More enterprise-focused than developer-CLI focused.
Technical support	Email support in English (and Danish). Self-service via dashboard.	Engineering team in Seville, phone and email support in Spanish, English and Portuguese. Technical onboarding from day one, regardless of account size.
Spanish regulated verticals	No specific focus on Spanish regulated verticals (regulator-monitored metering, national critical infrastructure). Suited to generic pan-European cases.	Documented operational experience in metering deployments (PRIME/G3-PLC/Meters & More), named partnerships (Iberdrola/Telefónica), ICCID-keyed traceability for regulatory audit.
Spanish regulatory compliance	Danish company; GDPR compliance at European level. No legal entity in Spain.	Spanish company (Kore Logic SL, CIF B90463662), LSSI-CE + LOPDGDD + GDPR compliance. Matters if your client requires a vendor with legal presence in Spain.
Billing model	Monthly invoice from Denmark in EUR. Spanish customer applies the EU intra-community reverse-charge scheme.	Monthly invoice for actual pooled consumption in EUR, issued from Spain (Spanish VAT charged to Spain customers).

When to choose which

Choose Onomondo if…

Your deployment is pan-European or multi-region with no strong Spain focus.
You want a "single global network" abstraction and don't need to audit which underlying carrier each SIM uses.
Your team works in English and dashboard self-service is more useful than human Spanish-language onboarding.
You don't need specific anchoring to Movistar, Vodafone or Orange.
Your use case isn't regulated in Spain (no metering compliance, no Spanish critical infrastructure).
The vendor can be outside Spain without your legal department raising flags.

Choose iot.cards if…

You deploy mostly in Spain and need real tri-carrier multi-IMSI (Movistar+Vodafone+Orange) as a differentiator.
You need to know which underlying carrier serves each SIM, with configurable preference and exclusion policy.
You need private APN or static IP as a standard layer contractable from the first unit, not a gated enterprise module.
Your client or legal department requires a vendor with legal presence in Spain (Spanish-VAT invoice, Spanish-law contract, Spanish-language support).
Your vertical is regulated metering, healthcare, or Telefónica/Iberdrola partner contexts.
You need human technical onboarding from the first SIM and ICCID-keyed traceability for regulatory audit.

Frequently asked questions

Does Onomondo have coverage in Spain?: Yes, Onomondo offers Spain coverage through its partner network. The operational difference vs iot.cards isn't "yes or no coverage" but the model: Onomondo abstracts the underlying carrier under its "single network", whereas iot.cards publicly exposes Movistar, Vodafone and Orange with documented multi-IMSI. If your integrator needs to audit which carrier serves each SIM, or configure per-carrier preference policy, iot.cards does that natively. If you'd rather not worry about it, Onomondo simplifies.
Which has the better network abstraction?: Onomondo has made the "single global network" abstraction its main proposition. It's very useful for teams that don't want to think about individual carriers. iot.cards prefers transparency: the list of underlying carriers is documented, per-SIM preference policy is configurable, and the portal shows it. They are two legitimate philosophies — abstraction vs control — and the decision depends on what your operations team prefers.
What about regulated metering?: Here iot.cards has a clear advantage from documented operational experience in PRIME, G3-PLC and Meters & More deployments, ICCID-keyed traceability for regulatory reporting, dedicated private APN to the DSO, private static IP per meter. Onomondo doesn't publish that specific operational experience in the Spanish market. For a Spanish electricity distributor under regulator scrutiny, it matters.
What about private APN / static IP?: Both offer them but with different positioning. iot.cards offers them as a standard layer contractable from the first SIM (no enterprise committee), whereas in Onomondo private APN and static IP are enterprise products. For integrators who want to validate private APN on a 5-SIM pilot before scaling, iot.cards reduces commercial friction. For large fleets with annual commitment, both are viable.
Does Onomondo invoice include Spanish VAT?: Onomondo invoices from Denmark. For Spanish companies that need an invoice with Spanish VAT charged (not the EU intra-community reverse-charge scheme), iot.cards (Kore Logic SL, Spanish CIF) issues a local invoice. For companies with a finance department comfortable with the European intra-community scheme, it's not a problem. For Spanish SMBs with local accounting advisors, it simplifies things.
Spanish-language support?: Onomondo operates in English (and Danish). iot.cards has an engineering team in Seville responding in Spanish by phone and email, with technical onboarding included from the first SIM. For Spanish integrators with non-English-speaking teams, it matters.
When should I NOT pick iot.cards?: If your deployment is 80% Netherlands, Belgium, Germany, Denmark and only 20% Spain, Onomondo has better cultural and market fit. If your team works in English and the "single network" abstraction is what you value most (vs granular per-carrier control), Onomondo scores higher. If your end client is a European multinational with no Spain-vendor requirements, both deliver and the decision goes on DX, abstraction and price.
Can I migrate between Onomondo and iot.cards?: Technically yes, but it requires a physical SIM swap (different IMSI). If in doubt, we recommend starting with a 5-10% pilot at each vendor to validate the real usage profile (per-location coverage, latency, billing) before mass deployment. Especially with solderable MFF2, migration costs field time.

Want us to size your case?

Tell us how many devices, what they consume, what your requirements are (APN, IP, regulated vertical) and where they're deployed (Spain, EU, international). We'll honestly tell you which fits better — even if the answer is "stay with Onomondo".