Transactional Email
Sweego
EU-Made Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by MINDBAZ SAS · www.sweego.io
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.
Sweego at a glance
- Vendor
- MINDBAZ SAS
- Headquarters
- Not stated on the vendor’s pages as of 1 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 1 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 1 Nov 2026
- Panel verdict
- The AI panel rates Sweego 3/5, the mean of 6 judges. Sweego, published by MINDBAZ SAS of Lille, is a transactional email and SMS service sent through a REST API or an SMTP relay. 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
Sweego, published by MINDBAZ SAS of Lille, is a transactional email and SMS service sent through a REST API or an SMTP relay. Its highest scores come on sovereignty, at 7 to 8, resting on a French contracting entity under French law and the French courts, a published processing agreement with customer audit rights and 48-hour breach notification, and a subprocessor list naming OVH Cloud, Scaleway and Alter Way for data hosting in France, with CM.com, Mollie and Hyperline in France and the Netherlands. The judges scoring 7 pointed to the absence of ISO 27001 or SOC 2 certification and to France-based processing resting on the vendor's own statement. Deliverability, observability and pricing transparency each drew a uniform 6; reliability and accounts a uniform 4, with no public information on an uptime SLA, sub-accounts or team roles. Sending sits at 5 to 6 and data and security at 4 to 5; the pages show no public information on idempotency keys, rate limits, two-factor authentication, encryption at rest or certifications. No meaningful disagreement was computed between the judges.
Speaks for it
- Sender authentication is documented as exact DNS records — the SPF include, a DKIM CNAME with a 2048-bit minimum key, a return-path CNAME for bounce routing
- Hard-bounced addresses are automatically suppressed for 90 days, with further sends blocked before any delivery attempt
- The published processing agreement grants customer audit rights, 48-hour breach notification, and deletion or return of data at contract end
- Real-time searchable logs keep one record per email, statistics break down by mailbox provider, and webhooks are signed with a documented retry schedule of every five minutes up to twenty attempts
- Public pricing spans a 0€ free tier (100 emails a day, no credit card) to Startup at 63€ excl. tax and Scaleup at 216€ excl. tax, with no minimum term
Held against it
- No public information on an uptime SLA, service credits, incident history, sub-accounts or team roles — reliability and accounts scored a uniform 4
- No public information on two-factor authentication, SSO, encryption at rest, API-key scopes or ISO 27001 and SOC 2 certifications
- The overage is described only as available with no rate per thousand, and no price is published for the Individual tier, so a full annual cost cannot be computed from the captured pages
- No public information on idempotency keys, scheduled sending, rate limits or an OpenAPI specification for the sending API
- Viewing the suppression list from the dashboard or the API is not yet available, per the vendor's own documentation, with the feature planned for a future release
Best for
- You send transactional mail from a Symfony, WordPress (Post SMTP) or Odoo stack and want a documented REST API and SMTP relay with a dry-run test mode
- Your procurement requires a French contracting entity under French law, a published processing agreement with audit rights, and named EU subprocessors for hosting
- You want to validate the integration before committing — a 0€ free tier at 100 emails a day with no credit card and no minimum term
- You need to answer 'did this specific message arrive?' with per-mailbox-provider statistics, real-time logs and signed webhooks
Avoid if
- You must view or manage your suppression list from the dashboard or the API — the vendor's documentation states this is not yet available and is planned for a future release
- You send more than one million emails a month and need a published price — beyond that volume the plan becomes contact sales
- Your policy requires vendor-maintained integrations — beyond the official Symfony components, the catalogue entries are community-maintained
- You need inbound email routing on the free tier — the pricing page lists inbound routing as not included on Free
The scores
| Criterion | Panel median |
|---|---|
| Sending API, SMTP & developer experience | 3 of 5 |
| Deliverability & sender reputation | 3 of 5 |
| Message logs, events & webhooks | 3 of 5 |
| Message data, retention & security | 2.5 of 5 |
| Reliability, accounts & support | 2 of 5 |
| European sovereignty | 4 of 5 |
| Pricing transparency | 3 of 5 |
Sending API, SMTP & developer experience
Show reasoningHide reasoning
How this is scored
How an application sends mail: a REST API and an SMTP relay with their limits stated, official SDKs and drivers for named languages and frameworks (PHP and Laravel, Node, Python, Ruby and Rails, Java, Go, .NET), stored templates with variables and versions, batch sending, attachments, idempotency keys, scheduled sending, a test or sandbox mode that does not deliver, inbound email parsed into a webhook, and the quality of the API reference and guides.
0 — Not a sending service; an application cannot send email through it by API or SMTP.
3 — An API or SMTP credentials to send a message; SDKs, templates, limits and a test mode are basic or not described.
5 — A documented REST API and SMTP relay, official SDKs for several named languages, stored templates with variables, attachments and batch sending, rate limits stated, a sandbox or test mode, and quick-start guides for named frameworks.
8 — An API reference with every endpoint and error code, idempotency keys, scheduled sending, template versions and a template language documented, inbound email parsed to a webhook, an OpenAPI specification or official CLI, framework drivers maintained by the vendor, and a migration guide from named competitors.
10 — An API a team builds its product on: versioning and deprecation policy published, backward compatibility stated, full parity between API and SMTP features, local or staging test tooling that mirrors production, and every limit, timeout and retry behaviour documented.
The SaaS Developer
The sending API is documented down to parameter level — a REST endpoint for single sends, a bulk endpoint capped at 200 recipients with per-recipient variables, template IDs, base64 attachments, a 20 MB size cap, and a dry-run flag so nothing reaches a real inbox — alongside an SMTP relay with STARTTLS on ports 2525 and 587 and code samples across eight languages including PHP. The only vendor-maintained framework component named is Symfony; we found no public information on a Laravel driver, idempotency keys, scheduled sending, an OpenAPI specification or a migration guide. 3 12 13 7 19
The Platform Engineer
The REST send endpoint and the SMTP relay are both documented (STARTTLS on port 587 or 2525), with code samples across nine named languages, templates with variables, base64 attachments, a bulk endpoint capped at 200 recipients with per-recipient variables, and a dry-run parameter plus a sandbox mode that keeps test mail out of production. Inbound email routing exists as a channel on paid plans, and the official Symfony components are backed by community plugins for WordPress, Odoo and Terraform. We found no public information on idempotency keys, scheduled sending, rate limits, or inbound mail parsed into a webhook. 12 13 7 2 19
The Shop Operator
A REST endpoint with Api-Key auth and an SMTP relay on STARTTLS ports 2525/587, with code examples in PHP, Node, Python, Go and more, templates with variables like name and order, attachments, bulk sending up to 200 recipients per request, and a dry-run test mode that delivers nothing — my developer can drive our order mail with this. I found no documented rate limits, idempotency keys or scheduled sending, and the PHP story is an official Symfony integration rather than anything for Shopware. 3 12 13 7 19
The Data Protection Officer
The REST send endpoints and the SMTP relay are documented down to their limits — up to 200 recipients per bulk request, 20 MB per message, five custom headers — with attachments in base64, templates carrying variables, and a dry-run test mode, and code examples cover nine languages. We found no public information on idempotency keys, scheduled sending or template versioning, which my developers would need before routing appointment reminders through the service. 2 3 7 12 13
The Agency Lead
The sending documentation is deeper than most at this size: a REST endpoint for single sends plus a bulk endpoint with per-recipient variables and up to 200 recipients a request, base64 attachments, custom headers, a dry-run flag that simulates sending, SMTP with STARTTLS on port 2525 or 587, and code examples across nine languages including PHP, Node and Java. Stored templates with a builder and variables, and inbound email routing from the paid tiers onward, round it out. We found no public information on idempotency keys, scheduled sending, an OpenAPI specification or published rate limits, so it sits one notch above the middle documented level. 3 12 13
The Skeptic
The sending documentation is concrete: two REST endpoints with payload fields and hard limits (20 MB messages, 200-recipient bulk batches, five custom headers), base64 attachments, template IDs with personalisation variables, dry-run mode, and an SMTP relay on ports 587 and 2525 with mandatory STARTTLS and mandatory verified subdomains. Code samples cover eight languages and the Symfony components are official, though nearly every other platform integration is community-maintained. I found no public information on idempotency keys, scheduled sending, template versioning, an OpenAPI specification, a migration guide, or per-second rate limits. 12 13 3 7 2
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
Authentication is documented at the record level — an SPF include, a DKIM CNAME with 2048-bit minimum keys, a custom return-path CNAME for bounce routing and DMARC reporting — and hard bounces are auto-suppressed for 90 days with sends blocked before delivery, plus complaints monitoring and a feedback loop delivered via SFTP. We found no public information on shared-pool vetting, dedicated-IP warm-up, separation of transactional and marketing traffic, or published delivery times. 14 15 7 4 16
The Platform Engineer
Authentication is properly documented — SPF include, DKIM CNAME with 2048-bit keys, a return-path CNAME for bounce routing, and a mandatory verified subdomain — and a user-unknown hard bounce lands on an automatic 90-day suppression list with a visible log marker; statistics per mailbox provider, complaints monitoring and a feedback loop delivered via SFTP go beyond the basics. We found no public information on dedicated-IP warm-up, a vetting policy for the shared pool, a statement on the Gmail and Yahoo sender rules, or published delivery times, and the vendor itself documents that viewing the suppression list from the dashboard or API is planned for a future release. 14 15 7 4 13
The Shop Operator
The sender-authentication guide spells out the exact SPF include, DKIM CNAME and return-path CNAME to paste — the guided setup a non-specialist like me needs — and hard bounces are auto-suppressed for 90 days with sends blocked before delivery, plus complaint handling, a feedback loop via SFTP and statistics per mailbox provider. We found no public information on shared-pool vetting, dedicated-IP warm-up, published delivery times or a named deliverability expert to call when Gmail refuses; separating order mail from newsletters is a header choice, not a documented separate stream. 14 15 7 16 4 12
The Data Protection Officer
Sender authentication is documented concretely — the SPF include, a 2048-bit minimum DKIM key via CNAME, and a custom return-path CNAME that routes bounces to their servers — and a hard bounce (user unknown) is automatically placed on a suppression list for 90 days that blocks further sends before any delivery attempt, with one-click list-unsubscribe implemented and the feedback loop delivered via SFTP. We found no public information on dedicated-IP warm-up, how senders on shared pools are vetted, or published delivery times and inbox placement. 4 7 12 14 15 16
The Agency Lead
Authentication is documented concretely — an SPF include, a DKIM CNAME with a 2048-bit minimum key, a custom return-path CNAME for bounce routing, and DMARC reporting — and a built-in suppression list blocks further sends to a hard-bounced address for 90 days before any delivery attempt. Dedicated, pooled and shared IPs are offered, with a dedicated IP included on the Scaleup plan and an additional IP at 30€/month. We found no public information on automatic IP warm-up, vetting of senders on the shared pool, or stated compliance with the Gmail and Yahoo bulk-sender requirements, though one-click list-unsubscribe headers are supported. 7 14 15
The Skeptic
Authentication set-up is genuinely guided — an SPF include, a DKIM CNAME with 2048-bit keys, a DMARC explanation, and a return-path CNAME for bounce routing — and hard bounces land on an automatic 90-day suppression list that blocks re-sends before any delivery attempt, which is more honesty than most deliverability pages show; the vendor itself states the suppression list is not yet viewable from the dashboard or API. Feedback loops arrive via SFTP and there is a blocking check plus per-mailbox-provider statistics. I found no public information on shared-pool vetting, dedicated-IP warm-up, separation of transactional and marketing streams, Gmail and Yahoo bulk-sender compliance, or published delivery times. 14 15 4 16 7
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
This is close to what I need for the "did the user get the reset mail?" question: real-time searchable logs with advanced filters, retention stated per plan at 7, 30, 60 and 90 days, log export via SFTP, and webhooks that are signed, retried every 5 minutes up to 20 attempts, restrictable per domain, and multiple on higher plans. We found no public information on an events API, alerts on bounce or complaint spikes, or read-only access for support staff, and the docs state themselves that viewing the suppression list from the dashboard or API is not yet available. 4 16 17 7 15
The Platform Engineer
Logs are searchable with advanced filters at one record per sent message, retention is stated per plan at 7, 30, 60 and 90 days, statistics break down per mailbox provider and per domain, and the webhooks are signed with a documented retry schedule — every five minutes, twenty attempts, up to one hour and forty minutes of coverage. For my pager the gaps matter: we found no public information on alerts for bounce or complaint spikes, per-message raw SMTP responses, read-only access for support staff, or an API to fetch the event history itself; only the audit log has a documented API. 17 16 4 7 1
The Shop Operator
One record per sent email, searchable in real time with advanced filters, log retention stated per plan at 7 to 90 days, signed webhooks retried every five minutes up to twenty attempts with the schedule published, statistics per mailbox provider and domain, and an audit log reachable through an API. We found no public information on native alerts for bounce spikes, read-only access for support staff, or viewing the receiving server's raw answer per message. 4 16 17 18 7
The Data Protection Officer
Logs are searchable in real time with advanced filters, one record per email, retention tied to the plan at 7 to 90 days, statistics broken down by mailbox provider, suppressed sends marked in the log, export by SFTP, and webhooks that are signed with a documented retry schedule of every five minutes up to twenty attempts. We found no public information on bounce or complaint spike alerts, an events API, the raw SMTP answer per message, or read-only access for support staff. 2 4 7 15 16 17
The Agency Lead
Message observability is solid for my team: real-time searchable logs with advanced filters, retention stated per plan at 7 to 90 days, retrieval by SFTP, and statistics broken down by mailbox service provider, domain and dates. Webhooks are signed, retried every 5 minutes up to a maximum of 20 attempts with the schedule documented, restricted to chosen domains, and multiple webhooks arrive from the Startup plan upward. We found no public information on bounce or complaint spike alerts, read-only roles for support staff, or an API for fetching message events, which keeps it one step short of the higher documented level. 4 7 16 17
The Skeptic
Webhooks are the strong part: signature validation documented, retries every five minutes up to twenty attempts with the window stated, domain-level routing, and log retention stated per tier at 7 to 90 days; logs are real-time with advanced filters, detailed bounce statistics, per-provider insights, and export via SFTP. I found no public information on the raw SMTP response per message, a rendered-message view, an events API, alerts on bounce or complaint spikes, or read-only roles for support staff, and webhook subscriptions cover email sending only. 17 16 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
STARTTLS is required on the SMTP relay, TLS is listed among the email features, retention is stated per plan and in the DPA (delete or return everything at contract end), a DPA with customer audit rights and 48-hour breach notification is published, and the audit log is documented in real depth — per-resource actions, originating IP, user, timestamp and an API endpoint with date filters. We found no public information on two-factor authentication, SSO, scoped API keys, per-stream tracking opt-outs, or ISO 27001 and SOC 2 certifications. 7 13 16 18 10
The Platform Engineer
There is a real data processing agreement with customer audit rights, 48-hour breach notification and documented deletion or return at contract end, audit logs of configuration changes and logins with their own API endpoint, enforced STARTTLS on the relay, and stated retention terms. For a fintech most of the rest of the checklist is unanswered: we found no public information on two-factor authentication, scoped or restricted API keys, IP allow-listing, SSO, encryption at rest, certifications, or switching open-and-click tracking off per message or stream. 10 13 18 9 1
The Shop Operator
Retention periods are stated (log retention per plan, tracers up to 13 months, deletion at end of engagement), SMTP delivery requires STARTTLS, unlimited API keys can be created, and a published data processing agreement grants customer audit rights, 48-hour breach notification and recipient erasure rights. Two-factor authentication, SSO, API-key scopes, encryption at rest and certifications are not documented on the captured pages, so the dashboard controls my shop would lean on remain unconfirmed. 7 13 10 9 18
The Data Protection Officer
The processing agreement names MINDBAZ as processor, promises deletion or return of personal data at contract end, breach notification within 48 hours and customer audit rights, and the audit log records logins and configuration changes with originating IP and is retrievable by API. But retention is fixed by plan tier rather than a setting, and we found no public information on whether message bodies are stored, whether open and click tracking can be switched off per stream or message, two-factor authentication, SSO, encryption at rest, or certifications such as ISO 27001 or SOC 2 — the first questions I put to any processor carrying patient names. 4 7 10 16 18
The Agency Lead
The published data processing agreement is unusually strong — customer audit rights, breach notification within 48 hours, processing only on documented instruction, deletion or return of data at contract end — and the audit log records configuration changes and logins with timestamp and originating IP, queryable through its own endpoint. TLS covers delivery through SMTP STARTTLS and log retention is stated per tier. We found no public information on two-factor authentication, SSO, scoped API keys, encryption at rest, switching open and click tracking off, or ISO 27001 and SOC 2 certifications. 7 10 13 18
The Skeptic
The audit log is better than most — every configuration change and login with timestamp and originating IP, a documented API endpoint with date filtering, and a full resource table — and it sits on a real DPA granting customer audits and 48-hour breach notification, with message-log retention of 7 to 90 days by plan, TLS, enforced STARTTLS on submission, unlimited API keys, and data returned or deleted at contract end. But I found no public information on two-factor authentication, SSO, key scopes, IP allow-listing, encryption at rest, switching open and click tracking off, deletion of a recipient's data by API, or any ISO 27001 or SOC 2 certification — and what is stored per message is described only as one record per email. 18 10 7 13 16
Reliability, accounts & support
Show reasoningHide reasoning
How this is scored
Whether the platform can be relied on and run by a team: a public status page with incident history, uptime SLA and service credits published, redundancy or failover across data centres described, queueing and retry of mail during outages, sub-accounts or servers per application, client or tenant, team members with roles, separate environments, support channels and response times per plan, named migration help, and integrations with platforms that send mail on the customer's behalf (WordPress, Shopify, Shopware, Supabase, Vercel and similar).
0 — No status page, no support channel and no way to separate users or applications.
3 — A support contact and a single account; status page, SLA, sub-accounts and roles are basic or not described.
5 — A public status page with incident history, an uptime SLA on at least one plan, sub-accounts or separate servers per application, team members with roles, support by email or chat with stated hours, and plugins or guides for several named platforms.
8 — An SLA with service credits published, redundancy across data centres or regions described, mail queued and retried during incidents, sub-accounts with their own keys, domains and limits manageable by API, granular roles, support response times per plan, and migration assistance offered.
10 — Reliability that can be verified: uptime history published for years, post-mortems for incidents, multi-region failover documented, an SLA covering delivery latency as well as API availability, and white-label or reseller tooling for agencies and platforms.
The SaaS Developer
A status page exists, support runs on Slack for free accounts and chat and email on paid plans, and there is a genuinely broad integration catalogue — WordPress via Post SMTP with its own logs and one-click resend, Odoo modules, Payload, a Terraform provider, and official Symfony components — though most entries are community-maintained. We found no public information on an uptime SLA or service credits, incident history, queueing of mail during outages, team roles, or support response times per plan. 7 19 20 18
The Platform Engineer
A status page exists, support runs on Slack for free accounts and chat-and-email on paid plans, and the ecosystem includes official Symfony components plus WordPress, Odoo, Payload and Terraform integrations. We found no public information on an uptime SLA with service credits, incident history, mail queued and retried during outages, sub-accounts with their own keys, or team roles and per-plan response times — the things I check first when login codes stop arriving. 7 19 20 8
The Shop Operator
There is a public status page, support runs via Slack on the free tier and chat plus email on paid plans, a test mode serves as a separate environment, and integrations exist for WordPress, Odoo, Payload and official Symfony components — but no Shopware plugin appears anywhere, which is the platform my kitchen shop runs on. No uptime SLA, incident history, per-plan response times or team roles are documented. 7 19 20 18
The Data Protection Officer
A public status page exists, support runs on Slack for free accounts and chat and email on paid plans, and there is a wide integration ecosystem including official Symfony components, WordPress via Post SMTP with detailed documentation, and Odoo, Payload CMS and Terraform providers, mostly community-maintained. We found no public information on an uptime SLA or service credits, incident history, team roles, sub-accounts per application, or support response times by plan. 7 19 20
The Agency Lead
For running client platforms there is real substance: a status page, chat and email support on paid plans with a Slack channel on the free tier, and an integration shelf covering Post SMTP for WordPress, Odoo modules, Symfony, Payload CMS, Convex and a Terraform provider for provisioning domains as code. Unlimited API keys and SMTP access can be created, which helps separate clients. What I actually need — sub-accounts with their own keys, domains and limits, team roles so a client sees only their own logs, and a published SLA with service credits — we found no public information on. 1 7 19 20
The Skeptic
There is a status page, Slack assistance on the free plan, chat and email on paid plans, and an unusually rich integration shelf from WordPress and Odoo to Payload, Convex and Terraform — though almost all community-maintained rather than vendor drivers, and the free plan excludes inbound routing. I found no public information on an uptime SLA or service credits, incident history, sub-accounts, team members with roles, support response times, redundancy or failover, or named migration help. 7 19 20 6 2
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Who the contracting entity and the parent company are, where messages, logs and recipient data are processed and stored, whether an EU region can be chosen and what it covers, and who the subprocessors are (cloud hosting, sending infrastructure, logging, support and payment tools). Independently sourced by the sovereignty pipeline; every message carries personal data, so the whole sending chain counts, not only the dashboard.
0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors unnamed, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist, but hosting location is unstated or non-EU and the subprocessors are not listed.
5 — An EU region available and an EU contracting entity or EU representative, but parts of the chain (sending infrastructure, logs, support, payment) run through non-EU providers without a stated safeguard, or the EU region does not cover logs and account data.
8 — EU processing of messages, logs and account data on named infrastructure, an EU contracting entity, subprocessors listed with their locations, a data processing agreement published, and security certifications (ISO 27001, SOC 2) stated.
10 — Sovereign end to end and evidenced: European ownership, entity, hosting, sending infrastructure and every subprocessor, data export and deletion documented, and certifications published with their scope rather than implied.
The SaaS Developer
The contracting entity is MINDBAZ SAS in Lille under French law and French courts, the vendor describes itself as GDPR-compliant and "based in France (datacenters included)", and the published subprocessor list names its data hosting on OVH Cloud, Scaleway and Alter Way — all in France — with the only non-French entries being Dutch SMS and payment providers, so the whole chain stays in the EU. The DPA adds audit rights, 48-hour breach notification, records of processing and documented deletion or return of data; we found no public information on ISO 27001 or SOC 2 certification with its scope. 8 10 11 1 9
The Platform Engineer
The whole chain reads European: a French contracting entity in Lille under French law and French courts, datacenters in France, hosting on named French providers (OVH Cloud, Scaleway, Alter Way), a published subprocessor list where even the SMS and payment providers are EU-based, and a data processing agreement with audit rights and documented deletion. The one missing piece is certifications — we found no public information on ISO 27001 or SOC 2. 8 11 10 1 9
The Shop Operator
The publisher is MINDBAZ SAS, registered in Lille, France, under French law and French courts, the vendor's own pages state it is based in France with datacenters included, and the public subcontractor list names OVH Cloud, Scaleway and Alter Way in France for hosting plus CM.com and Mollie in the Netherlands for SMS and payment, all under a published data processing agreement. No ISO 27001 or SOC 2 certification is stated, and the independently computed sovereignty attributes could not confirm residency beyond the vendor's own claim, so I stop short of the top band. 8 11 10 1 2
The Data Protection Officer
The contracting entity is MINDBAZ SAS of Lille under French law and the French courts, the published processing agreement applies specifically to the Sweego service, and the subprocessor list names OVH Cloud, Scaleway and Alter Way for data hosting in France with CM.com, Mollie and Hyperline in France and the Netherlands — every subprocessor inside the EU, with transfers outside it only on documented instruction. The vendor states it is GDPR-compliant, based in France with datacenters in France. We found no public information on certifications such as ISO 27001 or SOC 2, so the French hosting position rests on the vendor's own word rather than an audited scope. 1 8 9 10 11
The Agency Lead
The chain is European as published: MINDBAZ SAS in Lille is the contracting entity under French law and the French courts, the vendor states it is based in France with datacentres included, and the subprocessor list names every link with its location — OVH Cloud, Scaleway and Alter Way hosting data in France, CM.com in the Netherlands for SMS, Mollie in the Netherlands for payments, Hyperline in France for billing. The data processing agreement is published with audit rights and documented deletion or return at contract end. We found no public information on ISO 27001 or SOC 2 certification, the one open item against a fully evidenced sovereign profile. 2 8 10 11
The Skeptic
The contracting entity is MINDBAZ SAS of Lille under French law and French courts, the DPA is published with article-level GDPR commitments including third-country transfers only on documented instruction, and the subprocessor list is named with locations: three French data hosts (OVH Cloud, Scaleway, Alter Way), a French billing system, and Dutch SMS and payment providers — all inside the EU. What holds me back is that France-based processing rests on a marketing bullet, "based in France (datacenters included)", plus the hosting subprocessors, with no explicit residency statement for message content and logs; I found no public information on security certifications behind the chain. 8 11 10 1 9
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
Much of the annual cost is computable: the free tier at 0€ with 100 emails a day, Startup at 63€ excl. tax and Scaleup at 216€ excl. tax with their volumes, an additional IP at 30€ per month, 20% off on annual billing, SMS at a published price with 12-month credit validity and no setup fee, log retention stated per tier, and no minimum term. The overage is only described as "available" with no rate published, the captured pages give no price for the Individual tier, and above one million emails it is contact sales; we found no public information on SSO or support-plan add-on pricing. 7 2
The Platform Engineer
Tiers are public with volumes and prices excluding VAT — Free at 0€ for 100 emails a day, Startup at 63€ excl. tax, Scaleup at 216€ excl. tax, custom above one million — plus no minimum engagement, log retention stated per tier, a 20% annual saving, an additional IP at 30€/month and a separate SMS price list. Overage is described as available but the per-thousand rate is not stated, so I cannot compute a real annual cost from the pricing page alone. 7 2
The Shop Operator
The pricing page is concrete enough to budget with: a free tier at 100 emails a day, Startup at 63€ excl. tax for 100 K or 200 K monthly, Scaleup at 216€ excl. tax for 500 K or 1 M, an additional IP at 30€/month, log retention per tier, a 20% annual saving, no minimum term and published SMS prices valid twelve months. The overage rate is only described as available without a figure, and above one million emails it becomes a contact-sales plan, so the ceiling cost is not computable from public pages. 7 2
The Data Protection Officer
Tiers are public with volumes and prices excluding tax — 0€ for 100 emails a day, Startup at 63€ for 100 K or 200 K emails, Scaleup at 216€ for 500 K or 1 M, a dedicated additional IP at 30€ a month, an SMS price list with credits valid twelve months, log retention stated per tier, a 20% annual saving and no minimum engagement or credit card. The overage is described only as available with no rate per thousand, and we found no public information on the price of the Individual tier or of support plans, so a buyer cannot fully compute a year's cost from the captured pages. 2 7
The Agency Lead
Most of the contract maths is public: the free tier at 0€ with 100 emails a day, Startup at 63€ excl. tax for 100 K or 200 K emails a month, Scaleup at 216€ excl. tax for 500 K or 1 M, an additional IP at 30€/month, a 20% annual saving, log retention by tier, VAT treatment and the no-minimum-term promise all stated. The volume steps for the Individual tier are shown but we found no public price for that tier, and the overage is listed only as available with no rate per additional thousand. We found no public information on SSO or support-plan add-ons. 2 7
The Skeptic
Startup at 63€ excl. tax and Scaleup at 216€ excl. tax are published with their monthly volumes, the free tier (0€, 100 emails a day) and its limits are clear, an additional IP costs 30€/month, annual billing saves 20%, there is no minimum term, and log retention per tier is stated. But the overage rate per extra thousand messages is not stated, we found no public information on the price of the Individual tier even though its volume appears in the tier table, and beyond one million emails it becomes a sales conversation. 7 2
European sovereignty — proven facts
0 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined ⚠ unverified | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined ⚠ unverified | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Sweego
Is Sweego European?
Yes. whats-best.ai classifies Sweego as EU-Made.
Where does Sweego store data?
Not stated on the vendor’s pages as of 1 Nov 2026.
Does Sweego have a free plan?
Yes. Sweego has a free plan, per the vendor’s page captured 1 Nov 2026.
What are the best alternatives to Sweego?
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: Sweego 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 — Data processing agreement, Hosting location, Legal entity. 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.
- 5 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
- 2 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
- 1 legal 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 subprocessors 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
- 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 (20)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor homepage www.sweego.io Checked 1 Nov 2026 Details →
- 2 Features page (transactional email) www.sweego.io Checked 1 Nov 2026 Details →
- 3 Features page (API and SMTP) www.sweego.io Checked 1 Nov 2026 Details →
- 4 Features page (observability and deliverability) www.sweego.io Checked 1 Nov 2026 Details →
- 5 Integrations page www.sweego.io Checked 1 Nov 2026 Details →
- 6 Documentation learn.sweego.io Checked 1 Nov 2026 Details →
- 7 Pricing page www.sweego.io Checked 1 Nov 2026 Details →
- 8 Legal notice www.sweego.io Checked 1 Nov 2026 Details →
- 9 Privacy policy www.sweego.io Checked 1 Nov 2026 Details →
- 10 Data processing agreement (dpa) www.sweego.io Checked 1 Nov 2026 Details →
- 11 Subprocessor list www.sweego.io Checked 1 Nov 2026 Details →
- 12 Sending API, SMTP & developer experience — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 13 Sending API, SMTP & developer experience — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 14 Deliverability & sender reputation — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 15 Deliverability & sender reputation — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 16 Message logs, events & webhooks — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 17 Message logs, events & webhooks — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 18 Message data, retention & security — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 19 Reliability, accounts & support — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →
- 20 Reliability, accounts & support — found from sitemap learn.sweego.io Checked 1 Nov 2026 Details →