beehiiv
Provenance unknown Report an errorPanel rating · 6 judges · How to read the stars
Category median
Sovereignty: 2 of 6 dimensions proven
0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by beehiiv, Inc. · www.beehiiv.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.
beehiiv at a glance
- Vendor
- beehiiv, Inc.
- Headquarters
- Incorporated in the United States source, captured 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 beehiiv 2/5, the mean of 6 judges. Judged from the captured pages, beehiiv scores highest on list data control, integrations and campaign and automation, all clustering at 6-7, and lowest on sovereignty, clustering at 2-3. 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
Judged from the captured pages, beehiiv scores highest on list data control, integrations and campaign and automation, all clustering at 6-7, and lowest on sovereignty, clustering at 2-3. The highs rest on documented CSV export of subscribers in Quick and Full variants and of all posts including drafts, permanent irreversible deletion, a public API spanning 38 endpoint groups with webhooks, and a drag-and-drop automation builder with triggers, actions and conditional logic. Sovereignty sits low because the contracting entity is beehiiv Inc. of New York, transfers rely on Standard Contractual Clauses, we found no public information on hosting or data residency, and the privacy policy states identifiers, network activity and commercial information were "sold" or "shared" with advertising partners and analytics providers. Judges split on deliverability, 5 to 6, over how heavily to weigh the pages' silence on bounce suppression, dedicated IP options and warm-up; they split on pricing transparency, 3 to 4, where every paid figure is a "Starting at" price and the captured pages give different figures for the Lite and Pro tiers.
Speaks for it
- Subscriber data exports in Quick and Full CSV variants, with the Full variant including custom fields and statistics, and all posts including drafts export as CSV
- Full deletion permanently erases all records associated with the email and cannot be undone
- The public API spans 38 endpoint groups with bearer authentication, OAuth scopes and create-to-delete webhook management
- Double opt-in is available on all plans and excludes pending subscribers from every send, including API-added and referral sign-ups
- Custom-domain SPF, DKIM and DMARC set-up is documented through CNAME records with a DMARC wizard and a free report analyser
Held against it
- The contracting entity is beehiiv Inc. of New York, transfers rely on Standard Contractual Clauses, and beyond an Article 27 representative in Vienna we found no public information on hosting or data residency
- The privacy policy states identifiers, network activity and commercial information were 'sold' or 'shared' with advertising partners and analytics providers
- We found no public information on a per-subscriber consent record with timestamp and source, or on switching open and click tracking off
- Paid tiers are published only as 'Starting at $49' and 'Starting at $95', and the same pricing page's structured data gives $59 for Lite and $109 for Pro
- We found no public information on A/B testing, send-time optimisation, dedicated IP options, warm-up or an integration with a major shop platform
Best for
- You want exit rights documented before you commit — subscriber and post-content CSV export plus permanent, irreversible deletion
- Your team builds its own integrations and prefers a documented 38-endpoint-group API with webhooks and OAuth scopes over maintained connectors
- You want double opt-in enforced on every signup path, including API additions and referrals
- You want to start free at $0 with no credit card required and move to Pro for dynamic content, click-triggered automations and the Send API
Avoid if
- You weigh a US contracting entity, SCC-based transfers and the privacy policy's 'sold' or 'shared' disclosure with advertising partners and analytics providers as disqualifying for a European list
- You need to compute your invoice from public pages — every paid figure is a 'Starting at' price and above 250,000 subscribers pricing becomes a sales contact
- You run a shop and expect out-of-the-box cart- or order-triggered flows — the named integrations are Zapier, Make, Webflow, Stripe and Google Analytics, and we found no public information on triggers from shop order and cart data
- You must document consent per subscriber with timestamp and source, or switch open and click tracking off — the only opt-out granularity shown is a global unsubscribe by email
The scores
| Criterion | Panel median |
|---|---|
| Campaigns & automation | 3 of 5 |
| Deliverability infrastructure | 3 of 5 |
| Consent, proof & tracking limits | 2 of 5 |
| List ownership, import & exit | 3 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 1.5 of 5 |
| Pricing transparency | 2 of 5 |
Campaigns & automation
panel disagrees
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 builder with triggers, actions and conditional logic, automations on user behaviour, custom events and time delays, and dynamic content plus click-triggered automations on the top tier give me journeys that genuinely branch. Segments and custom fields exist as API endpoint groups, so behavioural splits are plausible. I found no public information on A/B testing, send-time optimisation or holdout groups — a builder with no measurement story stops short of the top end. 1 4 12
The Deliverability Engineer
A drag-and-drop newsletter builder with reusable blocks and post templates, segments and condition sets exposed in the API, dynamic content on the paid tier, and automations built on triggers, actions and conditional logic including user behaviour, custom events, click-triggered and RSS sends. We found no public information on A/B testing, send-time optimisation or holdout groups, which keeps this short of the top band. 1 4 12
The Data Protection Officer
The drag-and-drop automation builder with conditional logic, triggers on behaviour, custom events and time delays, plus a segments surface and reusable templates, goes well beyond simple broadcasts; dynamic content and click-triggered automations sit on the top plan. We found no public information on A/B testing of campaigns or send-time optimisation. 1 4 12
The Shop Owner
The captured feature pages document a drag-and-drop builder with triggers, actions and conditional logic, dynamic sequences driven by user behaviour, custom events and time delays, with segments, condition sets, reusable blocks and post templates throughout the API surface; the Pro tier adds dynamic content and click-triggered automations. We found no public information on A/B testing, send-time optimisation, or triggers from shop order and cart data — as a shop, that last gap means no abandoned-cart or post-purchase flows without a custom build. 1 4 12 8
The Integrator
The automations pages document a drag-and-drop builder with triggers, actions and conditional logic, sequences driven by user behaviour, custom events and time delays, with dynamic content and click-triggered automations on the top plan, and the API surface lists segments, condition sets and automation journeys on top. We found no public information on A/B testing or send-time optimisation, so the journey tooling clears the basics without approaching the top anchors. 1 4 12
The Skeptic
A drag-and-drop newsletter builder sits next to an automation builder with triggers, actions and conditional logic, dynamic content and click-triggered automations appear on the top tier, and segments exist in the API surface. We found no public information on A/B testing, send-time optimisation or how segments are actually defined, so this reads as a solid sequence builder rather than a full lifecycle journey tool. 1 4 8 12
Deliverability infrastructure
panel disagrees
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
Authentication is documented properly — SPF and DKIM via CNAME records, a DMARC wizard with none/quarantine/reject options, automatic handling on beehiiv subdomains, and sender/reply-to alignment rules — and the help centre defines acceptable and problematic complaint rates at 0.10% and 0.30%, explains feedback-loop coverage of roughly 30% of traffic, and surfaces spam reports in the dashboard. I found no public information on hard-bounce suppression, dedicated IPs, warm-up or per-domain reputation reporting, so the documented setup and education stop short of deliverability operated as a service. 6 7
The Deliverability Engineer
The authentication stack is documented end to end — SPF and DKIM via CNAME records the sender adds, DMARC with a wizard, a free report analyser and policy options, all managed automatically on beehiiv-provided subdomains — and the complaint side is unusually honest: the vendor states its own FBL coverage ceiling of roughly 30% of a typical list, surfaces spam reports in the dashboard with acceptable and problematic rates, and names M3AAWG membership. We found no public information on hard-bounce suppression, dedicated IP options, warm-up or engagement-based sunsetting, which caps this well below the top band. 6 7 3
The Data Protection Officer
Custom-domain authentication is documented in depth — CNAME-based SPF and DKIM, a DMARC record wizard, automatic DMARC on beehiiv subdomains — and the help centre explains feedback loops, acceptable complaint rates and enforcement for abuse. We found no public information on automatic bounce suppression, dedicated IP options or warm-up. 1 6 7
The Shop Owner
Help-centre articles document SPF and DKIM set-up through CNAME records, automatic SPF, DKIM and DMARC on beehiiv-provided subdomains, a DMARC wizard with a free report analyzer, and complaint feedback loops at 30+ mailbox providers with complaint tallies surfaced in the post dashboard, alongside list-hygiene guidance and a purchased-list prohibition. We found no public information on bounce handling and suppression, dedicated-IP options, warm-up or inbox-placement testing. 6 7 3
The Integrator
SPF, DKIM and DMARC for a custom domain are documented down to three CNAME records and a record wizard, with automatic management on vendor-provided subdomains, and the help centre goes unusually deep on feedback loops, complaint-rate thresholds, list hygiene and enforcement, with spam reports surfaced in the dashboard. We found no public information on dedicated IP options, warm-up, seed or inbox-placement testing, or automatic bounce suppression. 1 6 7
The Skeptic
SPF, DKIM and DMARC are documented for authenticated custom domains on paid plans with automatic handling on vendor subdomains, a DMARC wizard and a free report analyser; complaints are worked seriously, with feedback loops stated for roughly 30% of traffic, visible spam-report tallies, published acceptable-versus-problematic complaint rates and enforcement up to deactivation. We found no public information on dedicated IP options, warm-up, seed or inbox-placement testing, or automatic hard-bounce suppression. 1 3 6 7
Consent, proof & tracking limits
panel disagrees
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
Double opt-in is documented in unusual depth: pending subscribers receive nothing at all, including automations and welcome mail, referrals go through the same confirmation, and there is deliberately no programmatic way to flip a pending subscriber to active. The GDPR page adds permanent, irreversible deletion and a subscription-management listing, and a global unsubscribe request exists. I found no public information on a per-subscriber consent record with timestamp and source, one-click unsubscribe handling, or any way to switch open and click tracking off — which is precisely the proof and the tracking limits I need. 8 9 2
The Deliverability Engineer
Double opt-in is documented with real mechanical depth: Pending subscribers are excluded from every send including automation sequences, referrals and API additions follow the same confirmation flow, and there is no programmatic path to Active — the subscriber's click is the only key, with a 48-hour nudge on top. We found no public information on a per-subscriber consent record with timestamp and source, one-click unsubscribe mechanics, or any way to switch off open and click tracking; a global opt-out address and a GDPR rights page do exist. 8 2 9
The Data Protection Officer
Double opt-in is documented thoroughly — pending status, a mandatory confirmation button, referrals included, API sign-ups following the same confirmation flow — but it is an optional setting, and we found no public information on a per-subscriber consent record with timestamp and source. Open and click tracking is presented as a standard analytics feature; we found no public information on switching tracking off, and the only opt-out granularity documented is an all-or-nothing global unsubscribe by email. 2 8 9
The Shop Owner
Double opt-in is documented on all plans and gated tightly: pending subscribers receive nothing, referrals and API-added subscribers follow the same confirmation flow, and there is no programmatic way to move a subscriber to active; a global opt-out by email plus GDPR-page permanent deletion and a subscription-listing redaction form also exist. We found no public information on a stored consent record with timestamp and source, one-click unsubscribe, or any way to switch open and click tracking off. 8 2 9
The Integrator
Double opt-in is documented on every plan in real detail — pending status blocks every send including automations, the confirmation mail is customisable, and API-added subscribers follow the same confirmation flow — and the privacy pages show permanent deletion plus a redaction form listing current subscriptions. We found no public information on a stored consent record per subscriber with timestamp and source, a preference centre, or any way to switch open and click tracking off. 2 8 9
The Skeptic
Double opt-in is documented in real depth — pending status gates every send including automation sequences, the confirmation button cannot be removed, even API-added and referral subscribers go through the flow — and a GDPR page covers deletion and a redaction form. But we found no public information on a stored consent record per subscriber with source or IP, on unsubscribe handling across lists or a preference centre, or on switching open and click tracking off. 2 8 9
List ownership, import & exit
panel disagrees
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
Exit is clearly designed for: subscriber export in Quick and Full CSV variants carrying status, tier, custom fields and statistics, all post content exportable including drafts, an asynchronous API-triggered export, and a permanent full-data deletion that cannot be undone. Migration is offered as a feature and the API spans subscriptions, custom fields, segments and bulk updates. I found no public information on exporting templates or campaign analytics history, and the help centre notes the export endpoint is available on paid plans only. 11 9 13
The Deliverability Engineer
Subscriber export comes in a full variant with status, tier, custom fields and statistics, all post content including drafts is exportable, deletion is stated as permanent and irreversible, and the API imports into lists as well as triggering exports. The programmatic export sits behind paid plans and covers subscribers only, and we found no public information on export throttling or a documented full-account export beyond these options. 11 10 9
The Data Protection Officer
Subscriber export offers a Full CSV including custom fields and statistics, post content exports as CSV, deletion is documented as permanent and a migration service exists, with a subscription-export API alongside it on paid plans. We found no public information on per-campaign engagement history in exports, template export, or import with field mapping from other systems. 9 10 11 13
The Shop Owner
Subscriber export runs in Quick or Full CSV variants carrying email, status, tier, custom fields and statistics, all posts including drafts export as CSV, a subscription export endpoint processes asynchronously, and full deletion permanently erases all records tied to the email. Download links expire after 24 hours, the export API sits on paid plans only, and we found no public information on exporting templates. 11 10 9
The Integrator
Exit is genuinely documented: CSV export of all post content including drafts, subscriber exports where the full variant includes custom fields and statistics, an asynchronous export API endpoint, a background list import that deduplicates and filters by tag or custom field, and deletion described as permanent and irreversible. Template export, throttling terms and deletion of a single subscriber across all account records by the account owner are not described, and the export API is stated to be available on paid plans only, which keeps this below the top anchor. 9 10 11
The Skeptic
Quick and Full CSV exports cover subscribers with custom fields and statistics, post content exports include drafts, an API export endpoint exists, deletion is described as permanent across all records, and a migration feature is offered. The export API is on paid plans only, post content exports run through the dashboard rather than the API, and we found no public information on exporting templates or on export throttling. 9 10 11 13
Integrations & API
panel disagrees
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
Thirty-eight API endpoint groups with bearer auth and OAuth scopes, full create-to-delete webhook management, and event webhooks for new subscriptions, cancellations and content publishing, plus named Zapier, Make, Webflow, Stripe and Google Analytics connections and a CRM sync — this is a surface my team could build against without a partner agreement. I found no public information on webhook retries, documented rate-limit figures, a sandbox, or a major shop platform among the named systems, which is what the top end would show. 12 13 4
The Deliverability Engineer
A documented REST API with bearer and OAuth authentication spans 38 endpoint groups including webhooks with full create-to-delete management, event webhooks for new subscriptions, cancellations and content publishing, and named connections through Zapier, Make, Stripe and CRM sync. We found no public information on a major shop-platform integration, webhook retries, published rate-limit numbers beyond a 429 error code, or a sandbox. 12 13 1
The Data Protection Officer
A documented REST API with token authentication spans some thirty-eight endpoint groups with OAuth scopes, and webhooks cover new subscriptions, cancellations and publishing; Zapier, Make, Webflow, Stripe, Google Analytics and generic CRM sync are named. We found no public information on rate-limit values, webhook retries, a sandbox, or an integration with a major shop platform. 1 4 12 13
The Shop Owner
The developer reference lists 38 API groups behind bearer keys and OAuth scopes, full create-list-get-update-delete handling for webhooks, real-time events for new subscriptions, cancellations and publishing, plus a Send API on the Pro tier; Zapier, Make, Webflow, Stripe and Google Analytics are named and CRM sync is claimed. We found no public information on an integration with a major shop platform, webhook retries, a sandbox, or documented rate-limit values — so orders, carts and products would flow only through custom work. 12 13 4 1
The Integrator
The strongest part for my stack: a public developer reference with thirty-eight endpoint groups including OAuth, webhooks, segments, automations and data deletion, bearer authentication, webhook create, list, update and delete with separate read and write scopes, a send API on the top plan, and an asynchronous export endpoint. But rate limits are only implied by a documented 429 error code with no numbers, we found no public information on webhook retries, a sandbox or a deprecation policy, and the shop and CRM connections run through Zapier and Make rather than maintained named integrations. 1 4 8 11 12 13
The Skeptic
A public REST API with bearer tokens and OAuth scopes spans a very broad surface — webhook create to delete, bulk subscriptions, condition sets, exports — alongside webhooks for subscription and publishing events and connector platforms like Zapier and Make. We found no public information on webhook retries, published rate-limit numbers, a sandbox, or a maintained integration with a major shop platform, so this stops short of the top of this scale. 1 4 12 13
European sovereignty
panel opinion
panel disagrees
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 privacy policy and a self-serve data processing agreement exist, an Article 27 GDPR representative is appointed in Vienna, standard contractual clauses handle transfers, and a subprocessor list is published at a public URL. The contracting entity is beehiiv Inc. of New York, data residency and hosting are not stated on the captured pages, and the policy discloses selling or sharing identifiers and browsing activity with advertising and analytics partners. For a European list I weight this heavily, and SCC-based transfers out of a US entity that monetises reader data is a real cost. 2 3
The Deliverability Engineer
The contracting entity is beehiiv Inc. of New York, an Article 27 GDPR representative is appointed in Vienna, SCCs are named for transfers, and a data processing agreement plus a published subprocessor list URL exist — the shape of a bare compliance minimum rather than a European footprint. Data residency and hosting are unknown on the vendor's own pages, and the privacy policy records that identifiers and network activity were sold or shared with advertising and analytics partners; a buyer who weighs this heavily gets very little to hold on to. 2 3
The Data Protection Officer
The contracting entity is beehiiv Inc. of New York, a self-serve data processing agreement is linked and an Article 27 EU representative in Vienna is named — one European element — while data residency and hosting are not stated anywhere I read. Transfers rely on Standard Contractual Clauses, so behavioural data crossing the Atlantic still needs exactly the Schrems II argument I want to avoid, and the privacy policy states identifiers and internet activity were sold or shared with advertising and analytics partners. 2 3
The Shop Owner
The contracting entity is beehiiv Inc. at a New York address, with an Article 27 EU representative in Vienna appointed and a self-serve data processing agreement linked from the privacy page; cross-border transfers rely on Standard Contractual Clauses. The policy also states identifiers, network activity and commercial information were "sold" or "shared" with advertising and analytics partners in the preceding 12 months — for a shop mailing EU customers that is what I weigh heaviest — and we found no public information on hosting or data residency. 2 3 13
The Integrator
The contracting entity is beehiiv Inc. in New York, cross-border transfers run on Standard Contractual Clauses, and the privacy policy states personal information is sold or shared with advertising partners and analytics providers. The proven European elements are an Article 27 representative in Vienna and a self-serve data processing agreement link, plus a published subprocessor list URL — but hosting location, the sending infrastructure and subprocessor locations are not stated on the captured pages, so I weigh this heavily against the vendor. 2 3
The Skeptic
The contracting entity is a New York company, softened only by a Vienna-based Article 27 representative, a self-serve data processing agreement link and SCCs for transfers; hosting and data residency are simply not stated on the captured pages. The privacy policy also states a "sale" or "share" of identifiers and internet activity to advertising and analytics partners, and the vendor runs its own ad network with its own targeting decisions — a US chain with unknown infrastructure and monetised data flows is not a sovereign option. 2 3
Pricing transparency
panel disagrees
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
Three tiers are public with unusually clear feature boundaries and a free plan at $0, but the paid tiers appear only as "Starting at $49" and "Starting at $95", and the captured page gives different figures for Lite and Pro in its structured price data. I found no public information on how price scales with subscriber count between zero and the 250,000-subscriber sales contact, or on overage and VAT treatment. I cannot compute the invoice for a given list size from these pages. 1
The Deliverability Engineer
Three tiers are priced publicly with per-tier feature boundaries, a free plan with no credit card required, and a sales contact above 250,000 subscribers — but every paid figure is a Starting at price, and the captured pages give different figures for the Lite and Pro plans. How the invoice scales with list size between the entry price and the sales threshold, overage rates, VAT treatment and add-on pricing are not documented, so the real invoice is not computable from public pages. 1
The Data Protection Officer
A free plan at $0, Lite "Starting at $49" and Pro "Starting at $95" are published with per-tier feature lists, but the same pricing page's structured data gives $59 for Lite and $109 for Pro, so the captured pages give different figures for the paid tiers. We found no public information on subscriber limits per tier, overage rates or VAT treatment, and above 250,000 subscribers everything becomes a sales contact. 1
The Shop Owner
The pricing page publishes three tiers — "Free Starting at $0", "Lite Starting at $49", "Pro Starting at $95" — with per-plan feature lists and "More than 250,000 subscribers? Contact Sales" as the ceiling, though the same page's structured pricing data gives different figures for the Lite and Pro tiers. We found no public information on how price scales with subscriber count beyond the "Starting at" figures, or on overage rates and VAT treatment. 1 11
The Integrator
Three tiers are public with a free plan and unusually clear feature boundaries between them — webhooks on Lite, send API on Pro — but the prices are 'Starting at $0', 'Starting at $49' and 'Starting at $95' with no contact-tier table, so I cannot compute an invoice for a given list size. The captured pages also give different figures for the Lite plan ('Starting at $49' versus '59') and the Pro plan ('Starting at $95' versus '109'), and we found no public information on VAT treatment; beyond 250,000 subscribers the price becomes a sales conversation. 1
The Skeptic
Three tiers are priced publicly with unusually detailed feature boundaries per tier and a free plan with no credit card, but every paid figure is a "starting at" with no contact-band scale, billing period, VAT treatment or overage shown, and sales contact takes over above 250,000 subscribers. The captured pricing also gives different figures for the Lite plan ("Starting at $49" in page copy against "59" in the structured offer data) and for Pro ("Starting at $95" against "109"), so a buyer cannot compute an invoice from the public pages. 1
European sovereignty — proven facts
2 of 6 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity |
Incorporated in US
unverified
Why unverified?Headquarters statement appears in the privacy policy's international-transfers section rather than a formal imprint; the address block names beehiiv Inc. but gives no state of incorporation or register. |
0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
Not determined
unverified
Why unverified?Not confirmed on the vendor’s own pages as captured. |
— | 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 document's title as a link in the privacy page's Documents menu; the addendum's text and any online acceptance flow are not shown. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about beehiiv
Is beehiiv European?
Not determined: the vendor’s pages as captured do not say where beehiiv is based. Its vendor, beehiiv, Inc., is incorporated in the United States, per the vendor’s page captured 10 Nov 2026.
Where does beehiiv store data?
Not stated on the vendor’s pages as of 10 Nov 2026.
Does beehiiv have a free plan?
Yes. beehiiv has a free plan, per the vendor’s page captured 10 Nov 2026.
What are the best alternatives to beehiiv?
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: beehiiv 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 document's title as a link in the privacy page's Documents menu; the addendum's text and any online acceptance flow are not shown.
- Weak sourcing — Legal entity. Headquarters statement appears in the privacy policy's international-transfers section rather than a formal imprint; the address block names beehiiv Inc. but gives no state of incorporation or register.
- Weak sourcing — Hosting location. 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.
- 24 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
- 21 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
- 7 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
- 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
- 1 data fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 sovereignty dimension could not be confirmed on the vendor’s own pages and is shown as unknown. Know more? Tell us
Sources (13)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.beehiiv.com Checked 10 Nov 2026 Details →
- 2 Privacy policy — found from the homepage www.beehiiv.com Checked 10 Nov 2026 Details →
- 3 Security / trust page — found from the homepage security.beehiiv.com Checked 10 Nov 2026 Details →
- 4 Campaigns & automation — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 5 Campaigns & automation — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 6 Deliverability infrastructure — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 7 Deliverability infrastructure — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 8 Consent, proof & tracking limits — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 9 Consent, proof & tracking limits — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 10 List ownership, import & exit — found from sitemap developers.beehiiv.com Checked 10 Nov 2026 Details →
- 11 List ownership, import & exit — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →
- 12 Integrations & API — found from sitemap developers.beehiiv.com Checked 10 Nov 2026 Details →
- 13 Integrations & API — found from sitemap www.beehiiv.com Checked 10 Nov 2026 Details →