turboSMTP
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by turboSMTP (eDigital S.r.l., Italy) · www.turbo-smtp.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.
turboSMTP at a glance
- Vendor
- turboSMTP (eDigital S.r.l., Italy)
- Headquarters
- Not stated on the vendor’s pages as of 17 Nov 2026
- Data hosting
- In the EU source, captured 17 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 17 Nov 2026
- Panel verdict
- The AI panel rates turboSMTP 2/5, the mean of 6 judges. turboSMTP is a transactional email service from an Italian company — the captured pages give different renderings of the company name (Edisplay srl, eDigital S.r.l.) — offering a documented REST API v2 with an OpenAPI specification, an EU send endpoint and an SMTP relay with SSL on port 465. how scores are made
- As of
- Vendor pages captured 17 Nov 2026; evaluated by the panel 19 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
turboSMTP is a transactional email service from an Italian company — the captured pages give different renderings of the company name (Edisplay srl, eDigital S.r.l.) — offering a documented REST API v2 with an OpenAPI specification, an EU send endpoint and an SMTP relay with SSL on port 465. The bench scored pricing transparency at a uniform 5 and sovereignty at 5-6, crediting published tiers (Free €0/month with 200 email/day, Basic €14.95/month, Pro €79.95/month, the paid tiers including 15,000 email/month), a downloadable GDPR data processing agreement and a "100% European infrastructure" claim the judges repeatedly read as marketing wording rather than a statement of where customer data sits. Deliverability scored lowest at 3-4: bounce, spam-complaint and unsubscribe handling is concrete, but the shared-IP promise is assertion without published method and we found no public information on SPF, DKIM and DMARC set-up. Reliability and accounts spread widest at 4-6: the high end leaned on sub-accounts with individual quotas and 24/7 multilingual support, while we found no public information on an uptime SLA or incident history behind the server-status badge.
Speaks for it
- Sub-accounts with individual sending quotas — up to 100 on the Pro plan — can be managed through the API and resold white-label under your own brand
- The API v2 is publicly documented with an OpenAPI specification, client libraries for C#, PHP, Node.js, Python, Java and Go, and an SMTP relay with SSL on port 465
- Webhooks are documented down to the flat JSON payload, a message identifier shared across events, and two retries before an event is dropped
- The vendor states its GDPR processor role with a downloadable data processing agreement and breach notification within seventy-two hours
- Pricing tiers are public — Free at €0/month with 200 email/day, Basic at €14.95/month and Pro at €79.95/month, both paid tiers including 15,000 email/month — and no credit card is required to start
Held against it
- Webhooks are not signed, and the dashboard accepts plain HTTP callback URLs that may carry basic-auth credentials
- Deliverability beyond bounce and complaint management rests on the assertion of reliable, never-shared IPs rather than a documented method
- The captured pages give different figures for the free tier's allowance: 200 email/day, 6,000 free emails per month and 200 free emails/month
- Free and Basic plans include only a 30-day webhook demo
- We found no public information on log retention periods, what is stored per message, two-factor authentication, or ISO 27001 or SOC 2 certification
Best for
- You are an agency or reseller that wants each client to have their own sending quota and statistics area — sub-accounts run up to 100 on the Pro plan and can be resold white-label
- You want a transparent, low-cost start — the tiers are published with volumes, the free offer is stated with no lock-in, and no credit card is required
- You need a European contracting setup — an Italian company, a dedicated EU send endpoint and a self-service downloadable data processing agreement under GDPR
- You integrate by code or SMTP and want published developer material — an OpenAPI specification, client libraries for C#, PHP, Node.js, Python, Java and Go, and webhooks with a documented retry policy
Avoid if
- You need to authenticate webhook callbacks before trusting them — the reference states requests are not signed and plain HTTP callback URLs are accepted
- You plan to build on webhooks from the Free or Basic plan — those plans include only a 30-day webhook demo
- You must evidence deliverability controls to a risk or security reviewer — ask the vendor: the public pages we read do not show it
- You need sub-accounts on a lower tier — reselling quotas under your own brand requires the Pro plan at €79.95/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 | 2 of 5 |
| Reliability, accounts & support | 2 of 5 |
| European sovereignty | 2.5 of 5 |
| Pricing transparency | 2.5 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
A documented REST API v2 with an OpenAPI specification, a management API, an EU endpoint and an SMTP relay on SSL port 465, plus client libraries for C#, PHP, Node.js, Python, Java and Go — enough to wire up myself, though I found no public information on a vendor-maintained Laravel or framework driver. Attachments and campaign identifiers are documented, but I found no public information on stored templates with variables, batch sending, rate limits or a sandbox mode, which is exactly what I would check before touching my mail driver again. 1 2 3 8
The Platform Engineer
The v2 REST API is properly documented with an OpenAPI specification, covering send, analytics, suppressions, sub-accounts and validation, alongside an SMTP relay and official client libraries for six named languages including Go and Java. But I found no public information on rate limits, a sandbox mode, stored templates, batch sending, idempotency keys or scheduled sending, so I could not safely put a production one-time-code pipeline on it from the docs alone. 2 3 1
The Shop Operator
The sending path is documented: a REST API v2 with endpoints for sending, analytics, suppressions, sub-accounts and validation, an OpenAPI specification, an SMTP relay, official client libraries for C#, PHP, Node.js, Python, Java and Go, and a worked Go example with instant API keys and SMTP credentials on sign-up. Plain-text or HTML mail with attachments and campaign identifiers is supported. We found no public information on stored templates, batch sending, rate limits or a sandbox mode, so I cannot see how to stage test sends before pointing my shop's order mail at it. 1 2 3 8
The Data Protection Officer
A REST API v2 with an OpenAPI specification, a send endpoint on both global and EU hosts, client libraries for six named languages, attachments, and JSON and multipart formats are documented, alongside the SMTP relay with SSL/TLS on port 465. We found no public information on stored templates, rate limits, a test or sandbox mode, or inbound email parsing, which keeps this below the mid anchor. 1 2 3 8
The Agency Lead
API v2 is real and documented — an OpenAPI specification, EU and global send endpoints, attachments, consumer-key authentication, official libraries for C#, PHP, Node.js, Python, Java and Go, plus an SMTP relay with SSL on port 465 and a free WordPress plugin. We found no public information on stored templates, batch sending, rate limits, a sandbox mode or inbound email, which my Laravel and Node teams would ask about on day one. 1 2 3 8
The Skeptic
There is a documented REST API v2 with an OpenAPI specification, an SMTP relay with SSL/TLS, client libraries in six named languages, attachments, and a worked guide. But we found no public information on rate limits, stored templates with variables, batch sending, a sandbox mode, or idempotency keys — the pages simply never mention them. 1 2 3
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
Bounces, spam complaints and unsubscribes are managed in one dashboard with real-time tracking per address, unsubscribed addresses are excluded from future sends automatically, suppressions can be filtered and imported via the API, and a domain validation check references the Gmail and Yahoo rules. The shared IP pool is described in marketing terms as reliable IPs never blacklisted and never shared with shady senders, but I found no public information on guided SPF, DKIM and DMARC set-up, dedicated IPs or separating transactional from marketing streams. 4 5 8 2
The Platform Engineer
Bounce, spam-complaint and unsubscribe handling is described in detail, with real-time tracking per address, automatic exclusion of unsubscribed addresses, suppression lists manageable via API, custom tracking domains on the Pro plan, and a domain validation tool referencing the Gmail and Yahoo sender rules. Beyond a marketing line about reliable IPs never shared with shady senders, I found no public information on SPF, DKIM or DMARC set-up guidance, dedicated IPs or warm-up, stream separation between transactional and marketing mail, or published delivery times. 4 2 5 1
The Shop Operator
Bounces, spam complaints and unsubscribes are tracked in real time per address and managed from one dashboard, unsubscribed addresses are excluded automatically, suppressions can be filtered, imported and exported, and the shared IPs are described as vetted and never shared with shady senders. There is a domain validation check against the Gmail and Yahoo rules and custom tracking domains on the Pro plan. We found no public information on guided SPF, DKIM and DMARC set-up, dedicated IPs, warm-up or separate streams for order mail versus newsletters — the guided set-up is exactly what I need before moving 900 orders a week off my hoster's mail server. 1 2 4 5 8
The Data Protection Officer
Bounces, spam complaints and unsubscribes are managed from one dashboard with real-time per-address tracking, unsubscribed addresses are automatically excluded from future sends, suppressions can be filtered and removed by API, custom tracking domains exist, and there is a domain validation tool referencing the Gmail and Yahoo rules. We found no public information on guided SPF, DKIM or DMARC set-up, dedicated IPs, or separation of transactional and marketing streams; the IP policy rests on a marketing statement about reliable, never-shared IPs. 1 2 4 5 8
The Agency Lead
Bounces, spam complaints and unsubscribes are tracked per address in one dashboard, unsubscribed addresses are excluded automatically, Pro adds custom tracking domains, and there is an IP claim of never blacklisted and never shared with shady senders alongside a domain validation check against the Gmail and Yahoo rules. We found no public information on guided SPF, DKIM and DMARC set-up, dedicated IPs, or how transactional and marketing mail are separated. 1 4 5 8
The Skeptic
Bounces, spam complaints and unsubscribes are tracked per address with automatic exclusion of unsubscribed recipients, and a domain-validation tool checks the Gmail and Yahoo sender rules. Beyond that it is assertion, not method: IPs promised as "never blacklisted and never shared with shady senders" with nothing behind it, and we found no public information on SPF/DKIM/DMARC set-up, dedicated IPs, warm-up, feedback loops, pool vetting, or stream separation between transactional and marketing mail. 2 4 5 8
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
Webhooks come with a documented payload shape, a two-retry schedule, expected duplicates and per-message identifiers, message records can be retrieved and exported as CSV, and there are real-time per-address tracking and WebSocket streams. However, the webhook reference states that requests are not signed and no HMAC signature header is provided, which removes the one guarantee I need before trusting bounce callbacks, and I found no public information on log retention, per-message bounce reasons or alerts on bounce and complaint spikes (only a daily credit-usage alert is described). 6 2 1 4
The Platform Engineer
Webhooks are documented down to the payload — flat JSON, a shared message identifier, two retries before an event is dropped — and there is an analytics API for message records with CSV export plus claimed low-latency WebSocket streams. But the webhooks carry no signature to verify, configuration changes can take an hour to propagate, and I found no public information on log retention, per-message SMTP responses, or alerts on bounce spikes; the only alert described is a daily credit-usage threshold, which pages nobody when a mailbox provider starts deferring us. 6 2 1 4
The Shop Operator
Message records can be retrieved and exported as CSV, real-time delivery, bounce and open or click insights are offered, low-latency WebSocket streams are advertised, and the webhook system is genuinely documented: flat JSON payloads, a message identifier shared across events, spam-complaint events, two retries before dropping, and honest advice to expect duplicates. Webhooks are not signed, and open and click events depend on tracking being enabled. We found no public information on log retention, a searchable message view or the receiving server's answer per message — which is what my staff would need when a customer says an invoice never arrived. 1 2 4 6
The Data Protection Officer
The webhook reference documents a flat JSON payload, a message identifier shared across events, a spam-complaint event type, a retry policy of two attempts before dropping, and expected duplicates with deduplication advice; real-time delivery and bounce insights, message records, CSV export and tracking configuration are also available. The callbacks are unsigned and registration is dashboard-only, and we found no public information on log retention, per-message bounce reasons, or alerts on bounce or complaint spikes. 1 2 4 6
The Agency Lead
Message records can be retrieved and exported as CSV, delivery, bounce, open and click activity is tracked in real time, and webhooks are documented down to the retry schedule of two attempts with spam-complaint events, though open and click events depend on tracking being enabled. The documented facts cut the other way too: turboSMTP does not sign webhook requests and accepts plain HTTP callbacks with credentials in the URL, and we found no public information on log retention, a searchable per-message log with the bounce reason, or alerts on bounce and complaint spikes. 1 2 4 6
The Skeptic
Event webhooks are documented down to the payload shape and retry schedule — two retries, then the event is dropped, duplicates expected — and message records can be retrieved and exported as CSV, with real-time delivery and bounce insights. But the reference states outright that turboSMTP does not sign webhook requests, the event types shown name only spam complaints, and we found no public information on log retention, a searchable per-message log, or the bounce reason per message. 1 2 6
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 names the vendor as data processor with GDPR Article 33 breach notification, a stated data-minimization principle, staff training, encryption of transactions, access and backups, and a downloadable data processing agreement; SMTP delivery runs over SSL/TLS. I found no public information on message retention periods, two-factor authentication, permission scopes for the consumer keys, or certifications such as ISO 27001 or SOC 2. 9 8 2 3
The Platform Engineer
The GDPR page is more substantive than most — processor and controller roles, a downloadable data processing agreement, data minimisation, breach notification within seventy-two hours, staff training, and encryption for transmission and stored data — and API credentials can be created and revoked through the management API without a deploy. The keys show no visible scopes, however, and I found no public information on retention periods, what is stored per message, two-factor authentication, single sign-on, IP allow-listing, an audit log, or ISO 27001 or SOC 2 certifications. 9 2 3
The Shop Operator
The privacy policy commits to data minimisation, encryption of stored data plus secured transactions, access and backups, firewalls, antivirus and intrusion detection, encrypted transmission, breach notification to customers under GDPR's seventy-two-hour rule, and staff who are trained and instructed before accessing data; a complete data processing agreement can be downloaded, open and click tracking is configurable, and application credentials can be created, updated and revoked through the API. We found no public information on what is stored per message, retention periods, deletion of a recipient's data on request, two-factor authentication or certifications such as ISO 27001, so I cannot verify the controls sitting behind my customers' order data. 1 2 6 8 9
The Data Protection Officer
The privacy policy names the vendor as data processor with a downloadable data processing agreement, states data minimization, seventy-two-hour breach notification, trained staff, encrypted transmission and encryption of stored data, and open and click events are tied to tracking being enabled and configurable. What is stored per message and for how long is not described, and we found no public information on two-factor authentication, scoped API keys, IP allow-listing, an audit log, or ISO 27001 or SOC 2 certification — retention silence is the part I weigh hardest. 2 6 8 9
The Agency Lead
The privacy policy is concrete: the company acts as data processor with a downloadable DPA, 72-hour breach notification, data minimization, trained staff, and technical measures from firewalls and intrusion detection to encrypted transmission and encryption covering transactions, access and backups. We found no public information on what is stored per message, retention periods, API key scopes, two-factor authentication, or ISO 27001 or SOC 2 certification. 2 8 9 3
The Skeptic
The privacy policy names concrete measures — multi-level firewalls, antivirus, intrusion detection, SSL/HTTPS/VPN transmission, encryption of stored data, staff training, and 72-hour breach notification — and a DPA is downloadable, with SSL/TLS for SMTP delivery. What I could not find anywhere: what is stored per message, retention periods, two-factor authentication, scoped API keys, an audit log, or any certification such as ISO 27001 or SOC 2 with its scope. 3 8 9
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
Sub-accounts are a real capability — manageable by API with limits, status and white-label, up to 100 on the Pro plan, with per-member sending quotas and reseller branding — and support is described as 24/7, human, multilingual, with a knowledge base and a free WordPress SMTP plugin. But I found no public information on an uptime SLA, service credits, incident history or data-centre redundancy; the public status evidence is a server status OK indicator. 1 2 11 5 8
The Platform Engineer
Sub-accounts are a real product — up to one hundred on the Pro plan with individual quotas and white-label reselling — support is 24/7 human by email, chat and telephone, and there is a free WordPress plugin. But the status evidence is an OK badge with no incident history behind it, and I found no public information on an uptime SLA with service credits, redundancy or failover, queueing of mail during an outage, or support response times per plan — for a login-code pipeline, that is the part I need in writing. 5 1 11 3 8
The Shop Operator
Sub-accounts are the strongest part: up to 100 on the Pro plan, manageable by API with individual sending quotas, central monitoring and white-label resale under my own brand, with fixed quotas even assignable to individual team members. Support is 24/7 human help by email, online chat and telephone in several languages, with a knowledge base, FAQ and articles, and the site carries a server status indicator reading OK. We found no public information on a status page with incident history, an uptime guarantee or migration help, and the only shop plugin documented is for WordPress — nothing for Shopware, which is the plugin I would actually install. 1 2 3 5 8 9 11
The Data Protection Officer
There is 24/7 human multilingual support via email, chat and telephone, a public server-status indicator, knowledge base and FAQ, sub-accounts up to one hundred on the Pro plan with individual quotas and white-label reselling under the customer's own brand, and a free WordPress plugin. We found no public information on an uptime SLA, incident history, redundancy across data centres, or response times per plan. 1 2 3 5 11
The Agency Lead
For my thirty clients this is the strongest part: sub-accounts with individual sending quotas managed through the API, up to 100 on the Pro plan, white-label reselling where each client gets their own statistics area, plus a free WordPress SMTP plugin and 24/7 multilingual support by email, chat and phone. We found no public information on an uptime SLA, an incident history behind the server-status badge, support response times per plan, or granular roles so a client could see only their own logs. 1 2 11 8 3
The Skeptic
Sub-accounts are the genuine strength here — manageable by API with limits, status and white-label, resellable quotas on the Pro plan, with sending quotas assignable per team member — alongside 24/7 multilingual support by email, chat and telephone, and WordPress plugins. But "SERVER STATUS OK" is an indicator on a page, not a status page with incident history, and we found no public information on an uptime SLA, incident history, redundancy, or support response times per plan. 1 2 5 8 11
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 an Italian company (the pages name Edisplay srl) with a dedicated EU API endpoint, claims of 100% Italian and European sending infrastructure, and a self-serve data processing agreement under GDPR. The infrastructure claim is a marketing tagline about the sending service rather than a policy statement naming where logs and account data are stored, and I found no public information on a subprocessor list or security certifications. 1 2 4 9 8
The Platform Engineer
The captured pages show an Italian company with a dedicated EU sending endpoint, a claim of 100% European — on one page 100% Italian — infrastructure, and a downloadable data processing agreement. That infrastructure claim is marketing text rather than a privacy-policy statement of where customer data sits, and I found no public information on the hosting providers, a subprocessor list with locations, or security certifications, so the sending chain cannot be verified end to end. 2 1 9 4
The Shop Operator
turboSMTP belongs to Edisplay S.r.l. in Italy and its pages consistently claim 100% European — even 100% Italian — sending infrastructure, with a dedicated EU API endpoint, a downloadable data processing agreement and a GDPR privacy policy covering breach notification and staff access rules. Those European claims are marketing statements; we found no public information naming where customer data is stored, which subprocessors handle hosting, logging, support or payment, or any security certification. For my German and Austrian customer data, that gap between claim and named infrastructure is what I would have to resolve before signing. 1 2 4 8 9 11
The Data Protection Officer
An Italian company contracts for the service, sending infrastructure is described as one hundred per cent European with a dedicated EU API host, and a GDPR data processing agreement is downloadable. Subprocessors are not listed anywhere we captured, no certifications are stated, and the European-infrastructure claim appears as marketing rather than a data-residency statement covering logs and account data. 1 2 4 9
The Agency Lead
An Italian company claiming 100% Italian and European infrastructure, a dedicated EU send endpoint, and a self-service DPA with clear GDPR processor and controller roles give me a workable answer for German clients. The infrastructure claim is marketing wording rather than named data centres, and we found no public information on a subprocessor list with locations or security certifications. 1 2 4 9 11
The Skeptic
The captured pages give different renderings of the company name (eDisplay Srl, eDigital S.r.l.) but both point to an Italian contracting entity, there is a dedicated EU API endpoint, and a "100% Italian/European infrastructure" claim — which is marketing copy about the sending infrastructure, not a privacy-policy statement of where customer data sits. The DPA is downloadable and the GDPR processor role is explicit, yet we found no public information on subprocessors, the hosting provider, whether the EU endpoint covers logs and account data, or any security certification. 1 2 4 9 11
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
Tiers are public with volume and price — Free at €0/month, Basic at €14.95/month with 15,000 email/month, Pro at €79.95/month with 15,000 email/month and up to 100 sub-accounts — and no lock-in is stated for the free offer. The captured pages give different figures for the free tier (200 email/day, 200 free emails/month and 6,000 free emails per month), and I found no public information on overage rates per thousand messages, dedicated IP or add-on pricing, VAT treatment, or tiers above 15,000 emails a month. 1 3 5 11
The Platform Engineer
Three tiers are public with their prices and volumes — Free, Basic at €14.95/month for 15,000 emails, and Pro at €79.95/month for 15,000 emails with sub-accounts — but the captured pages give different figures for the free allowance: 200 emails a day on the pricing page, 200 a month elsewhere on the same capture, and 6,000 a month on other pages. I found no public information on overage rates per thousand messages, dedicated IPs, log retention add-ons, VAT treatment or rollover, so a real annual cost for a given volume cannot be computed. 1 3 5 11
The Shop Operator
Three tiers are public with volume and price: Free at €0/month with 200 email/day (also advertised as 6,000 free emails per month), Basic at €14.95/month with 15,000 email/month, and Pro at €79.95/month with 15,000 email/month plus sub-accounts, webhooks and custom tracking domains; no credit card is needed to start, and sub-account reselling requires the Pro plan. We found no public information on overage rates per additional thousand emails, tiers above 15,000 email/month, dedicated IP or support pricing, or minimum terms for paid plans, so I cannot compute the annual cost for my order volume from the public pages alone. 1 3 5 6 11
The Data Protection Officer
Three tiers are public with their monthly price and volume — Free at €0/month with 200 email/day, Basic at €14.95/month for 15,000 email/month, and Pro at €79.95/month for 15,000 email/month and up to 100 sub-accounts — and sub-accounts are stated to require the Pro plan. The price per additional thousand messages, dedicated IPs and other add-ons are unpriced, and the captured pages give different figures for the free tier's email allowance (200 email/day, 6,000 free emails per month, and 200 free emails/month). 1 3 5 6
The Agency Lead
The tiers are public: Free at €0/month with 200 email/day, Basic at €14.95/month and Pro at €79.95/month, both showing 15,000 email/month, with sub-accounts tied to the Pro plan. We found no public information on the price of additional messages beyond the included volume, dedicated IPs or longer log retention, so the annual cost per client at higher volume is not computable from these pages. 1 3 5 11
The Skeptic
Three tiers are public with their prices — Free at €0/month, Basic at €14.95/month for 15,000 email/month, Pro at €79.95/month for the same 15,000 email/month plus up to 100 sub-accounts — though the captured pages give different figures for the free allowance: 200 email/day, 6,000 free emails per month, and once 200 free emails/month. To compute a real annual bill you still need the overage price per additional thousand, dedicated IP and retention pricing, minimum term, and VAT treatment — we found no public information on any of them, and webhooks appear as a 30-day demo on Free and Basic. 1 3 6 11
European sovereignty — proven facts
2 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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location |
EU only
unverified
Why unverified?This is a marketing tagline about the service's infrastructure, not a privacy-policy statement naming where customer data is stored. |
4/4 pts | 9 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The excerpt shows only the link text; the DPA document itself is not part of the excerpt. |
1/1 pts | 9 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about turboSMTP
Is turboSMTP European?
Not determined: the vendor’s pages as captured do not say where turboSMTP is based.
Where does turboSMTP store data?
turboSMTP stores customer data in the EU, per the vendor’s page captured 17 Nov 2026.
Does turboSMTP have a free plan?
Yes. turboSMTP has a free plan, per the vendor’s page captured 17 Nov 2026.
What are the best alternatives to turboSMTP?
As of 19 Nov 2026, the panel rates Lettermint (3.5/5), Bird Email API (formerly SparkPost) (3/5) and Postmark (3/5) highest among the other 22 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, Netherlands). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: turboSMTP alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 17 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 — Data processing agreement. The excerpt shows only the link text; the DPA document itself is not part of the excerpt.
- Weak sourcing — Hosting location. This is a marketing tagline about the service's infrastructure, not a privacy-policy statement naming where customer data is stored.
- 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.
- 2 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
- 1 compliance 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 hosting 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
Sources (11)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.turbo-smtp.com Checked 17 Nov 2026 Details →
- 2 Sending API, SMTP & developer experience — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 3 Sending API, SMTP & developer experience — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 4 Deliverability & sender reputation — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 5 Deliverability & sender reputation — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 6 Message logs, events & webhooks — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 7 Message logs, events & webhooks — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 8 Message data, retention & security — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 9 Message data, retention & security — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 10 Reliability, accounts & support — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
- 11 Reliability, accounts & support — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →