Comparison
Overview
Company snapshot and where each provider is based.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| What it is | Danish SMS gateway and messaging platform by ONLINECITY.IO offering SMS, RCS and email APIs with pay-as-you-go pricing and EU data hosting. | Omnichannel business messaging platform and API from Cyprus-based Intergo Telecom for sending SMS, Viber, WhatsApp, RCS and Telegram messages worldwide. |
| Founded | 1999 | 2016 |
| Ownership | private | private |
| Employees | 11-50 | 51-200 |
| HQ city | Odense | Paphos |
| HQ country | Denmark (EU) | Cyprus (EU) |
What's the differenceGatewayAPI edges ahead on the overall messaging.dev Score (54 vs 49). GatewayAPI is private and headquartered in Odense, Denmark (EU); SMS.to is private and based in Paphos, Cyprus (EU).
Channels
Which messaging channels each provider can send and receive on.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| SMS | Yes | Yes |
| MMS | No | No |
| RCS | Yes | Yes |
| No | Yes | |
| Viber | No | Yes |
| Facebook Messenger | No | No |
| Telegram | No | Yes |
| Apple Messages for Business | No | No |
| Voice | No | No |
| Yes | No |
What's the differenceThey share 2 channels. GatewayAPI additionally offers Email, while SMS.to additionally offers WhatsApp, Viber, Telegram.
Developer Experience
How quickly a developer can sign up and send a first message.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| Self-service onboarding | Yes | Yes |
| Free developer credit | Test credits on request | Free trial credits on sign-up |
| Docs quality | med | med |
| Documentation | Open ↗ | Open ↗ |
| SDKs | — | PHP |
| Sandbox / test env | No | No |
| API types | REST, SMPP, Email-to-SMS | REST, SMPP |
What's the differenceOn SDKs, SMS.to adds PHP; on API types, GatewayAPI adds Email-to-SMS.
Data & Compliance
Data residency options and enterprise compliance certifications.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| EU data residency | Yes | Yes |
| US data residency | No | Yes |
| Choose region | Yes | Yes |
| GDPR | Yes | Yes |
| ISO 27001 | No | Yes |
| SOC 2 | No | No |
| HIPAA | No | No |
What's the differenceSMS.to offers US data residency, while GatewayAPI does not; SMS.to offers ISO 27001, while GatewayAPI does not.
Data Retention
How long message content and metadata are stored, and whether that is configurable.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| Retention policy | Message content, sender and recipient are stored in the traffic log for 30 days, after which records are anonymized (message content and full sender deleted, last half of the recipient number removed). An optional "secret" message class skips storage of content, sender and recipient entirely. | Customer data is retained only while the account remains open; on an account deletion request all data is deleted within 30 days. Customers can choose to have data processed only within the EU, in which case it is not transferred outside the EU; per-message content retention periods are not publicly documented in detail. |
What's the differenceGatewayAPI: Message content, sender and recipient are stored in the traffic log for 30 days, after which records are anonymized (message content and full sender deleted, last half of the recipient number removed). An optional "secret" message class skips storage of content, sender and recipient entirely. SMS.to: Customer data is retained only while the account remains open; on an account deletion request all data is deleted within 30 days. Customers can choose to have data processed only within the EU, in which case it is not transferred outside the EU; per-message content retention periods are not publicly documented in detail.
Pricing & Credits
Pricing model and the cost of a first message.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| Pricing model | Pay-as-you-go per-message pricing with prepaid credit; no monthly subscriptions or fees (except short-code countries), with negotiated discounts for high volumes. | Prepaid pay-as-you-go credit with no contracts or commitments; per-SMS rates vary by destination and volume discounts are negotiated with sales. |
| SMS starting price | From €0.0061 per SMS (standard class, cheapest destination on the public price list; e.g. €0.0401 to Denmark) | From $0.023 per SMS (advertised base rate; per-country rates via downloadable price list) |
| Free developer credit | Test credits on request | Free trial credits on sign-up |
What's the differenceGatewayAPI and SMS.to are closely matched on pricing & credits — no material differences in the tracked fields.
Reach & Reliability
Global coverage and delivery dependability.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| Countries covered | 200 | 0 |
| Direct operator connections | Yes | Yes |
| Published uptime SLA | No published SLA (99.99%+ historical uptime claimed) | No published SLA (public status page at status.sms.to) |
What's the differenceGatewayAPI leads on Countries covered (200 vs 0 for SMS.to).
Company & Trust
Independent reviews and company profile.
| Field | GatewayAPI | SMS.to |
|---|---|---|
| G2 rating | 4.9 | 4.4 |
| G2 reviews | 7 | 4 |
| Ownership | private | private |
| Employees | 11-50 | 51-200 |
What's the differenceGatewayAPI leads on G2 rating (4.9 vs 4.4 for SMS.to); GatewayAPI leads on G2 reviews (7 vs 4 for SMS.to).
Still deciding? Read the quickstart guides: