Benchmark Email
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 1 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Benchmark Internet Group · www.benchmarkemail.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.
Benchmark Email at a glance
- Vendor
- Benchmark Internet Group
- Headquarters
- Not stated on the vendor’s pages as of 10 Nov 2026
- Data hosting
- Not stated on the vendor’s pages as of 10 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 10 Nov 2026
- Panel verdict
- The AI panel rates Benchmark Email 2.5/5, the mean of 6 judges. Benchmark Email scores strongest on deliverability, which holds at 6 with no spread, and integrations clustering at 5–6, and weakest on sovereignty at 1–2. how scores are made
- As of
- Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Benchmark Email scores strongest on deliverability, which holds at 6 with no spread, and integrations clustering at 5–6, and weakest on sovereignty at 1–2. Deliverability credit rests on documented SPF and DKIM via two CNAME records, a required DMARC record, rewriting of unauthenticated from-addresses, and a dedicated IP at $28.95/month with a stated warm-up of 20,000 emails per batch for the first five campaigns. The API sits on every plan with an OpenAPI specification, scoped keys and event webhooks, though scheduling and sending happen in the web app and shop and CRM connections run through Zapier. The judges split on campaign and automation at 4–6, on consent and proof at 3–4 and on pricing transparency at 4–6: they found no public information on A/B testing, send-time optimisation, a per-subscriber consent record or a way to switch open and click tracking off, nor on how the $10 Pro price scales with list size. Sovereignty sits low because the captured pages leave residency, hosting and contracting-entity jurisdiction unstated, and the Data Processing Addendum's terms are not visible in the capture.
Speaks for it
- SPF and DKIM set up through two Benchmark CNAME records with a required DMARC record are documented, with unauthenticated from-addresses rewritten onto an authenticated domain.
- A dedicated IP is priced at $28.95/month with a documented warm-up capping the first five campaigns at 20,000 emails per batch.
- The API is included on every plan at no extra cost, with a published OpenAPI specification, scoped keys with per-resource permissions and hourly and monthly rate limits.
- Contacts and segments export to CSV or Excel with field selection and filtering, and the API can create, rename, duplicate, merge and delete lists.
- The Free Forever plan is fully specified at $0 with 500 contacts, 1,000 sends and one verified sending domain, with no credit card required at signup.
Held against it
- The captured pages give different trademark holders — Benchmark Internet Group, LLC and Polaris Software, LLC — with no jurisdiction stated for either, no data residency or hosting location shown, and a Data Processing Addendum whose terms are not visible in the capture.
- We found no public information on a per-subscriber consent record with timestamp and source, a preference centre, one-click unsubscribe, or a way to switch open and click tracking off.
- Campaigns can be created through the API but scheduling and sending happen only in the web app, and shop and CRM links run through Zapier.
- How the Pro price scales with contact count is not shown on the captured pages, and we found no public information on overage rates or VAT treatment.
- Opened email addresses can be exported only one campaign at a time, and we found no public information on documented deletion of a subscriber across all records.
Best for
- You send at volume and need documented SPF, DKIM and DMARC set-up plus a priced dedicated IP with a stated warm-up pace.
- You build your own tooling and want an API on every plan with an OpenAPI specification, scoped keys, rate limits and subscriber-event webhooks.
- You run a small shop's lifecycle: welcome, follow-up, abandoned-cart and purchase-confirmation automations are documented.
- You want a fully specified free start — $0 with 500 contacts, 1,000 sends and one verified sending domain, no credit card required at signup.
Avoid if
- Your compliance review requires a stated data residency or jurisdiction for the sending and tracking chain — the bench scored sovereignty at 1–2 and the Data Processing Addendum's terms are not visible in the capture.
- You must evidence consent per subscriber with timestamp and source, or switch open and click tracking off — consent and proof scored 3–4.
- Your workflow depends on scheduling or sending mail through the API rather than the web app, or on a maintained native shop connector rather than Zapier.
- You need to compute the invoice for a large list before committing — ask the vendor: the public pages we read do not show it
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 2.5 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 2 of 5 |
| List ownership, import & exit | 2.5 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 0.5 of 5 |
| Pricing transparency | 2 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
A drag-and-drop editor with ready-made templates, segments built on contact-list fields that enter in real time, and automation series triggered by website and email engagement give me a real programme rather than a broadcast pipe. Automation Pro branches on 'Contact Joins a Segment' as a trigger and 'Is in a Segment' as a condition, which is genuine branching on behaviour rather than a flat drip. I found no public information on A/B testing of campaigns, dynamic content per segment, or holdout groups, so I cannot take the lifecycle story above the middle of this scale. 1 3 4
The Deliverability Engineer
A drag-and-drop builder with templates, real-time segmentation on contact fields, and automated series triggered by website and email engagement are all documented — welcome, follow-up and abandoned-cart series included, with segments usable as triggers and conditions in the automation tooling. Split testing of campaigns is only gestured at in reporting copy, and send-time optimisation or journey branching is not described, so it sits above a basic broadcaster without reaching a full journey builder. 1 3 4
The Data Protection Officer
The drag-and-drop editor with templates and AI copy help, segmentation across 26 contact fields with real-time segment entry, and automation from welcome and follow-up series through abandoned cart to a purchase-confirmation journey, with segment triggers and conditions in Automation Pro, are all documented. We found no public information on A/B testing of campaigns, dynamic content per segment or send-time optimisation, so this sits above the mid anchor on journey strength but below the top. 1 3 4
The Shop Owner
The drag-and-drop builder with templates, brand kit and merge-field personalisation is documented, and the named automations are exactly what my shop runs — welcome series, follow-up series, abandoned cart, and a purchase confirmation that moves subscribers from a leads list to a customers list. Segments act as triggers and conditions in Automation Pro and contacts enter them in real time. We found no public information on A/B testing, send-time optimisation or branching on shop events, so this sits just below the level where testing is documented. 1 3 4
The Integrator
A drag-and-drop builder with templates, segments that fill in real time on field conditions with exclude options, and automated series triggered by website and email engagement — welcome, follow-up, abandoned cart and purchase confirmation — are all documented. We found no public information on A/B testing, a visual journey builder, send-time optimisation or significance reporting, so I score the solidly evidenced middle. 1 3 4
The Skeptic
A drag-and-drop builder with templates, segmentation on contact-list fields with real-time entry and exclusion, and automated series triggered by website and email engagement are all documented, including Automation Pro triggers and conditions and abandoned-cart templates. We found no public information on A/B testing of campaigns, send-time optimisation or dynamic content per segment, so this sits below the journey-builder level. 1 3 4
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
Domain authentication is well documented — two CNAME records for SPF and DKIM, a required DMARC record, per-domain statuses, and an unauthenticated 'from' address rewritten to an authenticated Benchmark domain — alongside help-centre guidance on confirmed opt-in and list hygiene. There is a priced dedicated IP at $28.95/month with a documented warm-up capping the first five campaigns at 20,000 emails per batch, plus a shared-IP quality protocol grouping clients by public reputation. I found no public information on inbox-placement testing, engagement-based sunsetting, complaint feedback loops, or reputation reporting per sending domain, which is what a fully operated deliverability service would demand. 5 6 7 12
The Deliverability Engineer
The authentication stack is written down and enforced: SPF and DKIM via two CNAME records, a required DMARC record, and unauthenticated senders have their from-address rewritten onto an authenticated sending domain — that last point is real discipline. A dedicated IP is priced at $28.95/month with a stated warm-up cap of 20,000 emails per batch for the first five campaigns, and shared-IP clients are grouped by public reputation; I found no public information on automatic bounce and complaint suppression, complaint feedback loops, or inbox-placement testing. 5 6
The Data Protection Officer
Authentication is well documented: two CNAME records with a DMARC requirement, the Gmail and Yahoo sender rules, from-address rewriting for unauthenticated domains, plus a dedicated IP at $28.95/month with a stated warm-up (first five campaigns capped at 20,000 emails per batch) and a shared-IP protocol grouping clients by public reputation. We found no public information on automatic hard-bounce and complaint suppression, feedback loops, inbox-placement testing or per-domain reputation reporting, which caps this below the upper anchors. 5 6
The Shop Owner
Domain authentication is documented step by step — two Benchmark CNAME records covering SPF and DKIM plus a required DMARC record, a subdomain recommendation, and rewriting of the from-address if authentication fails — and a dedicated IP at $28.95/month carries a documented warm-up capped at 20,000 emails per batch for the first five campaigns, with shared-IP clients grouped by reputation. We found no public information on automatic bounce and complaint suppression, feedback loops, or inbox-placement testing. 5 6
The Integrator
Authentication is documented end to end — two CNAME records for SPF and DKIM plus a DMARC record, subdomain advice, a stated rewrite of the from-address for unauthenticated senders — and the dedicated IP at $28.95/month carries a real warm-up document of at most 20,000 emails per batch for the first five campaigns. We found no public information on automatic bounce and complaint suppression, feedback loops, or inbox-placement testing, which is what would move this higher. 5 6
The Skeptic
SPF, DKIM and DMARC set-up through CNAME records with visible domain statuses, a subdomain recommendation, and a rewritten sender address when a domain cannot be authenticated are documented, alongside a dedicated IP at $28.95/month with a stated warm-up pace of 20,000 emails per batch for the first five campaigns. We found no public information on inbox-placement testing, complaint feedback loops or per-domain reputation reporting, which keeps this below the upper anchors. 5 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
Sign-up forms, a documented double opt-in where the subscriber must click a confirmation link to become active, and an unsubscribe merge tag are all evidenced, and webhooks fire on subscribes, unsubscribes and cleaned addresses. I found no public information on a per-subscriber consent record with timestamp and source, one-click unsubscribe, a preference centre, or any way to switch open and click tracking off — open tracking is documented, since openers are exportable per campaign, but its limits are not. The burden of proof sits with me as the sender, and the captured pages do not yet evidence it. 1 7 8 10 12
The Deliverability Engineer
Double opt-in is documented down to the mechanism — Benchmark sends the confirmation mail and the subscriber must click through to activate — and sign-up forms, opt-in and unsubscribe merge tags are all described. What I cannot see is the proof: no consent record with timestamp and source, no one-click unsubscribe, and nothing showing open or click tracking can be switched off. 7 8 1
The Data Protection Officer
Double opt-in is documented as a confirmation mail the subscriber must click to become active, with branded sign-up forms and unsubscribe and opt-in merge tags, and the vendor itself argues confirmed opt-in protects deliverability. What I need and do not find is the proof: no public information on a per-subscriber consent record with timestamp, source and IP, on preference handling across lists, or on any way to switch open and click tracking off. 1 7 8
The Shop Owner
Confirmed opt-in is documented in detail — Benchmark sends a confirmation email the subscriber must click to become active — and opt-in and opt-out merge tags can be placed in button text or body text, with drag-and-drop sign-up forms also shown. We found no public information on a stored per-subscriber consent record with source and timestamp, one-click unsubscribe, a preference centre, or any way to switch open and click tracking off. 1 7 8
The Integrator
Double opt-in is properly documented — Benchmark sends the confirmation mail and the subscriber must click a link to activate — and campaigns carry an unsubscribe merge tag, with a separate opt-in merge tag for building reconfirmation lists. We found no public information on a stored consent record with timestamp and source, one-click unsubscribe handling, or any way to switch open and click tracking off. 7 8 1
The Skeptic
Sign-up forms, a documented double opt-in with a confirmation mail and click-to-activate link, and unsubscribe plus opt-in merge tags are shown. We found no public information on a per-subscriber consent record, a preference centre, or any way to switch open and click tracking off. 1 7 8
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
Contacts import quickly, export to CSV or Excel with a choice of fields and filters, and the API can create, rename, duplicate, merge and delete lists and search contacts by email, custom field, list, status or creation date — the list is genuinely mine to read and write. Engagement history export exists but the vendor states opened email addresses can only be exported one campaign at a time, and I found no public information on exporting campaigns and templates, on documented deletion of a subscriber across all records, or on export throttling. That is a solid middle score, not an exit I could run as a documented feature. 1 4 9 10 11
The Deliverability Engineer
CSV and Excel export with selectable fields, segment export, and an API that reads and writes contacts and lists make the list demonstrably portable. Engagement export exists but only one campaign's openers at a time, and I found no public information on documented deletion of an individual subscriber across all records. 9 10 11
The Data Protection Officer
Contact import, export to CSV or Excel with field selection and filters, segment export that keeps the original contacts, and an API on every plan that reads and writes contacts and lists put exit and portability on solid ground. Engagement history export exists but only for one campaign at a time, and we found no public information on documented deletion of a subscriber across all records. 1 9 10 11
The Shop Owner
Contacts export with field selection and filtering to CSV or Excel, segment exports work the same way, opens can be exported per campaign though only one campaign at a time, and the API reads and writes contacts and lists on every plan. Deleting a segment leaves the original list's contacts intact, which is the right default. We found no public information on documented per-subscriber deletion, a full engagement-history export, or export throttling. 4 9 10 11
The Integrator
Contacts export with selectable fields and filters in CSV or Excel, segments export the same way, and the API reads and writes contacts and lists — though the opens export runs one campaign at a time. We found no public information on documented deletion of a subscriber across all records, or on exporting campaigns and templates. 9 10 4 11
The Skeptic
CSV and Excel export with field selection and filtering, segment export, and a list-management API that can create, rename, duplicate, merge and delete lists are documented, with openers exportable per campaign but only one campaign at a time. We found no public information on field-mapped import, deletion of a single subscriber across records, or export of full engagement history in one go. 1 4 9 10 11
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 API is real and well governed: JSON over HTTP with a published OpenAPI specification, scoped keys with per-resource permissions, documented hourly and monthly rate limits surfaced in response headers, and scenario guides, included on every plan at no extra cost. Webhooks post subscribes, unsubscribes, profile updates, cleaned addresses and email changes, and Zapier connects to CRM, store and booking tools without code. Scheduling and sending happen in the Benchmark Email web app rather than through the API, and I found no public information on named maintained shop integrations, webhook retries, or a sandbox, so this lands just above the middle. 1 11 12
The Deliverability Engineer
A documented API with a published OpenAPI specification, scoped keys, per-resource permissions and stated hourly and monthly rate limits, plus subscriber-event webhooks — somebody can build against this without a partner agreement, and the API is included on every plan. Scheduling and sending happen in the web app rather than through the API, webhook retries and a sandbox are not described, and shop connectivity runs through Zapier rather than maintained native integrations. 11 12 1
The Data Protection Officer
A JSON-over-HTTP API with a published OpenAPI specification, scoped keys with per-resource permissions, hourly and monthly rate limits in response headers, plus subscriber-event webhooks and a Zapier connector to CRM, store and booking tools, all included on every plan. Scheduling and sending happen in the web app rather than the API, and we found no public information on a sandbox or webhook retries. 1 11 12
The Shop Owner
The API is well documented — JSON over HTTP with a published OpenAPI specification, scoped keys with per-resource permissions, and hourly and monthly quotas surfaced in response headers — and webhooks post subscriber events in real time, with a Zapier bridge for CRM, store and booking tools. But scheduling and sending happen only in the web app, not through the API, and we found no public information on a named vendor-maintained shop integration, webhook retries or a sandbox — for my shop, orders and carts arriving only through Zapier is a weaker pipe than a maintained connector. 1 11 12
The Integrator
The API is the best-documented surface here: an OpenAPI specification at developers.benchmarkemail.io, scoped keys with per-resource permissions, key expiry and reactivation, and rate limits with hourly and monthly quotas plus response headers, included on every plan. It stops short of what I need: scheduling and sending happen only in the web app so the API cannot send mail, the webhooks post subscribe and unsubscribe events but no retry behaviour is documented, and I found no public information on a sandbox or a deprecation policy — while the CRM and store connections run through Zapier, which I read as an outsourced connection surface. 11 12 1
The Skeptic
A documented API included on every plan with an OpenAPI specification, scoped keys with per-resource permissions and stated rate limits, plus webhooks for subscribe, unsubscribe, profile-update and cleaned-address events, form a real connection surface. Campaigns can be created through the API but scheduling and sending happen in the web app, shop and CRM links come through Zapier generically, and we found no public information on webhook retries or a sandbox. 1 11 12
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
A data processing addendum is offered and reachable, which is more than nothing, but I found no public information on the contracting entity's jurisdiction, data residency, hosting options, or any subprocessor locations. The captured pages name limited-liability companies as the trademark holder without stating a jurisdiction — one page names Benchmark Internet Group, LLC, another Polaris Software, LLC. As a buyer who weighs where subscriber data lives heavily, nothing here lets me place a single element of the chain in Europe. 2 6 12
The Deliverability Engineer
A Data Processing Addendum is published, but no European element is proven on the captured pages: legal-entity jurisdiction, data residency and hosting options are all unstated, and the contracting names shown — Benchmark Internet Group, LLC and Polaris Software, LLC — carry no stated jurisdiction. For a buyer who weighs this heavily, nothing here lets you place the sending or tracking chain on a map. 1 2 6 12
The Data Protection Officer
A data processing addendum page exists, but the captured pages give different LLCs as the trademark holder and state no jurisdiction, no hosting location, no data residency and no subprocessor list with locations, so where the opens and clicks on named people actually live cannot be answered without a transfer argument I would rather not make. No European element is proven anywhere on the captured pages. 2 6 9
The Shop Owner
A data processing addendum page exists, and the trademark holders named on the captured pages are US-style LLCs, but the jurisdiction itself is not stated in what we captured. We found no public information on hosting location, data residency, subprocessors or any European entity or representative, and as a buyer who weighs this heavily I can credit little beyond the addendum's existence. 2 6 9
The Integrator
I can confirm a data processing addendum page exists, but the capture shows only its heading, and the captured pages name different trademark-holding entities — Polaris Software, LLC and Benchmark Internet Group, LLC — with no jurisdiction stated for either. We found no public information on data residency, hosting options or subprocessors, and the pages prove no European element; as this buyer weighs the category heavily, an addendum heading alone sits near the bottom. 2 6 12
The Skeptic
We found no public information on data residency, hosting location or the jurisdiction of the contracting entity; the captured pages name Benchmark Internet Group, LLC and Polaris Software, LLC, and a Data Processing Addendum page exists whose terms are not visible in the capture. No European element — an EU entity, representative or EU hosting — is stated on any page we read. 2 6 9 12
Pricing transparency
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
Public prices are concrete where they matter: a Free Forever plan at $0 /mo with 500 contacts, 1,000 email sends and 1 verified sending domain, a Pro plan from $10, and an Enterprise tier by quote for 100,000+ contacts with additional users at $15/mo. per user and a stated send limit of 10x your contact limit every month. The dedicated IP is priced at $28.95/month and every plan is stated to include all features with pricing scaling on list size, but I found no public information on how the Pro price scales across contact tiers, on overage rates, or on VAT treatment. 1 3 6
The Deliverability Engineer
Free and Pro plans are public with contact and send limits — up to 10x the contact limit per month — a dedicated IP is priced at $28.95/month, extra users at $15/mo., and the vendor states there is no feature gating between plans. How the Pro price scales across contact counts, VAT treatment and what happens beyond the send limit are not stated, and the Enterprise tier is quote-only. 1 6
The Data Protection Officer
The free plan is fully specified at $0 with 500 contacts and 1,000 sends, a Pro figure of $10 appears in the pricing page data, and add-ons carry numbers: a dedicated IP at $28.95/month and extra users at $15/mo, with sends allowed up to 10x the contact limit. How the Pro price scales with contact count is not captured, Enterprise is quote-only, and we found no public information on overage rates or VAT treatment. 1 3 6
The Shop Owner
The free plan's limits are exact — 500 contacts, 1,000 email sends, one user, one verified sending domain — the Pro plan shows $10, the Enterprise tier is quote-only with add-on users at $15/mo., a dedicated IP is $28.95/month, and the pages state pricing scales with list size rather than features. We found no public information on the per-contact price ladder for paid tiers, overage rates or VAT treatment, so I cannot compute the annual invoice for my list from the captured pages alone. 1 6
The Integrator
The free tier is concrete — $0 /mo with 500 contacts, 1,000 sends and one verified sending domain — the Pro plan starts at $10, Enterprise is a quote with 100,000+ contacts and users at $15/mo. per user, and even the dedicated IP carries a public $28.95/month. What I cannot compute from these pages is how the Pro price scales with list size, or VAT treatment and overage, so the real invoice for a large list stays unclear. 1 3 6
The Skeptic
The free plan is fully specified at $0 with 500 contacts and 1,000 sends, the Pro plan is shown at $10 with send allowance stated as 10x the contact limit, and add-ons carry numbers — dedicated IP at $28.95/month, extra users at $15/mo. How the Pro price scales with list size is not shown in the captured pages, and we found no public information on overage rates or VAT treatment. 1 3 6
European sovereignty — proven facts
1 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 |
Published, self-serve
unverified
Why unverified?The excerpt shows only the page's heading and footer link; the agreement's terms themselves are not visible in it. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Benchmark Email
Is Benchmark Email European?
Not determined: the vendor’s pages as captured do not say where Benchmark Email is based.
Where does Benchmark Email store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does Benchmark Email have a free plan?
Yes. Benchmark Email has a free plan, per the vendor’s page captured 10 Nov 2026.
What are the best alternatives to Benchmark Email?
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: Benchmark Email alternatives.
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 10 Nov 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Data processing agreement. The excerpt shows only the page's heading and footer link; the agreement's terms themselves are not visible in it.
- 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.
- 3 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 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
Sources (12)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.benchmarkemail.com Checked 10 Nov 2026 Details →
- 2 Data processing agreement (dpa) — found from the homepage www.benchmarkemail.com Checked 10 Nov 2026 Details →
- 3 Campaigns & automation — found from sitemap www.benchmarkemail.com Checked 10 Nov 2026 Details →
- 4 Campaigns & automation — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 5 Deliverability infrastructure — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 6 Deliverability infrastructure — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 7 Consent, proof & tracking limits — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 9 List ownership, import & exit — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 10 List ownership, import & exit — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →
- 11 Integrations & API — found from sitemap www.benchmarkemail.com Checked 10 Nov 2026 Details →
- 12 Integrations & API — found from sitemap kb.benchmarkemail.com Checked 10 Nov 2026 Details →