Transactional Email
SMTPeter
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Copernica BV · www.smtpeter.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.
SMTPeter at a glance
- Vendor
- Copernica BV
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Default not stated; pages mention Netherlands source, captured 1 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 1 Nov 2026
- Panel verdict
- The AI panel rates SMTPeter 2.5/5, the mean of 6 judges. SMTPeter, Copernica BV's transactional email service, scores highest on sovereignty at 6-7 and pricing transparency at 6-7: the captured pages document servers in the Iron Mountain data centre in Haarlem, backups with True BV in Amsterdam and a policy statement that data entered by you is only stored in the Netherlands, alongside a licence at € 55/month including 25.000 emails, one IP and one domain and per-thousand rates from € 0,23 down to € 0,05. 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
SMTPeter, Copernica BV's transactional email service, scores highest on sovereignty at 6-7 and pricing transparency at 6-7: the captured pages document servers in the Iron Mountain data centre in Haarlem, backups with True BV in Amsterdam and a policy statement that data entered by you is only stored in the Netherlands, alongside a licence at € 55/month including 25.000 emails, one IP and one domain and per-thousand rates from € 0,23 down to € 0,05. It scores lowest on data and security at 3-4 and reliability and accounts at 3-4, where we found no public information on two-factor authentication, encryption at rest, certifications or an uptime SLA, and retention is decided case-by-case. Scores span 4-5 on deliverability and observability: higher marks credit guided SPF, DKIM and DMARC set-up with a dedicated IP and webhooks; lower ones weigh the absence of published bounce suppression and a fixed log-retention period. The sending API holds at a flat 4, min 4 and max 4 — REST and SMTP are documented, with no public information on SDKs, rate limits or a test mode.
Speaks for it
- Publishes a complete price ladder — € 55/month including 25.000 emails, one IP and one domain, per-thousand rates from € 0,23 down to € 0,05, a monthly cost calculator and a support contract at 89 euros/month
- Documents the hosting chain in named Dutch locations — own and Leaseweb Netherlands BV servers at Iron Mountain in Haarlem and backups with True BV in Amsterdam — with the policy stating data entered by you is only stored in the Netherlands
- Includes a dedicated IP in the base licence with guided sender-domain set-up, hosted SPF records, automatic DKIM signing and DMARC deployment with daily reports
- Exposes log files, statistics, DMARC reports and archived emails in the dashboard and via the REST API, with webhooks for deliveries, bounces, clicks, failures and opens
- Publishes a data protection officer contact at dpo@smtpeter.com and supports GDPR access and deletion requests
Held against it
- States that a retention period cannot be specified in advance and data deletion is decided case-by-case
- Limits GDPR data requests to information Copernica BV holds for its own use, not data stored by customers
- We found no public information on two-factor authentication, encryption at rest, scoped API keys, ISO 27001 or SOC 2 certification, or a published data processing agreement
- We found no public information on an uptime SLA, a public status page with incident history, sub-accounts or team roles
- Extra IP addresses and domains are only said to be charged extra with no published rates, and requirements above five domains go through a sales contact
Best for
- You need transactional mail hosted in the Netherlands — the policy states data entered by you is only stored in the Netherlands, on servers in Haarlem with backups in Amsterdam
- You want to budget volume precisely: the pages publish the full per-thousand ladder from € 0,23 down to € 0,05 plus a monthly cost calculator
- You send from a single domain and want a dedicated IP with guided SPF, DKIM and DMARC included in the € 55/month licence
- You integrate over REST or SMTP and want templates stored centrally as JSON objects, personalised and sent to multiple recipients through the API
Avoid if
- You need a fixed, contractual data-retention period — the policy states one cannot be specified in advance and deletion is case-by-case
- Your GDPR workflows require the vendor to act on requests covering data you store through the platform — the policy states data requests apply only to information Copernica BV holds for its own use
- You run more than five sender domains or need add-on costs in advance — the pages direct you to contact the vendor above five domains and only state that extra IPs and domains are charged extra
- You need a support channel other than email during office hours — support is published as email during office hours, with a technical support contract at 89 euros/month
The scores
| Criterion | Panel median |
|---|---|
| Sending API, SMTP & developer experience | 2 of 5 |
| Deliverability & sender reputation | 2 of 5 |
| Message logs, events & webhooks | 2 of 5 |
| Message data, retention & security | 1.5 of 5 |
| Reliability, accounts & support | 1.5 of 5 |
| European sovereignty | 3.5 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
Both REST and SMTP are documented — REST with access tokens, SMTP with login credentials — and the template story is real: JSON templates with personalisation, a drag-and-drop editor and a REST call to send from a stored template. We found no public information on SDKs or a Laravel driver, a sandbox or test mode, attachments, idempotency or rate limits, which is exactly what I would check before touching our mail driver again. 1 2 4
The Platform Engineer
Both routes are documented — a REST API with a dashboard-issued access token and an SMTP relay with login credentials — and templates are stored as JSON with personalisation, multiple recipients and advanced delivery options, usable from the API, the dashboard or an ordinary mail client. We found no public information on official SDKs for named languages, rate limits, a test or sandbox mode, idempotency keys or inbound mail parsing. The protocol choice is real; the operation around it is thin. 1 2 4
The Shop Operator
Both a REST API and an SMTP login are documented, REST tokens come from the dashboard, and templates are stored as JSON objects that we can personalise and send to multiple recipients through the API. I found no public information on SDKs for named languages, rate limits, a test mode or attachments, so I cannot judge how quickly a developer could wire our shop software to it. 1 2 4
The Data Protection Officer
A REST API and an SMTP relay are both documented, with templates stored as JSON objects that can be personalised and sent to multiple recipients through the API, and the documentation covers a broad set of REST calls from accounts to log files. We found no public information on official SDKs for named languages, stated rate limits, a sandbox or test mode, attachments, or scheduled sending. 2 1 4
The Agency Lead
Both a REST API and an SMTP relay are documented with token and credential handling, and the template side is real: a centralised store, templates saved as JSON with unique IDs, personalisation, drag-and-drop and HTML editors, and CSS inlining. We found no public information on official SDKs for named languages, attachments, batch sending, rate limits or a test mode, so a developer gets a working integration but not the full toolkit. 1 2 4
The Skeptic
Both a REST API and an SMTP relay are documented, with a centralised template store (JSON objects with unique ids, personalisation), a drag-and-drop and an HTML editor, and a documentation section listing all REST calls. But I found no public information on official SDKs for named languages, attachments, a test or sandbox mode, rate limits, idempotency keys, scheduled sending or inbound email parsing, and no quick-start guides for named frameworks. 1 2 4
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
Sender domains with guided DNS set-up, hosted SPF, automatic DKIM signing and DMARC with daily reports are all documented, and a dedicated IP ships in the base licence rather than as an upsell. We found no public information on shared-pool vetting, automatic suppression of hard bounces and complaints, or separating transactional from bulk streams, so I would be trusting reputation management I cannot read about. 1 2 3 5
The Platform Engineer
Sender domains are configured through the dashboard with hosted SPF records, automatic DKIM signing and DMARC including daily reports, and a dedicated IP ships in the base licence — a sensible posture for transactional mail, with feedback loops and email throttling also documented. We found no public information on automatic suppression of hard bounces and complaints, IP warm-up, separation of transactional and bulk streams, or the Gmail and Yahoo sender requirements. Nothing is published on delivery times either, which is what I would want to verify before routing login codes through it. 1 2 3 5
The Shop Operator
The guided set-up I need is real: the dashboard shows exactly how to configure DNS for a sender domain, DKIM is signed automatically, SMTPeter hosts the SPF records, DMARC is deployed with daily reports, and a dedicated IP is included in the € 55 base price. I found no public information on automatic suppression of bounces and complaints, on separating transactional order mail from newsletter streams, or on compliance with the Gmail and Yahoo bulk-sender rules. 1 2 3 4 5
The Data Protection Officer
Sender domains come with guided DNS configuration, hosted SPF records, automatic DKIM signing and DMARC deployment with daily DMARC reports in the dashboard, and every licence includes a dedicated IP address; bounces, opens and clicks are tracked with feedback notifications. We found no public information on shared-pool vetting, automatic suppression lists, IP warm-up, or stated compliance with the Gmail and Yahoo bulk-sender rules. 3 2 5 1
The Agency Lead
Sender domains are configured in the dashboard with the exact DNS instructions, SPF records are hosted for you, DKIM is signed automatically once a domain is set, DMARC reports arrive daily, and one dedicated IP is included in the base price. We found no public information on a custom return path, shared-pool vetting, automatic suppression of hard bounces, or compliance with the Gmail and Yahoo bulk-sender rules. 1 2 3 5
The Skeptic
Guided sender-domain set-up with the dashboard showing the DNS changes, hosted SPF records, automatic DKIM signing, DMARC deployment with daily reports viewable in the dashboard, and a dedicated IP included in the base licence. The documentation names "bounce handling" as a topic without describing automatic suppression of hard bounces or complaints, and I found no public information on IP warm-up, shared-pool vetting, an acceptable-use enforcement process, the Gmail and Yahoo sender requirements, or published delivery times with a method. 1 2 3 4
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
Log files are browsable and downloadable in the dashboard and via REST, individual messages can be requested, and webhooks exist for deliveries, bounces, clicks, failures and opens with a documentation section on securing them. That answers my "did this user get the reset mail" question at a basic level, but retention is explicitly case-by-case with no fixed period, and we found no public information on searching logs by recipient, webhook retries or bounce-spike alerts. 1 2 4 7
The Platform Engineer
Log files, statistics, DMARC reports and archived emails are viewable in the dashboard and retrievable through the REST API, and webhooks cover deliveries, bounces, clicks, failures and opens, with notifications configurable per channel. Retention is explicitly decided case-by-case rather than stated as a period, and we found no public information on searching logs by recipient or message ID, webhook retry behaviour, or alerts on bounce spikes — the alert I would need before a slow login code reaches a customer. 1 2 4 7
The Shop Operator
The dashboard shows log files, statistics, DMARC reports and archived emails, log files can be browsed and downloaded through the REST API, and webhooks exist for deliveries, bounces, clicks, opens and failures with a page on securing them. The captured pages do not state how long logs are kept, whether I can search by recipient, or the remote server's bounce answer, which is what my support inbox would need. 1 2 3 4
The Data Protection Officer
The dashboard and the REST API give access to log files, statistics, DMARC reports and archived emails, and webhooks cover deliveries, bounces, clicks, failures and opens with a documented section on securing them. We found no public information on how long logs are kept, per-message bounce reasons from the receiving server, alerts on bounce or complaint spikes, or read-only roles for support staff. 1 2 4 3
The Agency Lead
Log files can be browsed and downloaded in the dashboard and through the REST API, archived emails are viewable, statistics come via both routes, and webhooks cover deliveries, bounces, clicks, failures and opens with a documented way to secure them. We found no public information on log retention (the privacy policy says deletion is decided case by case), a searchable per-message history with the bounce reason, alerts, or read-only access for client support staff. 1 2 4 7
The Skeptic
Log files can be browsed and downloaded in the dashboard and via the REST API, archived emails and DMARC reports are shown, statistics cover opens, clicks and spam complaints, and webhooks exist for deliveries, bounces, clicks, failures and opens with a section on securing them. Nowhere is log retention stated — the privacy policy says data is kept until it is no longer necessary and deleted on a case-by-case basis — and I found no public information on searching the log by recipient or message ID, the remote server's bounce answer, webhook retries, or alerts on bounce spikes. 1 2 3 4 7
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 candid: only employees on Dutch-law contracts with confidentiality clauses may access customer data, daily backups sit in Haarlem and Amsterdam for at most seven days, and there is a DPO plus GDPR access and deletion requests. But those requests apply only to data Copernica holds for its own use rather than customer-stored data, deletion happens case-by-case with no stated period, and we found no public information on TLS enforcement, encryption at rest, key scopes, two-factor authentication or certifications. 1 4 7
The Platform Engineer
The privacy policy documents what sits in log files, daily backups kept at most seven days across Haarlem and Amsterdam, a data protection officer, GDPR access and deletion requests, and staff access restricted to employees on Dutch contracts. We found no public information on encryption, TLS for delivery, scoped API keys, two-factor authentication, certifications, or a setting to shorten how long archived email content is kept. 1 4 7
The Shop Operator
The privacy policy documents log files, daily backups in Haarlem and Amsterdam kept at most seven days, a data protection officer at dpo@smtpeter.com, GDPR access and deletion requests, and employee access restricted to Dutch-law contracts. I found no public information on two-factor authentication, encryption at rest, API key scopes, enforced TLS or any ISO 27001 or SOC 2 audit, and retention is only described case-by-case with no fixed period. 4 7
The Data Protection Officer
Log files and archived emails are stored and downloadable, access is restricted to employees on Dutch-law contracts with confidentiality clauses, GDPR access and deletion requests are supported with a DPO contact, and daily backups are kept for at most seven days in Haarlem and Amsterdam. However, the privacy policy states a retention period cannot be specified in advance and deletion is case-by-case, data requests exclude data stored by customers, and we found no public information on switching off open and click tracking, encryption at rest, two-factor authentication, scoped API keys, or a data processing agreement. 7 4 1
The Agency Lead
The privacy policy is concrete on operations — daily backups kept up to seven days across Haarlem and Amsterdam, customer data accessible only to staff on Dutch employment contracts with confidentiality clauses — and GDPR access and deletion requests plus a data protection officer contact are published. We found no public information on configurable retention of message content, encryption at rest, two-factor authentication, scoped API keys or certifications, which is what I would need before putting thirty clients' recipient data on the platform. 1 4 7
The Skeptic
The privacy policy is refreshingly concrete on some things: where servers sit, daily backups in two physical locations kept at most seven days, GDPR access and deletion requests, a DPO contact, and access to customer data restricted to employees on Dutch-law contracts with confidentiality clauses. But I found no public information on encryption in transit or at rest, two-factor authentication, API key scopes, a data processing agreement, certifications or an audit — and archived emails are stored with nothing said about shortening content retention or switching tracking off. 4 7
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
Support is email during office hours at a named address, a technical support contract is available for 89 euros/month, and daily backups run in two Dutch locations. The captured pages mention statuspage.io only as a tool for emergency notifications when servers are unavailable, and we found no public information on an uptime SLA, public incident history, sub-accounts, team roles or guides for platforms like WordPress or Shopify. 1 4 7
The Platform Engineer
Support runs by email during office hours with a paid technical support contract at 89 euros/month, backups are taken daily to two locations, and the privacy policy names a third-party status tool used to notify customers when their own servers are unavailable. We found no public information on a public status page with incident history, an uptime SLA with service credits, queueing and retry during incidents, sub-accounts or team roles — the first things I check on any sender. 1 4 7 8
The Shop Operator
Support runs by email during office hours with a priced technical support contract at 89 euros per month, statuspage.io is used for emergency notifications when their own servers are down, and daily backups sit in two separate locations. I found no public information on an uptime SLA, incident history, team roles or sub-accounts, and nothing on plugins or guides for shop platforms like Shopware. 1 4 5 7
The Data Protection Officer
Support is reachable by email during office hours, a technical support contract is published at 89 euros/month, daily backups sit in two physical locations, and emergency status notifications go out through statuspage.io when the vendor's own servers are unavailable. We found no public information on a public status page with incident history, an uptime SLA, sub-accounts with their own keys and limits, or integrations with platforms that send mail on the customer's behalf. 4 1 7 2
The Agency Lead
Support runs by email during office hours with a paid technical support contract at 89 euros a month, backups sit in two separate Dutch locations, and emergency status notifications go out through statuspage.io. The documentation lists an accounts-and-users topic, but we found no public information on sub-accounts with their own keys, domains and limits per client, team roles, a public status page with incident history, an SLA, or plugins for platforms like WordPress or Shopware — the agency structure I run on is not described. 2 4 5 7
The Skeptic
Email support during office hours plus a technical support contract priced at 89 euros/month, an accounts-and-users section in the documentation, daily backups in Haarlem and Amsterdam, and statuspage.io named as the channel for emergency notifications when their own servers are down. I found no public information on a public status page with incident history, an uptime SLA, mail queueing during outages, sub-accounts with their own keys and domains, granular team roles, or plugins for platforms like WordPress or Shopify. 2 4 7
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
This is a genuinely European chain: Copernica BV in Amsterdam runs SMTPeter on its own and Leaseweb Netherlands servers in the Iron Mountain data centre in Haarlem, backups go to a second Amsterdam site at True BV, the policy states data entered is only stored in the Netherlands, and subprocessors from 8x8 to Pipedrive to Leadinfo in Rotterdam are named. We found no public information on a published data processing agreement or ISO 27001 / SOC 2 certifications, which keeps it a notch below the top. 1 7 8
The Platform Engineer
The chain is named and European: Copernica BV of Amsterdam is the entity, its own servers and Leaseweb Netherlands BV sit in the Iron Mountain data centre in Haarlem, backups are held with True BV in Amsterdam, and the policy states data entered by you is only stored in the Netherlands. Subprocessors are listed with their purposes — among them 8x8, Pipedrive, Recruitee, statuspage.io and Leadinfo of Rotterdam — and staff access to customer data from outside the EU requires DPO and customer approval. We found no public information on a published data processing agreement or security certifications, which keeps this short of the top level. 1 4 7
The Shop Operator
The whole chain is documented as Dutch: Copernica's own servers and Leaseweb Netherlands in the Iron Mountain datacentre in Haarlem, backups with True BV in the euNetworks datacentre in Amsterdam, a statement that data entered is only stored in the Netherlands, and Copernica BV in Amsterdam as the contracting entity with subprocessors like 8x8, Pipedrive and Recruitee named with their purposes. I found no public information on a published data processing agreement or security certifications, and most subprocessor locations are not given, which keeps it short of fully evidenced end-to-end sovereignty. 3 4 7
The Data Protection Officer
Copernica BV of Amsterdam is the contracting entity, servers run in the Iron Mountain data centre in Haarlem on Copernica's own hardware and Leaseweb Netherlands BV, backups are held at a second Amsterdam site, the policy states data entered by you is only stored in the Netherlands, and business subprocessors such as 8x8, Pipedrive, Recruitee and statuspage.io are named with their purposes. We found no public information on a published data processing agreement, ISO 27001 or SOC 2 certifications, or the locations of the named subprocessors. 7 3 1
The Agency Lead
Copernica BV in Amsterdam is the contracting entity, servers and backups sit in named Dutch locations (Iron Mountain in Haarlem via Leaseweb or own hardware, euNetworks Amsterdam via True BV), and the privacy policy states data is only stored in the Netherlands — exactly the hosting story I need for GDPR-bound German clients. Subprocessors are named with their purposes (8x8, Pipedrive, Recruitee, statuspage.io, Leadinfo) but mostly without locations, and we found no public information on a published data processing agreement or security certifications. 1 7 8
The Skeptic
Copernica BV in Amsterdam is the entity, servers run on own and Leaseweb Netherlands BV hardware in the Iron Mountain data centre in Haarlem with backups at True BV in the euNetworks data centre in Amsterdam, and the policy states data "is only stored in the Netherlands"; subprocessors are named (8x8, Pipedrive, Recruitee, statuspage.io, Leadinfo) though most without locations, and employee access from abroad is possible only after DPO and customer approval. I found no public information on a published data processing agreement for SMTPeter or ISO 27001/SOC 2 certification, which is what separates a documented sovereign chain from a provable one. 1 3 7
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
For message volume this is unusually computable: € 55/month including 25.000 emails, published per-thousand bands from € 0,23 down to € 0,05, a monthly-cost calculator, and a support contract priced at 89 euros/month. The captured pages state that more messages, multiple IPs or multiple domains "will be charged extra", and we found no public information on those rates, on minimum term or VAT treatment; contact is required above five domains and for enterprise licences. 1 4 5
The Platform Engineer
The volume ladder is unusually explicit: € 55/month including 25.000 emails, one dedicated IP and one domain, with per-thousand rates published from € 0,23 down to € 0,05 across bands up to 45.000.000 and beyond, plus a cost calculator and a priced technical support contract at 89 euros/month. Extra IPs and domains are acknowledged as charged extra without figures, and enterprise licensing and anything above five domains go through a sales contact. We found no public information on VAT treatment, minimum term, a free tier, or per-plan log retention. 1 4 5
The Shop Operator
The pricing is concrete: € 55 per month including 25.000 emails, one IP and one domain, a published declining rate per thousand (€ 0,23 for the next 25.000 down to € 0,05 for all further messages), a monthly cost calculator, and the 89 euros/month support contract. I cannot compute the real annual cost from the pages alone because the unit prices for extra IPs and domains are not published, more than five domains means contacting the vendor, and minimum term and VAT treatment are not stated. 1 4 5
The Data Protection Officer
The pricing page publishes a licence at € 55/month including 25.000 emails, one dedicated IP and one domain, a complete per-thousand volume table from € 0,23 down to € 0,05, a monthly cost calculator, and a support contract at 89 euros/month. Extra IP addresses and domains are only said to be charged extra, requirements above five domains are handled by contacting the vendor, and we found no public information on VAT treatment, minimum term, or the price of add-ons such as extended log retention. 5 1 4
The Agency Lead
The pricing page is unusually open: € 55 per month covering 25,000 emails with one dedicated IP and one domain, a complete overage ladder from € 0,23 per thousand down to € 0,05, an 89-euro monthly support contract, and a monthly-cost calculator. For pricing thirty client accounts the gaps hurt: extra domains and IP addresses are only said to be charged extra without rates, requirements above five domains need a sales contact, and we found no public information on minimum term or VAT treatment. 1 4 5
The Skeptic
Unusually granular for the sector: "€ 55/month" including 25.000 emails and one IP and domain, a full overage table per thousand messages ("€ 0,23" for the next 25.000 down to "€ 0,05" for everything beyond 50 million), a support contract at 89 euros/month, and a monthly cost calculator. But additional domains and IPs are only said to be "charged extra" with no published rate, more than five domains requires contact, the enterprise licence is enquiry-only, and I found no public information on a free tier, minimum term or VAT treatment. 1 4 5
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 ⚠ unverified | — | 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 SMTPeter
Is SMTPeter European?
Yes. whats-best.ai classifies SMTPeter as EU-Made.
Where does SMTPeter 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 Netherlands as hosting location, per the vendor’s page captured 1 Nov 2026.
Does SMTPeter have a free plan?
Not stated on the vendor’s pages as of 1 Nov 2026.
What are the best alternatives to SMTPeter?
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: SMTPeter 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, Hosting options. 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.
- 8 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 legal 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 subprocessors 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
- 3 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (8)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.smtpeter.com Checked 1 Nov 2026 Details →
- 2 API documentation www.smtpeter.com Checked 1 Nov 2026 Details →
- 3 Features page (email authentication) www.smtpeter.com Checked 1 Nov 2026 Details →
- 4 Documentation (FAQ) www.smtpeter.com Checked 1 Nov 2026 Details →
- 5 Pricing page www.smtpeter.com Checked 1 Nov 2026 Details →
- 6 Terms of service www.smtpeter.com Checked 1 Nov 2026 Details →
- 7 Privacy policy www.smtpeter.com Checked 1 Nov 2026 Details →
- 8 Acceptable use policy www.smtpeter.com Checked 1 Nov 2026 Details →