Transactional Email
SMTP2GO
Rest of world Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sand Dune Mail Ltd · www.smtp2go.com
Report an error on this page Is this your product? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
SMTP2GO at a glance
- Vendor
- Sand Dune Mail Ltd
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention the US, Europe and Australia source, captured 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates SMTP2GO 2.5/5, the mean of 6 judges. SMTP2GO is a transactional email and SMS service from Sand Dune Mail Ltd, Christchurch, New Zealand. how scores are made
- As of
- Vendor pages captured 1 Nov 2026; evaluated by the panel 1 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
SMTP2GO is a transactional email and SMS service from Sand Dune Mail Ltd, Christchurch, New Zealand. Its strongest criterion is reliability and accounts at 6 to 7, resting on a 100% uptime guarantee crediting 5% of the monthly fee per 30 minutes of downtime up to 100%, ten data centre locations with traffic re-routing, and subaccounts on every paid plan with optional per-customer dedicated IPs and customer self-login. Pricing transparency scores 5 to 6: the free tier is fully specified (1,000 emails per month, 200 per day, no credit card) and Professional is public at $75/mo for 100,000 emails, extra emails at $0.85 per thousand. Sovereignty is weakest at 2 to 4, a genuine split: judges weighed the New Zealand contracting entity against the privacy policy's pledge that EEA users' personal data is stored only within the EEA, and we found no public information on subprocessors or a data processing agreement. Deliverability spans 4 to 6 on similar lines — stated reputation tools, no public information on DMARC or warm-up. Sending API and data and security hold at 4.
Speaks for it
- Reliability and accounts scores run 6 to 7 on a written 100% uptime guarantee crediting 5% of the monthly fee per 30 minutes of downtime, up to 100% of the monthly fee.
- Subaccounts on every paid plan, with optional dedicated IPs per customer and customer self-login, aimed at web design agency resellers.
- Free tier fully specified — 1,000 emails per month, 200 per day, no credit card — plus a public Professional plan at $75/mo for 100,000 emails with extra emails at $0.85 per thousand.
- Concrete retention terms: headers kept 35 days and viewable in the control panel, one email per thousand stored 35 days with storage disableable on request.
- Public status page with a historical performance graph, network monitored every minute, and traffic re-routing across ten data centre locations.
Held against it
- Sovereignty scores span 2 to 4: contracting is with Sand Dune Mail Ltd under New Zealand law, and we found no public information on subprocessors, a data processing agreement or an EU representative.
- Sending API scores hold at 4, with no public information found on stored templates, attachments, batch sending, idempotency keys or a sandbox mode.
- Data and security scores hold at 4, with no public information found on two-factor authentication, scoped API keys, encryption at rest or certifications.
- Deliverability scores span 4 to 6, with no public information found on DMARC set-up, IP warm-up or separating transactional from marketing streams.
- The terms reserve the right to change fees at any time without advance warning, and we found no public information on VAT treatment or a minimum term.
Best for
- You run a web design agency or managed service provider and need per-customer subaccounts, customer self-login and optional dedicated IPs per client.
- You want a fully specified free tier — 1,000 emails per month, 200 per day, no credit card required — before committing to the $75/mo Professional plan.
- You answer for uptime: the written 100% guarantee, 5% credit per 30 minutes of downtime and the public status page with a historical performance graph give you paper for on-call reviews.
- Your compliance team values written retention terms: headers 35 days, one email per thousand stored 35 days with storage disableable on request, GDPR access and deletion answered within 30 days.
Avoid if
- You must contract with an EU entity, or need a published data processing agreement and named subprocessors — the terms choose New Zealand law and we found no public information on either.
- Your platform depends on stored templates, batch sending, idempotency keys or a sandbox mode that never delivers — ask the vendor: the public pages we read do not show it
- Your security review requires two-factor authentication, scoped API keys, encryption at rest or certifications — we found no public information on any of these.
- You need firm annual costs — we found no public information on the annual price or VAT treatment, and the terms reserve the right to change fees at any time without advance warning.
The scores
| Criterion | Panel median |
|---|---|
| Sending API, SMTP & developer experience | 2 of 5 |
| Deliverability & sender reputation | 2.5 of 5 |
| Message logs, events & webhooks | 2 of 5 |
| Message data, retention & security | 2 of 5 |
| Reliability, accounts & support | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 3 of 5 |
Sending API, SMTP & developer experience
Show reasoningHide reasoning
How this is scored
How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.
0 — Not a sending service; an application cannot send email through it by API or SMTP.
3 — An API or SMTP credentials to send a message; SDKs, templates, limits and a test mode are basic or not described.
5 — A documented REST API and SMTP relay, official SDKs for several named languages, stored templates with variables, attachments and batch sending, rate limits stated, a sandbox or test mode, and quick-start guides for named frameworks.
8 — An API reference with every endpoint and error code, idempotency keys, scheduled sending, template versions and a template language documented, inbound email parsed to a webhook, an OpenAPI specification or official CLI, framework drivers maintained by the vendor, and a migration guide from named competitors.
10 — An API a team builds its product on: versioning and deprecation policy published, backward compatibility stated, full parity between API and SMTP features, local or staging test tooling that mirrors production, and every limit, timeout and retry behaviour documented.
The SaaS Developer
The SMTP relay and a REST API at api.smtp2go.com/v3/email/send are documented with endpoints, response codes and rate limiting, and there are official libraries and code examples in JavaScript, Node, PHP, Ruby and Python. But we found no public information on stored templates with variables, batch sending, idempotency keys, scheduled sending, a test mode that never reaches a real inbox, or an official Laravel driver — and after replacing our mail driver once already, I will not do it again on per-language examples alone. 3 7 11 12
The Platform Engineer
There is a real API here: endpoints, response codes and rate limiting documented, official code examples in JavaScript, Node.js, PHP, Ruby and Python, plus an SMTP relay and webhooks — enough to wire up our sending code. What I could not find is templates, attachments, batch sending, idempotency keys or scheduled sends, and the spam-filter preview plus the Professional plan's email testing tools are the closest the documentation comes to a test mode. 3 6 7 11 12
The Shop Operator
For our shop the practical route is the SMTP relay or the documented HTTP send endpoint, with official libraries and code examples covering PHP among five languages and rate limiting documented in the API docs. We found no public information on stored templates, attachments, batch sending, a non-delivering sandbox or inbound parsing, and among the named integrations only WordPress, Slack and cPanel/WHM appear — no Shopware plugin. 7 3 11 12
The Data Protection Officer
A documented REST API with a send endpoint and an SMTP relay, official libraries and full code examples in JavaScript, NodeJS, PHP, Ruby and Python, and documentation sections covering endpoints, response codes and rate limiting. We found no public information on stored templates, attachments, batch sending, a sandbox or test mode, inbound email parsing or idempotency, so this sits below the level where a complete developer platform is evidenced. 7 11 12
The Agency Lead
The sending path is real for both integration styles my teams use: a documented REST API with an example endpoint, plus Endpoints, Response Codes and Rate Limiting sections in the developer docs, an SMTP relay, official libraries and full code examples in JavaScript, Node, PHP, Ruby and Python. What I could not find on the captured pages is stored templates, attachments, batch sending, a sandbox mode or inbound parsing, so I cannot place it higher. 7 12 3 11
The Skeptic
There is a documented REST endpoint for sending, an SMTP relay, official libraries with code examples in JavaScript, NodeJS, PHP, Ruby and Python, webhooks, and an API reference covering endpoints, response codes and rate limiting. We found no public information on stored templates, attachments, batch sending, idempotency keys, scheduled sending or a sandbox mode, and the email testing tools on the Professional plan are spam-filter and client previews rather than a mode that does not deliver. 3 6 7 12
Deliverability & sender reputation
Show reasoningHide reasoning
How this is scored
What the vendor does so the mail reaches the inbox: guided SPF, DKIM and DMARC set-up with a custom return path and tracking domain, shared IP pools and how senders on them are vetted and policed, dedicated IPs with automatic warm-up, transactional and bulk mail kept on separate streams or IP pools, bounces, complaints and unsubscribes turned into suppressions automatically, feedback loops with mailbox providers, blocklist and DMARC monitoring, compliance with the Gmail and Yahoo bulk-sender rules, and published delivery times or inbox placement with their method.
0 — No sender authentication and no bounce handling; mail goes out from shared addresses with no reputation management at all.
3 — SPF and DKIM can be set up and bounces are recorded; IP policy, stream separation and suppressions are basic or not described.
5 — Guided SPF, DKIM and DMARC set-up with a custom return path, shared IPs with a stated sender vetting policy, dedicated IPs available, automatic suppression of hard bounces and complaints, transactional and marketing mail separated by stream or IP pool, and deliverability guidance in the documentation.
8 — Dedicated IPs with automatic warm-up and pool management, a stated acceptable-use and vetting process for shared pools, feedback loops and blocklist monitoring, DMARC reports, BIMI or custom tracking domains, compliance with the Gmail and Yahoo sender requirements stated, delivery times published, and access to deliverability experts.
10 — Deliverability that can be verified: delivery time and bounce rates per mailbox provider published continuously with their method, inbox placement testing included, pool reputation shown to the customer, and a documented escalation path with mailbox providers.
The SaaS Developer
Guided SPF and DKIM set-up ("no prior knowledge required"), automatic blacklist monitoring, spam-trap detection, feedback loops with Yahoo, AOL and Hotmail, bounce and spam tracking, and dedicated IPs are all on the record. We found no public information on DMARC set-up, dedicated-IP warm-up, how senders on shared IPs are vetted, or keeping transactional and marketing mail on separate streams — and this service markets both transactional and marketing sending in one product. 2 3 6 8 11
The Platform Engineer
Guided SPF and DKIM set-up, dedicated IPs including per-subaccount ones, feedback loops with providers such as Yahoo, AOL and Hotmail, automatic blacklist monitoring and spam-trap detection, and an enforceable acceptable-use regime in the terms (100% opt-in lists, prohibited industries, termination for spam) make a real deliverability story. I found no public information on DMARC set-up, custom return paths, IP warm-up, separation of transactional from marketing mail, or published delivery times per mailbox provider — the last is exactly what I check during an incident. 3 4 6 9 13
The Shop Operator
This is what I need day to day: SPF and DKIM records are created and maintained "no prior knowledge required", the vendor handles reverse DNS, ISP throttling and feedback loops with Yahoo, AOL and Hotmail, and blacklist monitoring, spam-trap detection, unsubscribes and bounce-rate alerts are on every plan, with a dedicated IP on the paid tier. We found no public information on DMARC set-up, a custom return path, separate streams or pools for order mail versus newsletters, or published delivery times. 3 6 12 8 1 2
The Data Protection Officer
Guided SPF and DKIM set-up, dedicated IP addresses, feedback loops with major providers, blacklist monitoring, spam-trap detection and spam-filter testing are stated, backed by strict opt-in list rules in the terms. We found no public information on DMARC set-up, a custom return path, a vetting policy for shared IP pools, or separation of transactional and marketing streams, so the reputation machinery is only partly documented. 4 6 11 12
The Agency Lead
Feedback loops with providers like Yahoo, AOL and Hotmail, automatic blacklist monitoring, spam-trap detection and bounce and spam tracking are stated for every plan, dedicated IPs exist and can even be assigned to a single client subaccount, and the opt-in list rules and prohibited industries show the shared pool is policed. We found no public information on DMARC set-up, a custom return path, automatic suppression of hard bounces, or keeping transactional and marketing mail on separate streams. 6 8 12 9 2
The Skeptic
The pages state guided SPF and DKIM set-up without prior knowledge, feedback loops with Yahoo, AOL and Hotmail, automatic blacklist monitoring, spam-trap detection, bounce and spam tracking, and dedicated IPs. We found no public information on DMARC, a shared-pool vetting policy, automatic warm-up of dedicated IPs, automatic suppression of hard bounces and complaints, or separation of transactional and bulk streams — and staying a step ahead of blacklists is a slogan with no delivery-time figures or method behind it. 3 4 6 12
Message logs, events & webhooks
Show reasoningHide reasoning
How this is scored
What the team can see about each message once the application has handed it over: a message log searchable by recipient, subject, tag or message ID, the full event history (processed, delivered, deferred, bounced with the remote server's answer, opened, clicked, complained), how long logs and message content are kept, event webhooks with retries and a signature, an events API, dashboards and statistics per stream, tag or domain, alerts on bounce or complaint spikes, and access for a support team without developer rights.
0 — Nothing can be seen after sending; no logs, no events and no webhooks.
3 — Totals of sent and bounced messages; per-message logs, webhooks and retention are basic or not described.
5 — A searchable message log with per-message event history and the bounce reason, log retention stated, event webhooks for delivery, bounce, open, click and complaint, statistics per tag or domain, and an API to fetch events.
8 — Webhooks signed and retried with their schedule documented, the raw SMTP response and the rendered message viewable per send, log retention configurable or extended by plan, alerts on bounce, complaint or delivery-time thresholds, export or streaming of events to a named log or data tool, and read-only roles for support staff.
10 — Full traceability: every message traceable from API call to the receiving server's final answer, events streamed in real time with ordering and delivery guarantees stated, long retention with search across the whole history, and observability features documented with their limits.
The SaaS Developer
Every email can be tracked start to finish, with real-time dashboards for bounces, unsubscribes and spam reports, bounce-rate alerts, webhooks, and partly stated retention (headers kept 35 days; reporting 5 days on the free plan, 30 on Professional). We found no public information on a log searchable by recipient or message ID, webhook signatures and retries, or the receiving server's answer per message — so from these pages I still could not answer "did this user get the reset mail?" without opening a ticket. 1 4 6 7 10 12
The Platform Engineer
Every email is tracked from start to finish to the final destination, with a real-time dashboard for bounce and spam tracking, webhooks, headers kept 35 days and viewable in the control panel, and — the one I care about most — immediate alerts when the bounce rate suddenly rises. I found no public information on the raw SMTP response per message, webhook signing or retry behaviour, per-recipient search, or retention beyond the 5 to 30 days of reporting depending on plan. 1 4 6 7 10
The Shop Operator
Every email is trackable "from start to finish, just like tracking a parcel", headers stay viewable in the control panel for 35 days, and a real-time dashboard covers bounces and spam with webhooks and bounce-rate alerts on top. We found no public information on a log searchable by recipient or tag, on which event types the webhooks deliver, or on keeping full message data longer than the 35-day header and per-plan reporting windows. 1 6 10 7 4
The Data Protection Officer
Every email is trackable in real time with bounce, unsubscribe and spam reporting, headers are viewable in the control panel, and the privacy policy states headers are kept 35 days and one sampled email per thousand 35 days, with reporting history of 5 days on the free plan and 30 on Professional — retention statements I look for. We found no public information on webhook signatures and retry behaviour, per-message bounce reasons, or the raw server response, so full per-message traceability is not evidenced. 1 6 10 12
The Agency Lead
Every sent email is tracked from start to finish on a real-time dashboard covering bounces, spam and unsubscribes, webhooks have an overview and setup guide, alerting on bounce-rate spikes is claimed, and retention is stated — headers kept 35 days, reporting kept 5 days on the free plan and 30 on Professional. The pages we read do not state which events a webhook delivers, whether webhooks are signed and retried, or whether logs are searchable by recipient or message ID. 1 4 7 10 12
The Skeptic
Every email is tracked to its final destination with bounce, spam and unsubscribe reporting, bounce-rate alerts exist, webhooks are documented, and retention is unusually concrete: headers kept 35 days, one email per thousand sampled and kept 35 days, reporting five days on the free plan and thirty on Professional. We found no public information on a searchable per-message log, which events a webhook delivers, webhook signatures or retry schedules, per-tag or per-domain statistics, or extending retention beyond the plan. 1 4 6 7 10 12
Message data, retention & security
Show reasoningHide reasoning
How this is scored
What is stored about each message and what the customer controls: whether message bodies are stored or only metadata, retention periods and the setting to shorten them, deletion of a recipient's data on request, open and click tracking that can be switched off per stream or message, TLS for delivery with an option to require it, encryption at rest, API keys with scopes and per-domain restrictions, IP allow-listing, two-factor authentication and SSO for the dashboard, an audit log, a vulnerability disclosure programme, and security certifications or audits with their scope. Where the data is processed and by whom is scored under sovereignty.
0 — Stores every message indefinitely with no controls, and the vendor states it uses message content for its own purposes.
3 — A privacy policy and a statement that data is encrypted; what is stored, retention and access controls are basic or not described.
5 — What is stored per message documented, retention periods stated, open and click tracking switchable, TLS used for delivery, API keys with restricted permissions, two-factor authentication for the dashboard, and a data processing agreement offered.
8 — Message content retention configurable down to none or metadata only, enforced TLS per domain or message, encryption at rest stated, scoped API keys and IP allow-listing, SSO (SAML) and roles, an audit log, deletion of recipient data by API, and ISO 27001 or SOC 2 stated with its scope.
10 — Data minimisation that can be verified: every stored field and its retention listed, content never stored unless the customer opts in, customer-managed encryption keys or equivalent, independent audits published with their scope, and every security control the customer has listed with its effect.
The SaaS Developer
The privacy policy is unusually concrete about what is kept — email headers for 35 days, and one email in every thousand stored for 35 days, which can be disabled on request — alongside TLS/SSL-secured delivery, GDPR obligations, 30-day access and deletion responses, and a no-selling-of-data statement. We found no public information on two-factor authentication, API key scopes, encryption at rest, an audit log, or ISO 27001 / SOC 2 certifications. 8 10
The Platform Engineer
What gets stored is documented honestly: headers for 35 days, one email per thousand kept for 35 days with storage that can be disabled on request, TLS/SSL secured sending, GDPR pledges, and 30-day handling of access and deletion requests. For my stack the gaps are sharp — I found no public information on scoped API keys, two-factor authentication, SSO, IP allow-listing, encryption at rest, audit logs, certifications, or a data processing agreement. 8 10
The Shop Operator
The privacy policy is concrete about what is kept: email headers for 35 days and one stored email in every thousand for 35 days, with that sampling switchable off on request, and GDPR access and deletion handled free of charge within 30 days. We found no public information on two-factor authentication, scoped API keys, encryption at rest, certifications or a data processing agreement. 10 8
The Data Protection Officer
The privacy policy documents what is stored per message and for how long — headers 35 days, one email in a thousand 35 days with that sample storage disabled on request for trusted accounts — and commits to GDPR obligations, free access requests and deletion responses within 30 days, with TLS in transit. We found no public information on two-factor authentication, scoped API keys, encryption at rest, an audit log, certifications, or a way to switch tracking off per stream; for appointment reminders and lab-result notices, the default storage of sampled message bodies would need that switch-off confirmed in writing. 8 10
The Agency Lead
The privacy policy is unusually concrete about storage: headers kept 35 days, one email in a thousand sampled and stored for 35 days with that storage disableable on request for trusted accounts, TLS/SSL on all plans, and GDPR access and deletion handled within 30 days free of charge. We found no public information on API key scopes, two-factor authentication, encryption at rest, security certifications, or switching open and click tracking off. 10 8
The Skeptic
The privacy policy puts in writing what most vendors leave vague: headers stored 35 days, one email in a thousand sampled for 35 days with storage disableable on request, access and deletion requests answered within 30 days free of charge, and TLS/SSL for transit. We found no public information on two-factor authentication, scoped API keys, encryption at rest, an audit log, or security certifications with their scope — so the storage story is honest but the surrounding controls go undescribed on the captured pages. 8 10
Reliability, accounts & support
Show reasoningHide reasoning
How this is scored
Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).
0 — No status page, no support channel and no way to separate users or applications.
3 — A support contact and a single account; status page, SLA, sub-accounts and roles are basic or not described.
5 — A public status page with incident history, an uptime SLA on at least one plan, sub-accounts or separate servers per application, team members with roles, support by email or chat with stated hours, and plugins or guides for several named platforms.
8 — An SLA with service credits published, redundancy across data centres or regions described, mail queued and retried during incidents, sub-accounts with their own keys, domains and limits manageable by API, granular roles, support response times per plan, and migration assistance offered.
10 — Reliability that can be verified: uptime history published for years, post-mortems for incidents, multi-region failover documented, an SLA covering delivery latency as well as API availability, and white-label or reseller tooling for agencies and platforms.
The SaaS Developer
A 100% uptime SLA with 5% credit per 30 minutes of downtime up to the full monthly fee, a public status page with a historical performance graph, minute-by-minute monitoring, redundant multi-datacenter infrastructure that re-routes traffic between ten locations, and subaccounts our customers could log into themselves — that is the level of runnability a twelve-person team needs. We found no public information on granular team roles, whether mail is queued and retried during incidents, or per-plan response-time commitments. 1 5 6 7 9 13
The Platform Engineer
The reliability paper trail is unusually good: a written 100% uptime guarantee with 5% credit per 30 minutes of downtime up to 100% of the monthly fee, a public status page with a historical performance graph and minute-by-minute monitoring, ten data centre locations with traffic re-routing, and subaccounts with per-customer dedicated IPs and customer self-login. Missing for my on-call shifts: I found no public information on mail being queued and retried during an incident, team roles, response times per plan, or an SLA that covers delivery latency rather than uptime alone. 1 5 7 9 13
The Shop Operator
A 100% uptime guarantee with 5% of the monthly fee credited per 30 minutes of downtime, ten data centres with rerouting when one has an issue, a public status page with a historical performance graph, and paid-account subaccounts that can even get their own dedicated IP — plus phone, chat and ticket support around the clock. As a Shopware operator I note that no Shopware plugin is named among the integrations, and we found no public information on team roles or support response times per plan. 9 5 6 7 13 8 1
The Data Protection Officer
The terms publish a 100 percent uptime guarantee with a 5 percent credit per 30 minutes of downtime up to the monthly fee, and there is a public status page with a historical performance graph, minute-by-minute monitoring, ten data centres with traffic re-routing on failure, and subaccounts on every paid plan with optional dedicated IPs and customer logins. We found no public information on team member roles, mail queueing during incidents, or migration assistance, which keeps this below the higher level. 1 5 6 9 13
The Agency Lead
The closest fit for an agency like mine: every paid account gets subaccounts under Settings, customers can optionally log in and watch their own delivery, larger clients can sit on their own dedicated IP, and the vendor openly markets to web design agencies as resellers — backed by a public status page with a historical performance graph, a 100% uptime SLA paying 5% per 30 minutes of downtime up to the full monthly fee, and ten named data centres with traffic re-routing on failure. We found no public information on granular team roles, mail queueing during incidents, or per-plan support response times. 13 9 5 7 1
The Skeptic
A 100% uptime SLA with a published credit formula — 5% of the monthly fee per 30 minutes of downtime, up to 100% — sits alongside redundant multi-datacentre infrastructure with traffic re-routing, a status page with a historical performance graph, minute-by-minute monitoring, and round-the-clock phone, chat and helpdesk from four offices. Subaccounts on every paid plan, optional dedicated IPs per customer and customer self-login give an agency real tooling; we found no public information on queueing and retry of mail during incidents, per-plan response times or team roles, and the SLA credit must be claimed by contacting support. 1 5 6 8 9 13
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU region available and an EU contracting entity or EU representative, but parts of the chain (sending infrastructure, logs, support, payment) run through non-EU providers without a stated safeguard, or the EU region does not cover logs and account data.
8 — EU processing of messages, logs and account data on named infrastructure, an EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, sending infrastructure and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.
The SaaS Developer
The contracting entity is Sand Dune Mail Ltd of Christchurch, New Zealand, under New Zealand law, and we found no public information on an EU contracting entity or representative. Senders can choose Europe as their region, data centres include Amsterdam, Frankfurt and London, and the privacy policy commits that personal data for EEA users is stored only within the EEA — but we found no public information on subprocessors or a published data processing agreement. 5 6 9 10
The Platform Engineer
The contracting entity is Sand Dune Mail Ltd in Christchurch under New Zealand law, though sending and storage can be pinned to Europe — Frankfurt, Amsterdam and London among the data centres, with a stated region of choice and a pledge that EEA users' personal data is stored only within the EEA. I found no public information on subprocessors, an EU contracting entity or representative, or a data processing agreement, and for a Frankfurt fintech that is the list I need answered before signature. 5 6 9 10
The Shop Operator
The contract is with Sand Dune Mail Ltd of Christchurch under New Zealand law, the captured pages name no subprocessors, and we found no public information on a data processing agreement. There are real positives — Frankfurt, Amsterdam and London data centres, a stored-region choice, and a promise that EEA users' personal data stays in the EEA — but for a German shop the contracting and legal side sits outside Europe. 10 9 6 5
The Data Protection Officer
The contracting entity is Sand Dune Mail Ltd in Christchurch under New Zealand law, but the product tour states data is stored in the region of your choice among US, Europe and Australia, the data centre list includes Amsterdam, Frankfurt and London, and the privacy policy promises that personal data of EEA users is stored only within the EEA. We found no public information on a published data processing agreement, an EU representative, or the subprocessor chain — hosting, sending infrastructure, logging, support and payment — so the sending chain is not evidenced end to end. 5 6 9 10
The Agency Lead
The contracting entity is Sand Dune Mail Ltd in Christchurch and the terms are governed by New Zealand law, so this is not a European vendor; on the other hand the privacy policy commits that personal data for EEA users is stored only within the EEA, and sending regions can be chosen among the US, Europe and Australia, with named centres in London, Amsterdam and Frankfurt. The captured pages name no subprocessors, and we found no public information on a data processing agreement or certifications, so the rest of the chain beyond that commitment is unverified. 10 9 6 5
The Skeptic
The contracting entity is Sand Dune Mail Ltd of Christchurch and the terms choose New Zealand law; we found no EU entity or representative on the captured pages. Data centres include London, Amsterdam and Frankfurt, customers choose a storage region, and the privacy policy promises EEA users' personal data is stored only within the EEA — but the subprocessors behind the sending chain are unnamed and we found no public information on a data processing agreement. This is a New Zealand vendor with a European storage option, not European sovereignty. 5 6 9 10
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a buyer can compute the real annual cost from public pages alone: price per tier by monthly message volume, the price per additional thousand messages, the free tier and its limits, what dedicated IPs, extra log retention, sub-accounts, SSO and support plans cost, minimum term, and whether unused volume carries over.
0 — No public prices at all; every customer is a sales call.
3 — A starting price or a free tier exists, but how cost scales with volume or which features cost extra is unclear.
5 — Tiers are public with their monthly volume and price, but at least one commonly needed piece (overage rate, dedicated IP, longer log retention, SSO, support plan) is unpriced or "on request".
8 — Every tier priced publicly with its volume and overage rate per thousand messages, dedicated IPs and add-ons priced, log retention per tier stated, minimum term and VAT treatment stated.
10 — Complete price computability: annual cost derivable for a given monthly volume, number of domains and sub-accounts and feature set, with every add-on, support and overage fee and the cancellation terms published.
The SaaS Developer
The free tier is fully specified (1,000 emails per month, 200 a day, no credit card) and the Professional plan is public at $75/mo for 100,000 emails/mo with extra emails at $0.85 / thousand, 30 days of reporting and a dedicated IP included, billed monthly or yearly in USD. We found no public information on other tiers' prices, the annual price, VAT treatment or a minimum term, and the terms reserve the right to change fees at any time without advance warning — so our real annual cost is not computable from these pages alone. 4 8 9 11 12
The Platform Engineer
The free tier is fully specified — 1,000 emails a month, 200 a day, no credit card — and the Professional plan is $75/mo for 100,000 emails with extra emails at $0.85 / thousand, a dedicated IP and 30 days of reporting included, monthly or annual billing in USD and a 30-day full refund. Above that the page points to a custom plan, and I found no public information on VAT treatment, minimum term, or whether unused volume carries over. 4 8 9 12
The Shop Operator
The free tier is fully specified — 1,000 emails a month capped at 200 a day, no credit card, ticket support only, five days of reporting — and the Professional plan at $75/mo for 100,000 emails/mo prices extra emails at $0.85/thousand with a dedicated IP included and a 30-day full refund. The captured pages show only this one paid tier, minimum term and VAT treatment are not stated, and the terms reserve the right to change fees at any time without advance warning. 4 12 8 9
The Data Protection Officer
The free tier (1,000 emails per month, 200 per day, ticket support, no credit card) and the Professional plan at $75/mo for 100,000 emails with extra emails at $0.85 per thousand are public, with monthly or yearly billing in USD and a 30-day full refund. We found no public information on prices for other paid tiers, dedicated IP pricing outside Professional, minimum term, VAT treatment, or whether unused volume carries over, and the terms reserve the right to change fees at any time without warning. 4 8 9 12
The Agency Lead
The free tier is fully specified — 1,000 emails a month, 200 a day, no credit card, ticket support only — and Professional is public at $75/mo for 100,000 emails with extra emails at $0.85 per thousand and subaccount management included, monthly or annual billing, all prices in USD. For writing client maintenance contracts I am still missing the rest of the tier ladder, VAT treatment, any minimum term and a standalone dedicated-IP price, and the terms reserve the right to change fees at any time without advance warning. 12 8 4 9
The Skeptic
The free tier is fully specified — 1,000 emails a month, 200 a day, no credit card — and Professional is $75/mo for 100,000 emails with overage at $0.85 per thousand and a dedicated IP included, in USD, monthly or annually, with a 30-day full refund. The captured pages price only this one paid tier, we found no public information on VAT treatment, minimum term or how the annual price differs, and the terms reserve the right to change fees at any time without advance warning. 4 8 9 12
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about SMTP2GO
Is SMTP2GO European?
No. whats-best.ai classifies SMTP2GO as Rest of world.
Where does SMTP2GO store data?
The default storage location for customer data is not stated on the vendor’s pages as of 1 Nov 2026. The vendor’s pages mention the US, Europe and Australia as hosting locations, per the vendor’s page captured 1 Nov 2026.
Does SMTP2GO have a free plan?
Yes. SMTP2GO has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to SMTP2GO?
As of 2 Nov 2026, the panel rates Lettermint (3.5/5), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) highest among the other 15 Transactional Email products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Lettermint (EU-Made). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: SMTP2GO alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 1 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Hosting location. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 20 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 integrations fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 support fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.smtp2go.com Checked 1 Nov 2026 Details →
- 2 Features page (transactional email) www.smtp2go.com Checked 1 Nov 2026 Details →
- 3 Features page (API) www.smtp2go.com Checked 1 Nov 2026 Details →
- 4 Features page (deliverability) www.smtp2go.com Checked 1 Nov 2026 Details →
- 5 Features page (infrastructure) www.smtp2go.com Checked 1 Nov 2026 Details →
- 6 Features page (product tour) www.smtp2go.com Checked 1 Nov 2026 Details →
- 7 API documentation developers.smtp2go.com Checked 1 Nov 2026 Details →
- 8 Pricing page www.smtp2go.com Checked 1 Nov 2026 Details →
- 9 Terms of service www.smtp2go.com Checked 1 Nov 2026 Details →
- 10 Privacy policy www.smtp2go.com Checked 1 Nov 2026 Details →
- 11 Sending API, SMTP & developer experience — found from sitemap www.smtp2go.com Checked 1 Nov 2026 Details →
- 12 Sending API, SMTP & developer experience — found from sitemap www.smtp2go.com Checked 1 Nov 2026 Details →
- 13 Reliability, accounts & support — found from sitemap www.smtp2go.com Checked 1 Nov 2026 Details →