Panel 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

turboSMTP: AI-assisted analysis on whats-best.ai turboSMTP: AI-assisted analysis on whats-best.ai (dark)

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

turboSMTP alternatives, European ones first →

Read this page as one judge. Each weighs the same scores by what they care about.

The Shop Operator

Weighted verdict

Runs a Shopware shop for kitchen equipment in Germany and Austria with 900 orders a week. Order confirmations, invoices and shipping notices went out through the hosting provider's mail server until a customer found theirs in spam and the support inbox filled up. Wants guided SPF and DKIM set-up a non-specialist can follow, a plugin for the shop, order mail kept apart from the newsletter, and someone to ask when Gmail starts refusing.

Same scores as the panel view — this lens weights them the way this judge cares.

Scored by The Shop Operator

Panel median The Shop Operator This judge’s scores over the panel median. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median The Shop Operator
Sending API, SMTP & developer experience 2 of 5 2 of 5
Deliverability & sender reputation 2 of 5 2 of 5
Message logs, events & webhooks 2 of 5 2 of 5
Message data, retention & security 2 of 5 2 of 5
Reliability, accounts & support 2 of 5 2 of 5
European sovereignty 2.5 of 5 3 of 5
Pricing transparency 2.5 of 5 2.5 of 5

Sending API, SMTP & developer experience

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.

Report an error

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

Report an error

Deliverability & sender reputation

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.

Report an error

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

Report an error

Message logs, events & webhooks

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.

Report an error

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

Report an error

Message data, retention & security

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.

Report an error

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

Report an error

Reliability, accounts & support

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.

Report an error

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

Report an error

European sovereignty

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.

Report an error

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

Report an error

Pricing transparency

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.

Report an error

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

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

Built only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.

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

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.

Sources (11)

The pages every claim on this page was read from — each one checked, dated, and kept verifiable.

  1. 1 Vendor page www.turbo-smtp.com Checked 17 Nov 2026 Details →
  2. 2 Sending API, SMTP & developer experience — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  3. 3 Sending API, SMTP & developer experience — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  4. 4 Deliverability & sender reputation — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  5. 5 Deliverability & sender reputation — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  6. 6 Message logs, events & webhooks — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  7. 7 Message logs, events & webhooks — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  8. 8 Message data, retention & security — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  9. 9 Message data, retention & security — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  10. 10 Reliability, accounts & support — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →
  11. 11 Reliability, accounts & support — found from sitemap serversmtp.com Checked 17 Nov 2026 Details →