Sarbacane
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Sarbacane Software SAS · www.sarbacane.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.
Sarbacane at a glance
- Vendor
- Sarbacane Software SAS
- Headquarters
- Not stated on the vendor’s pages as of 16 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 16 Nov 2026
- Free plan
- Not stated on the vendor’s pages as of 16 Nov 2026
- Panel verdict
- The AI panel rates Sarbacane 2/5, the mean of 6 judges. Sarbacane, a French email-marketing suite rebranding to Positive User, stands on campaign tooling and connectors and falls on sovereignty and unproven infrastructure. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Sarbacane, a French email-marketing suite rebranding to Positive User, stands on campaign tooling and connectors and falls on sovereignty and unproven infrastructure. Campaign and automation, the strongest criterion, scores 6: a drag-and-drop editor, a template Studio, A/B testing with automatic or manual winner selection and a library of more than 50 ready-made journey scenarios are documented. Integrations follow at 5 to 6, naming Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, plus an API secured with HTTPS and TLS 1.2 and a mobile SDK. Deliverability scores 3 to 4: guidance exists, but we found no public information on SPF, DKIM or DMARC set-up, bounce suppression or warm-up. Sovereignty sits at 2 — a French address, the Positive Groupe France entity and a GDPR-compliance claim are shown, while hosting, the data processing agreement and subprocessors are not. Judges spread on consent and proof, 4 to 6, weighing enforced consent controls against undocumented double opt-in and consent source, and on list data control, 3 to 5, where export and single-subscriber deletion are undocumented. The pricing page states no prices.
Speaks for it
- Campaign and automation scores 6, with a drag-and-drop editor, a template Studio and an A/B test documented down to winner criteria and a recommended 100 people per test group.
- Integrations score 5 to 6, naming Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, plus an API secured with HTTPS and TLS 1.2 and a mobile SDK.
- Unsubscribe is enforced rather than advised: a campaign without a free, visible unsubscribe link is blocked from sending.
- Behavioural tracking consent is a per-contact Active/Inactive toggle with a dated record and pixel-consent mapping on import.
- Contact import is documented in depth, with file, paste or manual entry, column mapping and duplicate removal on by default.
Held against it
- Sovereignty scores 2: we found no public information on hosting, data residency, the data processing agreement or the subprocessor chain.
- Deliverability scores 3 to 4: we found no public information on SPF, DKIM or DMARC set-up, bounce or complaint suppression or IP warm-up.
- The exit half of list ownership is unproven — we found no public information on export scope, engagement history or single-subscriber deletion.
- We found no public information on double opt-in, a consent source or IP record, or a preference centre, which caps consent and proof.
- Replace mode permanently deletes all current contacts in a list, with no trash for contacts.
Best for
- You send newsletters and announcements and want a documented editor, template system and A/B testing rather than a journey builder.
- Your stack runs on Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, WordPress or Google Sheets and you want synchronised contact lists.
- You want unsubscribe and tracking-consent rules enforced by the tool rather than left to your team.
- You import large contact lists — files up to 100 MB — and want duplicate removal on by default.
Avoid if
- Your procurement requires documented hosting, a data processing agreement and a subprocessor list; we found no public information on any of them, and sovereignty scores 2.
- You route production email volume and need SPF, DKIM or DMARC set-up, bounce suppression and warm-up documented before switching; we found no public information on them.
- You need behaviour-based journey branching, dynamic content per segment or send-time optimisation; we found no public information on these.
- You need recoverable contact edits — the documented replace mode permanently deletes all current contacts in a list.
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 3 of 5 |
| Deliverability infrastructure | 2 of 5 |
| Consent, proof & tracking limits | 2.5 of 5 |
| List ownership, import & exit | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1 of 5 |
Campaigns & automation
Show reasoningHide reasoning
How this is scored
Building the mail and the journey around it: editor, templates, segmentation, triggered sequences, A/B testing.
0 — Not a campaign tool; mail cannot be composed and sent to a list from the product.
3 — Broadcasts to a list built in an editor with templates, with simple list or tag segmentation; automation and testing are basic or not described.
5 — A drag-and-drop editor with reusable templates, segmentation on subscriber fields or behaviour, automated sequences on common triggers (sign-up, date, click), and A/B testing of campaigns.
8 — A visual journey builder with branching on behaviour and data, dynamic content per segment, send-time optimisation, event triggers from shop or app data, and testing that reports significance rather than raw counts.
10 — Journeys treat the whole lifecycle: event-driven entry from other systems, branching on any attribute or event, holdout groups for measurement, and automations a marketer can read months later without a diagram.
The CRM Manager
The drag-and-drop editor, reusable template and block system, and automated customer-journey campaigns with a library of more than fifty ready-made scenarios are all documented, and A/B testing is described in real depth — automatic or manual winner selection on open or click rate, testable subject, sender and content, with a minimum of 100 people per group recommended. What I cannot see is segmentation proven to run on behaviour rather than fields, journeys that branch, dynamic content, or testing that reports significance rather than raw rates, which caps this below the journey-builder level. 2 3 1 3 1
The Deliverability Engineer
A drag-and-drop editor, Studio-managed templates with reusable blocks and sharing, and a genuinely well-documented A/B test covering subject line, sender and full content with automatic or manual winner selection are all captured, alongside customer-journey automation with fifty-plus ready-made scenarios. We found no public information on journey branching, dynamic content per segment or send-time optimisation, so this sits above the middle level without the journey-builder depth. 2 3 1 3 1
The Data Protection Officer
A drag-and-drop editor with reusable blocks and managed templates, A/B testing across subject, sender and content with automatic winner selection, and automated multi-channel journey scenarios backed by a library of fifty-plus ready-made use cases are all documented. The captured pages do not describe branching on behaviour and data, dynamic content per segment, or tests that report statistical significance. The guidance to use at least one hundred contacts per test group does at least show the vendor thinks about valid results. 1 2 3 1
The Shop Owner
A drag-and-drop editor, reusable templates and blocks, contact segmentation, automated journey workflows with a library of more than 50 ready-made scenarios, and a genuinely documented A/B test with automatic or manual winner selection are all on the record. What I could not find is journey branching on shop events, dynamic content per segment or send-time optimisation, so the abandoned-cart and post-purchase flows my revenue depends on would rest on undocumented ground. 1 2 3 1 1 1
The Integrator
A drag-and-drop editor, a proper template system with preview, isolation, sharing and reusable blocks, and a well-documented A/B test flow covering subject, sender and content with automatic or manual winner selection. Automation is described as multi-channel customer journeys with a library of more than 50 ready-made scenarios, but we found no public information on branching on behaviour or data, dynamic content per segment, or testing that reports significance, so this stops short of a documented journey builder. 1 2 3 1 3
The Skeptic
A drag-and-drop editor, a template Studio with sharing, folders and isolation from campaign edits, and an unusually specific A/B test (test duration, a recommended 100 contacts per group, winner by open or click rate, automatic or manual) clear the mid anchor comfortably. Automated multi-channel journey scenarios and a library of more than 50 ready-made scenarios are documented, but we found no public information on branching on behaviour, dynamic content per segment, or testing that reports significance rather than raw open and click counts. 1 2 3 1 3 1
Deliverability infrastructure
Show reasoningHide reasoning
How this is scored
Whether the mail arrives — authentication, sending reputation, bounce and complaint handling — judged on what the vendor documents rather than the inbox rate it advertises.
0 — The product does not send mail itself; delivery runs through the customer's own mail server with no sending infrastructure provided.
3 — Sending through the vendor's infrastructure with SPF and DKIM set-up for the sender's domain documented; bounce handling and reputation measures are basic or not described.
5 — SPF, DKIM and DMARC guidance with an authenticated custom sending domain, automatic suppression of hard bounces and complaints, and help-centre guidance on deliverability and list hygiene.
8 — Dedicated-IP options with a documented warm-up, seed or inbox-placement testing, engagement-based sunsetting, complaint feedback loops stated, and reputation reporting per sending domain.
10 — Deliverability is operated as a service: reputation monitoring surfaced to the customer, per-domain and per-ISP diagnostics, enforced authentication before first send, and postmaster or blocklist handling the vendor documents doing on the customer's behalf.
The CRM Manager
There is a real deliverability help centre — best-practice collections, spam-placement troubleshooting, sender and domain reputation articles, guidance on choosing between dedicated and shared IP, and priority send orchestration to protect inbox placement. The captured pages give no information on SPF, DKIM or DMARC set-up, bounce or complaint suppression, or IP warm-up, so the mechanics of arrival rest on guidance rather than documented infrastructure. 4 5 1 4
The Deliverability Engineer
There is a real deliverability help centre — dedicated versus shared IP choice, sender and domain reputation, spam-placement troubleshooting — and two things I rate highly: campaigns without an unsubscribe link are blocked from sending, and high-volume sends are regulated by priority orchestration the vendor says protects inbox placement. But the captured pages do not document SPF, DKIM or DMARC set-up, and we found no public information on bounce or complaint suppression, warm-up, feedback loops or seed testing — the infrastructure story is half-written. 4 5 1 4 6
The Data Protection Officer
The help centre carries a dedicated deliverability collection covering dedicated versus shared IP choice, how sender and domain reputation are built, and troubleshooting spam placement, and the vendor describes priority-based send orchestration that protects inbox placement. We found no public information on SPF, DKIM and DMARC set-up, nor on automatic suppression of bounces and complaints. Before I sign off on a sending tool I would want the authentication steps written down, not inferred from a domain-name FAQ. 4 5 1 4
The Shop Owner
There is a deliverability help collection with best practices, spam-placement troubleshooting, dedicated-versus-shared IP guidance, domain and sender reputation articles, and priority orchestration that regulates high-volume sends to protect inbox placement. We found no public information on SPF, DKIM or DMARC set-up, bounce and complaint suppression, IP warm-up or per-domain reputation reporting, so this stays at the documented-basics level. 4 5 1 4
The Integrator
The help centre carries a dedicated deliverability collection covering domain names, sender reputation and the choice between a dedicated and a shared IP, a send-orchestration feature that regulates large sends to protect inbox placement, and a deliverability manager who must approve exceptions. We found no public information stating SPF, DKIM or DMARC set-up for a custom sending domain, and none on automatic suppression of hard bounces or complaints, which is what I would want proven before routing production volume. 4 5 1 4 6
The Skeptic
The help centre documents deliverability and domain-name collections, the dedicated-versus-shared IP question, sender and domain reputation, spam-placement troubleshooting, and priority orchestration that throttles large sends to protect inbox placement. But we found no public information on SPF, DKIM or DMARC set-up, hard-bounce or complaint suppression, or a documented warm-up, so the authentication and hygiene half of the picture is missing from the captured pages. 4 5 1 4 6
Consent, proof & tracking limits
Show reasoningHide reasoning
How this is scored
How subscribers arrive and what the sender can prove afterwards: double opt-in, logged consent, unsubscribe handling, and whether open and click tracking can be limited or switched off.
0 — Not built for consent at all: the vendor describes the list as imported addresses, with no sign-up forms and no opt-in confirmation in the product.
3 — Sign-up forms, double opt-in available and an unsubscribe link in every mail; the consent record and tracking controls are basic or not described.
5 — Double opt-in documented with a consent record per subscriber (timestamp and source), one-click unsubscribe, and open or click tracking that can be switched off.
8 — Consent is reproducible as evidence: double opt-in as the default, the confirmation mail and form wording stored per subscriber with IP, unsubscribe honoured across lists, a preference centre, tracking off by default available, and retention rules for inactive subscribers.
10 — Built for the burden of proof: a per-subscriber consent history an authority would accept, documented handling of Art. 15 access and Art. 17 erasure requests, pixel-free and link-tracking-free sending as a supported mode, and preference-centre granularity rather than all-or-nothing.
The CRM Manager
Unsubscribe handling is enforced rather than advised — a campaign without a free, visible unsubscribe link is blocked from sending, unsubscribes feed an opt-out list, and a two-click confirmation is offered — while behavioural tracking is consent-gated per contact with an Active/Inactive toggle, a dated consent record, and pixel-consent mapping on import. I found no public information on double opt-in, a consent source or IP record, or a preference centre, so proof of consent is thinner than the tracking controls. 6 7 1 6 7
The Deliverability Engineer
Per-contact tracking consent with an Active/Inactive toggle — links still work while opens and clicks simply go unmeasured — plus a consent date updated automatically and an import step that maps the pixel-consent column, is genuinely strong, and the unsubscribe link is mandatory with its absence blocking the send entirely. We found no public information on double opt-in, one-click unsubscribe or a preference centre, which is what caps this level. 6 7 8 6 7
The Data Protection Officer
The tracking limits are the strongest part: a per-contact Active/Inactive toggle stops opens and clicks being measured while links keep working, pixel consent can be mapped on import, and a campaign without an unsubscribe link is blocked outright. But the arrival story is thin — we found no public information on double opt-in, and the consent record is a date that updates automatically on toggle, with no source or IP shown. A record that rewrites its own date bends under a complaint. 6 7 8 6 7
The Shop Owner
Unsubscribe is enforced — a campaign without a free, visible unsubscribe link is blocked from sending, unsubscribed contacts land on an opt-out list, and behavioural tracking consent (opens and clicks) is a per-contact Active/Inactive toggle with a dated state, explicit consent required for pixels and tracked links, links still working when consent is off. We found no public information on double opt-in or a preference centre, and the documented confirmation mode is two-click rather than one-click. 6 7 6 7
The Integrator
Tracking consent is a first-class object: a per-contact Active/Inactive toggle with an automatically dated record, explicit consent required before tracked links and pixels, and when inactive the links still work while opens and clicks go unmeasured. Unsubscribe is enforced at send time — a campaign without a link is blocked — with two-click confirmation and an opt-out list that excludes future sends; we found no public information on double opt-in, a preference centre, or a per-subscriber consent history with IP that would serve as evidence. 7 9 6 7
The Skeptic
Unsubscribe is enforced rather than advised: a campaign without a free, visible link is blocked, opt-outs join an opt-out list excluded from future sends, and a two-click confirmation is recommended. Behavioural tracking is a per-contact Active/Inactive toggle where opens and clicks are not measured when off, with an auto-updated consent date and an import mapping for the pixel-consent column — but we found no public information on double opt-in, a stored consent record with source and IP, or a preference centre. 6 7 9 8 6 7
List ownership, import & exit
Show reasoningHide reasoning
How this is scored
Whether the list and its history remain the sender's: import with attributes intact, full export including engagement history, deletion that executes, and no metering that prices leaving out of reach.
0 — The vendor states that the list cannot be exported; subscriber data stays inside the product.
3 — CSV import and export of subscribers with their fields; engagement history, unsubscribe state and deletion are basic or not described.
5 — Import with field mapping, subscriber export including custom fields and subscription or unsubscribe status, deletion of a subscriber on request, and an API to read and write the list.
8 — Everything exportable in open formats — subscribers, engagement history, campaigns and templates — with documented deletion of a subscriber across all records, and no export throttling.
10 — Exit is a documented feature: full-fidelity export of the whole account, contractual data return, deletion that is evidenced rather than asserted, and migration tooling in both directions.
The CRM Manager
Import is documented properly — file, paste or manual entry, automatic and manual column mapping, new column creation, replace-or-append with a clear warning that replace permanently deletes contacts, duplicate removal on by default, and a source column per contact. I found no public information on export of subscribers or engagement history, per-subscriber deletion on request, or API access to read and write the list, so the exit half of ownership is unproven. 8 9 8 9
The Deliverability Engineer
Import is documented in depth — file, manual and paste methods, suggested and manual column mapping, replace or supplement behaviour with permanent deletion and no trash for contacts, duplicate removal on by default. Export is only glimpsed in passing as "a Sarbacane export", and we found no public information on export scope, engagement history leaving the platform or single-subscriber deletion, so exit is where this thins out. 8 9 10 8
The Data Protection Officer
Import is thorough — file, paste or manual entry, column mapping with new columns, replace-or-supplement with duplicate removal on by default — and lists can synchronise automatically with business applications. An export is implied by import guidance referring to a Sarbacane export, but we found no public information on exporting engagement history or on documented deletion of a single subscriber across records, and replace mode permanently deletes contacts with no trash to recover from. 8 9 10 8 1
The Shop Owner
Import is well documented — xlsx, txt or csv with suggested and manual column mapping, new columns, replace-or-append, duplicate handling and a 100 MB limit — and lists can be synchronized from business applications. We found no public information on exporting subscribers with engagement history, deleting a single subscriber on request, or API access to the list; the only deletion described is a permanent whole-list replace with no trash for contacts. 8 9 8 9
The Integrator
Import is documented in real depth — xlsx, txt and csv up to 100 MB, automatic and manual column mapping, replace-or-append with an explicit warning that replace permanently deletes, and post-import analysis with reasons for exclusions. A Sarbacane export is mentioned only in passing as a file-format example; we found no public information on exporting engagement history or campaign data, on deleting a single subscriber on request, or on any exit tooling. 8 9 8 9
The Skeptic
Import is documented down to the detail that matters: file, paste or manual entry, suggested field mapping, new-column creation, replace-or-supplement where replace permanently deletes with no trash for contacts, and duplicate or unknown-domain analysis with the exclusion cause shown. But we found no public information on export contents — engagement history, unsubscribe state, custom fields — or per-subscriber deletion; only an incidental mention that a Sarbacane export exists, and an API whose list read-and-write scope the captured pages do not spell out. 8 9 10 8
Integrations & API
Show reasoningHide reasoning
How this is scored
The connection surface a newsletter lives on: shop and CRM systems, events in and out, webhooks, and an API somebody can build against without a partner agreement.
0 — A closed stand-alone tool: the vendor offers neither an API nor integrations, and the list is maintained by hand or CSV.
3 — A handful of named integrations or embeddable forms, or a basic API; webhooks and API documentation are basic or not described.
5 — Named integrations for common shop and CRM systems, a documented REST API with keys, and webhooks or connector-platform triggers for subscriber events.
8 — Maintained bidirectional integrations with named systems including at least one major shop platform, event webhooks with retries, documented rate limits, and a sandbox.
10 — The tool is a component rather than a destination: transactional and marketing sending on one API, events flowing both directions, versioned API with a deprecation policy, and integrations the vendor maintains rather than lists.
The CRM Manager
The connector surface is broad and specific — Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets each have their own documentation, plus an API secured with HTTPS and TLS 1.2, full API documentation, a mobile SDK, CRM list synchronisation, and lists auto-populated from business applications. Webhooks, rate limits, retries and a sandbox are not described, and two-way event flow beyond list synchronisation is not shown. 9 10 1 1
The Deliverability Engineer
Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets connectors are documented, with lists that synchronise automatically from business applications, an API secured by HTTPS and TLS 1.2, and a mobile SDK with its own documentation. We found no public information on webhooks with retries, documented rate limits or a sandbox. 9 10 1 1
The Data Protection Officer
Named connectors cover Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, alongside a documented API secured with HTTPS and TLS 1.2 and mobile SDK documentation. We found no public information on event webhooks with retries, documented rate limits, or a sandbox environment. 10 1 1
The Shop Owner
Three major shop platforms are named as connectors — Shopify, Magento (Adobe Commerce) and PrestaShop, the last two framed for automating e-commerce actions — alongside Salesforce, CRM list synchronisation, Google Sheets, WordPress, a documented API over HTTPS and TLS 1.2, and a mobile SDK. We found no public information on webhooks, rate limits, a sandbox or whether the connectors run bidirectionally, which is what I would need to attribute revenue back to my orders. 9 10 1 1
The Integrator
There are named connectors for Shopify, Magento (Adobe Commerce), PrestaShop, Salesforce, noCRM, WordPress and Google Sheets, CRM list synchronisation, synchronized lists auto-populated from business applications, plus an API with published documentation secured over HTTPS and TLS 1.2 and a mobile SDK. To wire this into an existing stack I need exactly what the captured pages do not show: documented rate limits, event webhooks with retries, a sandbox and a deprecation policy — the connectors are presented as help-centre how-to articles rather than documented bidirectional integrations. 9 10 1 1
The Skeptic
Named connectors for Shopify, Magento (Adobe Commerce), Prestashop, Salesforce, WordPress, Google Sheets and noCRM, plus CRM list synchronisation and synchronized lists auto-populated by business applications, cover the shop and CRM surface a newsletter lives on. A documented API secured with HTTPS and TLS 1.2 and a mobile SDK widen this, but we found no public information on webhooks, rate limits, a sandbox, or whether any integration is maintained bidirectionally. 10 1 1 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where subscriber data and behavioural tracking live, who the contracting entity is, and which subprocessors touch the send. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it — which in this category is heavily. Dimensions not proven either way are unknown, not non-European.
0 — Vendor, contracting entity and hosting shown to be outside the EU, and no data processing agreement offered.
3 — A privacy policy and a data processing agreement exist and one European element is proven (an EU contracting entity or representative, or EU hosting as an option); the rest of the chain is not stated.
5 — An EU contracting entity and EU hosting stated, with a data processing agreement; sending, tracking or support providers are not all shown to be European or are named without a stated safeguard.
8 — EU or DACH hosting on named infrastructure, EU contracting entity, the subprocessor list published with locations including the sending infrastructure, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting, sending and every subprocessor in the EU, certification published, and no transfer that needs a Schrems II argument to survive.
The CRM Manager
The vendor publishes a French address, trades as Positive Groupe France, claims full GDPR compliance and states 300+ experts based in France — the French presence is real and stated. But hosting location, the data processing agreement, and the subprocessor chain including the sending infrastructure are not shown on any captured page, and I weigh this dimension too heavily to treat unproven as European. 1 1 1 1
The Deliverability Engineer
The captured pages show a French postal address, an entity named Positive Groupe France and a team described as based in France, with GDPR compliance asserted. Hosting, the data processing agreement and every subprocessor in the sending and tracking chain are not documented on these pages, and for a buyer who weighs this heavily in this category, an unproven chain is what I score. 1 1 1
The Data Protection Officer
The captured pages prove a French seat — an address in Hem, a Positive Groupe France copyright and three hundred plus experts based in France — with a claim of total GDPR compliance. Where subscriber data and behavioural tracking are hosted, who the contracting entity is, and which subprocessors touch the send are unstated on the pages I read, so I cannot close the Schrems II question from public evidence. Marketing statements about a French team are not a data location. 1 1 1 1
The Shop Owner
The vendor's address is in Hem, France, the copyright entity is Positive Groupe France, and a team of 300-plus experts is described as France-based with full GDPR compliance. We found no public information on hosting, data residency, the data processing agreement or the subprocessor chain, and I weigh sovereignty heavily enough that French roots alone do not carry it further. 1 1
The Integrator
A French contracting entity is proven — Sarbacane Software SAS at an address in Hem, France, 300+ experts based in France, and a Positive Groupe France copyright — and the site asserts full GDPR compliance. We found no public information on hosting locations, a data processing agreement or a published subprocessor list including the sending infrastructure, and a rebrand to Positive User is under way, so the chain beyond the contracting entity is unproven. 1 1 1
The Skeptic
What the captured pages prove is a French address, a France-based team of 300-plus experts, a French copyright entity, and a marketing-page claim of total GDPR compliance — a European presence, but presence is not processing. We found no public information on hosting, data residency, a data processing agreement, or where the sending and tracking infrastructure runs, so the chain a buyer must audit is unstated end to end. 1 1 1
Pricing transparency
not rated — the vendor publishes no price
Show reasoningHide reasoning
How this is scored
Whether a sender can compute the real invoice for their list size and send volume — including overage, extra domains and automation limits — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A public "from" price, a free plan or one priced tier; how cost scales with contacts or sends is unclear.
5 — Prices per contact or send tier public for the main plans with the billing period stated and the main limits given; some add-ons (dedicated IP, extra domains, overage) may be unpriced.
8 — Every tier priced publicly with contact and volume limits, overage rates, feature boundaries and VAT treatment stated; only genuinely custom volume lacks a number.
10 — Complete price computability: a calculator producing the annual invoice for a given list size and send frequency, including overage, additional domains and dedicated IPs.
The CRM Manager
A pricing page exists but no prices are stated on it; the only cost-related facts are a free trial and a promise that existing customers keep identical pricing. From these pages a buyer cannot compute any invoice for their list size or send volume — pricing is effectively a conversation. 1 1
The Deliverability Engineer
The captured pricing page states no prices at all, and the only pricing-related facts are a free-trial button and an assurance that existing customers keep identical tariffs. No sender could compute an invoice for a given list size and send volume from these pages. 1 1
The Data Protection Officer
The captured pricing page states no prices at all; a free trial is offered and existing customers keep identical pricing after the rebrand. We found no public information on how cost scales with contacts or sends, so a buyer cannot compute any invoice from the public pages. 1 1
The Shop Owner
A pricing page exists but states no prices; the only pricing facts on record are a free trial, a licence model under which Sarbacane Contacts and Studio are included with a Campaigns licence, and existing customers keeping their pricing after the rebrand. We found no public information on per-contact or per-send figures, tier limits or overage, so I cannot compute the invoice for my list from public pages alone. 1 1 8
The Integrator
A pricing page exists but no prices are stated on it; the public path is a free trial and talking to an expert, and licensing is described only structurally — a Campaigns licence that includes Contacts and Studio. A buyer cannot compute any invoice for a given list size and send volume from the captured pages; the only pricing statement is that existing customers keep identical pricing. 1 1 8
The Skeptic
The captured pricing page states no prices at all; the only pricing-adjacent facts are a free trial, a talk-to-an-expert call to action, and a promise that existing customers keep identical data, settings and pricing. A buyer cannot compute a single invoice line from what was captured. 1 1
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 | — | uncited Report an error |
|---|---|---|---|
| Hosting location | Not determined | — | uncited Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement | Not determined | — | uncited Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Sarbacane
Is Sarbacane European?
Not determined: the vendor’s pages as captured do not say where Sarbacane is based.
Where does Sarbacane store data?
Not stated on the vendor’s pages as of 16 Nov 2026.
Does Sarbacane have a free plan?
Not stated on the vendor’s pages as of 16 Nov 2026.
What are the best alternatives to Sarbacane?
As of 18 Nov 2026, the panel rates Brevo (3/5), Dotdigital (3/5) and Mailjet (3/5) highest among the other 35 Email Marketing & Newsletter 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 Brevo (EU-Made, France). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Sarbacane alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- 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.
- 46 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
- 5 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 hosting facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 4 support 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 data 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 integrations 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. Know more? Tell us
Sources (10)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.sarbacane.com Checked 16 Nov 2026 +4 earlier captures: 9 Nov 2026, 2 Nov 2026, 26 Oct 2026, 22 Sep 2026 Details →
- 2 Campaigns & automation — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 4 Deliverability infrastructure — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Deliverability infrastructure — found from sitemap help.sarbacane.com Checked 16 Nov 2026 Details →
- 6 Consent, proof & tracking limits — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 9 Nov 2026 Details →
- 8 List ownership, import & exit — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 9 List ownership, import & exit — found from sitemap help.sarbacane.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 10 Integrations & API — found from sitemap help.sarbacane.com Checked 16 Nov 2026 Details →