Panel rating · 6 judges · How to read the stars

Category median

Sovereignty: 2 of 6 dimensions proven

0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.

by Apsis AB · www.apsis.com

Report an error on this page Is this your product? →

Link to this page

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

Add ?theme=dark to the image address for dark backgrounds. The badge shows the category and the month of the latest evaluation, and EU-Made where that is the product’s provenance. It never shows a score.

Apsis One at a glance

Vendor
Apsis AB
Headquarters
Incorporated in Sweden source, captured 10 Nov 2026
Data hosting
In the EU by default source, captured 10 Nov 2026
Free plan
Not stated on the vendor’s pages as of 10 Nov 2026
Panel verdict
The AI panel rates Apsis One 3/5, the mean of 6 judges. Apsis One, an email marketing and automation platform from Swedish vendor Apsis AB, is strongest on campaign and automation at 7 to 7, deliverability at 6 to 7 and integrations at 6 to 7. how scores are made
As of
Vendor pages captured 10 Nov 2026; evaluated by the panel 11 Nov 2026. all sources

Apsis One alternatives, European ones first →

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

The panel's verdict

Apsis One, an email marketing and automation platform from Swedish vendor Apsis AB, is strongest on campaign and automation at 7 to 7, deliverability at 6 to 7 and integrations at 6 to 7. Judges credit the visual flow builder with custom-event triggers from a website, app or CRM; email authentication — SPF pre-configured, 2048-bit DKIM, DMARC and IP reputation monitoring on Apsis-owned IPs — and a REST API with OAuth 2.0, published rate limits and native Tribe CRM, webCRM and efficy CRM connectors. Sovereignty and pricing transparency sit at 4. European hosting applies to customers subscribing from a European country, the privacy policy names suppliers without stating their locations, and beyond Send at 110 EUR, Automate at 300 EUR and Grow at 450 EUR no billing period or contact limits are stated, so a real invoice cannot be computed. Consent and proof spans 4 to 6, split between deep double opt-in documentation and imports that land as regular opt-in receiving sendings, with no public information on switching open and click tracking off.

Report an error

Speaks for it

  • Campaign and automation scores run 7 to 7, on a visual drag-and-drop flow builder with a Listen entry node fed by subscription, form, segment and custom events, branching, time delays, configurable re-entry and A/B test variants.
  • Deliverability scores run 6 to 7 on SPF pre-configured in Apsis DNS, 2048-bit DKIM per domain set up with the delivery team, DMARC guidance, automatic exclusion after three hard bounces, and IP reputation and blacklist monitoring on Apsis-owned IPs.
  • The REST API is documented with OAuth 2.0, published rate limits returning HTTP 429, a 100 KB request-body cap, EU and APAC hosts, custom events in, and native real-time integrations with Tribe CRM, webCRM and efficy CRM.
  • Double opt-in is documented in depth: four consent states, pending opt-ins blocked from every send, a customisable confirmation email and page, and a per-subscriber consent timeline recording email consent and confirmed double opt-in.
  • List data control runs 5 to 6: import from CSV or XLSX handles add, update, unsubscribe and delete with scheduled pickup from Apsis Cloud SFTP, and profile deletion is documented as permanent across the entire account.

Report an error

Held against it

  • Sovereignty sits at 4, with European hosting conditional on subscribing from a European country, named suppliers covered by standard contractual clauses with supplementary measures rather than stated locations, and we found no public information on a data processing agreement.
  • Pricing transparency sits at 4: beyond Send at 110 EUR, Automate at 300 EUR and Grow at 450 EUR, we found no public information on the billing period, contact or send limits, overage rates or VAT treatment.
  • Bulk exports exclude the event timeline — only the single-profile GDPR export in JSON includes events — and the export key cannot be reused as an import key.
  • We found no public information on switching open and click tracking off, on a preference centre, or on one-click unsubscribe mechanics.
  • We found no public information on a named shop platform integration, webhook retries or a sandbox environment.

Report an error

Best for

  • You run consent-based lifecycle marketing — welcome or win-back flows — driven by custom events fired from your website, app or CRM.
  • You want deliverability managed by the vendor: authentication set up with the delivery team at onboarding, warm-up above 10,000 recipients a day, and IP reputation and blacklist monitoring on Apsis-owned IPs.
  • You already work in Tribe CRM, webCRM or efficy CRM and want native real-time sync alongside a documented REST API.
  • You operate where double opt-in is required by law — the vendor's documentation names Germany — and need a per-subscriber consent timeline as proof.

Report an error

Avoid if

  • You need transactional email: the vendor states Apsis One is not designed for messages like order confirmations or password resets.
  • You must migrate your full behavioural history: bulk exports exclude the event timeline, which only leaves through the single-profile GDPR export, one profile at a time.
  • You need to compute the real invoice before committing — ask the vendor: the public pages we read do not show it
  • You require unconditional European hosting: the privacy policy's European data centres apply only if you subscribe from a European country, and named suppliers are covered by standard contractual clauses with supplementary measures rather than stated European processing.

Report an error

The scores

Panel median The median of the judges’ scores per criterion. Each label opens its reasoning below.
Scores per criterion, in stars out of 5
Criterion Panel median
Campaigns & automation 3.5 of 5
Deliverability infrastructure 3.5 of 5
Consent, proof & tracking limits 2.5 of 5
List ownership, import & exit 3 of 5
Integrations & API 3.5 of 5
European sovereignty 2 of 5
Pricing transparency 2 of 5

Campaigns & automation

Show 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.

Report an error

The CRM Manager

Marketing Automation flows are the real thing: a visual drag-and-drop canvas with a Listen entry node fed by subscription, form, response, segment and custom events, Split and Check Profile branching, wait-for-event gates, re-entry control, termination tags, dynamic scheduling on event time and per-node profile counts. What the pages do not show is send-time optimisation, holdout groups for measurement, or A/B testing that reports significance — variants exist, and the reporting I can find counts profiles per node rather than winners with confidence. 3 4

Report an error

The Deliverability Engineer

A visual drag-and-drop flow builder with a single entry node listening on subscription events, form and page interactions, response data, segment entry and exit, and custom events from a website, app or CRM, branching on profile attributes and events, with configurable re-entry, A/B test variants and per-node profile counts. We found no public information on dynamic content per segment, send-time optimisation or significance reporting for tests, which keeps it short of the top of the journey-builder class. 3 4

Report an error

The Data Protection Officer

The help centre documents a visual drag-and-drop flow builder with a single entry Listen node, branching on profile attributes and events, custom events from a website, app or CRM as triggers, time delays, configurable re-entry caps and per-node profile counts, plus A/B test variants on campaigns. I found no public information on send-time optimisation, dynamic content per segment, or testing that reports significance, so it sits just short of the top band. 3 4

Report an error

The Shop Owner

The drag-and-drop flow builder branches on profile attributes and events, with email, SMS, wait, update-profile and webhook nodes, entry from form submissions, subscription events, segment changes and custom events fired from a website or app, plus re-entry caps and external-signal termination — enough to run a real welcome or win-back series. I found no public information on send-time optimisation, dynamic content per segment, or testing that reports significance, and the vendor states plainly it is not designed for transactional messages like order confirmations. 3 4

Report an error

The Integrator

The visual flow builder is the real thing: a Listen node with entry from subscription events, forms, segment activity and custom events fired from a website, app or CRM via the API, branching on profile attributes and events, time delays, configurable re-entry, and A/B test variants on single-message campaigns. The API also lets you create and publish campaigns programmatically, which is what I need for wiring. We found no public information on send-time optimisation or statistical-significance reporting for tests, which keeps this below the top tier. 3 4 12

Report an error

The Skeptic

A visual drag-and-drop journey builder with Listen, condition and time nodes, branching on profile attributes and events, entry triggered by form submissions and custom events from a website or app, and A/B test variants for campaigns. We found no public information on send-time optimisation, dynamic content per segment, or testing that reports significance, which keeps it a step below the top level. 3 4

Report an error

Deliverability infrastructure

Show 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.

Report an error

The CRM Manager

Authentication is handled properly — SPF pre-configured, 2048-bit DKIM per domain set up with the delivery team during onboarding, DMARC guidance, and a private per-account technical sender domain so one sender cannot poison another. Bounce handling is genuinely automatic (hourly soft-bounce retries for 48 hours, greylisting retried after 15 minutes, addresses excluded after three hard bounces) with a documented warm-up above 10,000 recipients a day and a delivery team monitoring IP reputation and blacklists; I found no public information on seed or inbox-placement testing, reputation reporting surfaced per sending domain, or engagement-based sunsetting. 5 6

Report an error

The Deliverability Engineer

The help centre documents genuine sending discipline: SPF preconfigured in Apsis DNS, per-domain 2048-bit DKIM created during onboarding with the delivery team, DMARC guidance, automatic exclusion after three hard bounces, hourly soft-bounce retries for 48 hours, a 15-minute greylisting retry, warm-up for accounts intending more than 10,000 recipients a day, IP reputation and blacklist monitoring by the delivery team, and a private per-customer technical sender subdomain that isolates one account's behaviour from another's. We found no public information on dedicated IP options for customers, inbox-placement testing, engagement-based sunsetting or reputation reporting surfaced per sending domain, and the advertised 99 percent delivery rate I discount on principle. 5 6

Report an error

The Data Protection Officer

Authentication is handled properly: SPF is pre-configured, DKIM is set up with the Delivery team at onboarding with 2048-bit keys per domain, DMARC alignment runs through DKIM, and each account sends from a private per-customer technical sender domain on Apsis-owned IPs. A documented warm-up above 10,000 recipients a day, hard-bounce exclusion after three bounces, hourly soft-bounce retries for 48 hours, a 15-minute greylisting retry, and Delivery-team reputation and blacklist monitoring are all evidenced. I found no public information on seed or inbox-placement testing, engagement-based sunsetting, or reputation reporting per sending domain surfaced to the customer. 5 6

Report an error

The Shop Owner

Authentication is set up properly: SPF pre-configured, DKIM key pairs created during onboarding with a private per-customer technical sender subdomain, and DMARC guidance, all on sending IPs owned and managed by Apsis, whose delivery team performs warm-ups, IP reputation monitoring and blacklist checks. Hard bounces are suppressed automatically after three strikes, soft bounces retried hourly for up to 48 hours, and warm-up above 10,000 recipients a day is documented; I found no public information on seed or inbox-placement testing or on reputation reporting surfaced to the customer. 5 6

Report an error

The Integrator

SPF is pre-configured in the Apsis DNS, DKIM is generated per domain during onboarding with Apsis holding the private key on its mail server, DMARC configuration in the customer's DNS is documented, and hard bounces are auto-suppressed after three failures with hourly soft-bounce retries for 48 hours and a 15-minute greylisting retry. The vendor documents its Delivery team running IP warm-ups, reputation monitoring and blacklist checks on Apsis-owned IPs — a service model, not just tooling. We found no public information on seed or inbox-placement testing, engagement-based sunsetting, or reputation reporting surfaced per sending domain. 5 6

Report an error

The Skeptic

SPF is pre-configured, DKIM uses 2048-bit keys set up with the delivery team, DMARC guidance is published, three hard bounces trigger automatic exclusion, soft bounces retry hourly for 48 hours, warm-up applies above 10,000 recipients a day, and IP reputation, warm-ups and blacklist checks are run by the vendor's team on IPs Apsis owns. We found no public information on dedicated IP options for customers, seed or inbox-placement testing, or complaint feedback loops the vendor operates itself, so it sits above the middle of the scale without reaching the level above. 5 6

Report an error

List ownership, import & exit

Show 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.

Report an error

The CRM Manager

Import is serious — CSV or XLSX with add/update/unsubscribe/delete from one wizard, a format checklist, scheduled pickups from Apsis Cloud SFTP and a file import report — and profile deletion is documented as permanent across the entire account, with API access for reading and writing the list. Export runs from the 360 profile view, a subscription, a segment or a report as CSV, XLSX or GZIP including attributes and tags, in batches via the API, but bulk exports exclude the event timeline — only the single-profile GDPR export in JSON includes events — so engagement history does not travel with the list, and the export key cannot be used to import profiles back. 9 10 11

Report an error

The Deliverability Engineer

CSV and XLSX import supporting add, update, unsubscribe and delete actions, scheduled imports from an Apsis cloud SFTP server, permanent irreversible deletion of a profile across the account, and exports from the profile, subscription, segment and report views in CSV, XLSX and GZIP plus API bulk export give a workable exit path. Bulk exports carry attributes and tags but exclude the event timeline, which only appears in the single-profile GDPR export as JSON, and UI exports cap at 50 MB; we found no public information on exporting engagement history in bulk, or campaigns and templates. 9 10

Report an error

The Data Protection Officer

Import is well covered — CSV or XLSX with add, update, unsubscribe and delete from one wizard, scheduled pickup from a cloud SFTP server, and an import report — and deletion is documented as permanent and account-wide. The exit is weaker: bulk exports carry attributes and tags but explicitly exclude the event timeline, so the behavioural history only leaves one profile at a time in a GDPR export, the export key cannot be reused for import, and I found no public information on exporting campaigns or templates. 9 10 11

Report an error

The Shop Owner

File import handles CSV and XLSX with add, update, unsubscribe and delete actions, schedulable via their cloud SFTP, and export runs from subscriptions, segments and reports including attributes and tags, through the interface or the API in batches; deleting a profile is documented as removing all its data from the entire account, irreversibly. The catch for me is that bulk exports exclude the event timeline — engagement history only comes out one profile at a time through the single-profile GDPR export — and I found no public information on exporting campaigns or templates. 9 10 11

Report an error

The Integrator

Import is solid — CSV or XLSX supporting add, update, unsubscribe and delete actions, a file import report, and scheduled imports picked up from an Apsis Cloud SFTP server — and deletion is stated to permanently remove a profile and all its data from the entire account. Exports cover profiles, subscriptions, segments and campaign reports (openers, clickers) in CSV, XLSX or GZIP, with batch export via the API. The vendor states that bulk exports include profile attributes and tags but not the event timeline — only the single-profile GDPR export in JSON includes events — and the export key cannot be reused as an import key, so exit at scale is not full-fidelity. 9 10

Report an error

The Skeptic

File import handles add, update, unsubscribe and delete from one wizard with scheduled imports over SFTP, deletion is documented as permanently removing a profile and all its data across the account, and exports run from four places in open formats with a bulk export API. However, the event timeline is not included in bulk exports — only the single-profile GDPR export as JSON includes events — the UI caps exports at 50 MB, the export key cannot be reused as an import key, and we found no public information on exporting campaigns or templates. 9 10 11

Report an error

Integrations & API

Show 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.

Report an error

The CRM Manager

A documented REST API with OAuth 2.0, JSON payloads, keys, a full reference page with a changelog, stated rate limits (429 responses, 100KB request bodies), regional EU and APAC hosts and even a published API pricing article, with custom events posting in and data syncing to and from the platform. Native real-time integrations are named for three CRM systems (Tribe, webCRM, efficy) and a webhook node fires outbound from flows; I found no public information on a named major shop platform, webhook retries or a sandbox. 1 11 12

Report an error

The Deliverability Engineer

A documented REST API with OAuth 2.0, a full reference page with examples, a changelog, error handling, published rate limits returning HTTP 429, a 100 KB request-size limit, custom events in, profile create, import, update and merge, and separate EU and APAC regional hosts, alongside native real-time CRM integrations with Tribe CRM, webCRM and efficy CRM plus Zapier workflows. We found no public information on a named shop platform integration, a sandbox environment, or retry behaviour for the flow webhook node. 1 11 12

Report an error

The Data Protection Officer

There is a documented REST API with OAuth 2.0, API keys, a reference page, changelog, error handling, stated rate limits and a 100KB request-body cap, plus named native CRM connectors syncing in real time, a webhook action node inside flows, and custom events posted by API. I found no public information on a named shop platform integration, webhook retries, or a sandbox. 1 3 11 12

Report an error

The Shop Owner

The REST API is documented like something I could build against — OAuth 2.0, a method reference with examples, a changelog, rate-limit and error behaviour, batch export, custom events in, two-way data sync — and flows can push out through a webhook node, with native real-time CRM connectors to Tribe CRM, webCRM and efficy CRM, ecommerce named as an integration category, and Zapier mentioned on the Send plan. I found no public information naming a specific shop platform, on webhook retries, or on a sandbox. 1 2 3 10 11 12

Report an error

The Integrator

The API surface is documented the way I want to see it: REST with OAuth 2.0, a reference page with specifications and examples, a changelog, regional EU and APAC hosts, rate limits published in the Developer Hub with HTTP 429 on the limit, and a 100 KB request-body cap returning 413. Custom events flow in via the API, native integrations with Tribe CRM, webCRM and efficy CRM sync data in real time, and flows can call out through a Webhook node. We found no public information on webhook retries, a sandbox environment, or a deprecation policy — a changelog is not a deprecation policy — and the named native integrations are CRM systems rather than a major shop platform. 12 11 1 3 2

Report an error

The Skeptic

A documented REST API with OAuth 2.0 and keys, a full reference with changelog and error handling, published rate limits including the 429 response and a 100 KB request body cap, custom events in, campaign creation via API, a webhook node in automation, and native CRM integrations with Tribe CRM, webCRM and efficy CRM. We found no public information on a named major shop platform, webhook retries, or a sandbox, so it clears the middle level without reaching the one above. 1 3 11 12

Report an error

European sovereignty panel opinion

Show 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.

Report an error

The CRM Manager

The contracting entity is Apsis International AB in Malmö with a DPO in Utrecht, and subscribers from European countries get European data centres — but that residency is conditional, and where the sending and tracking infrastructure sits is not stated, with all sending IPs owned and managed by the vendor. Named suppliers handling personal data include Intercom, Amplitude, Planhat, Leexi and Google, covered by standard contractual clauses with supplementary measures rather than European processing; I found no public information on a data processing agreement or hosting options. 2 6

Report an error

The Deliverability Engineer

A Swedish contracting entity, European data centres for customers subscribing from a European country, a data protection officer in Utrecht, and standard contractual clauses with supplementary measures for suppliers are stated. The privacy policy names Intercom, Amplitude, Planhat, Leexi and Google without locations, an APAC API region exists, and we found no public information on a data processing agreement, on hosting for subscribers outside Europe, or on where the sending infrastructure sits. 2 6 12

Report an error

The Data Protection Officer

A Swedish contracting entity acting as processor, a data protection officer in Utrecht, and European data centres for customers who subscribe from a European country are proven — but the EU hosting promise is conditional, and I found no public information on where other customers' platform and tracking data is hosted. I found no public information on a data processing agreement or on the locations of the named suppliers Intercom, Amplitude, Planhat and Leexi, and the privacy policy invokes standard contractual clauses with supplementary measures, so transfers that need a Schrems II argument are contemplated rather than excluded. 1 2

Report an error

The Shop Owner

The contracting entity is Apsis International AB in Malmö, the privacy policy says the platform is hosted in Europe if you subscribe from a European country, the DPO sits in Utrecht, and the website runs from data centres in Germany and Switzerland. But the same policy names suppliers — Intercom, Amplitude, Planhat, Leexi, and Google for marketing — without stating locations, leans on standard contractual clauses with supplementary measures for transfers, and I found no public information on a data processing agreement or on the named infrastructure behind the European hosting. 1 2

Report an error

The Integrator

Apsis International AB is the Swedish contracting entity, the DPO sits in Utrecht, and subscribers from European countries are hosted in data centres in Europe, with the page silent on where non-European customers' platforms are hosted. Subprocessors such as Intercom, Amplitude, Planhat and Leexi are named with standard contractual clauses and supplementary measures as the safeguard, but without stated locations, and the privacy policy shows personal data shared with Google for marketing purposes. We found no public information on a published data processing agreement or on where the sending infrastructure is hosted, so the chain is European at the top but not proven end to end. 2 1 6

Report an error

The Skeptic

The contracting entity is Apsis International AB in Malmö, the DPO sits in Utrecht, and European subscribers are hosted in European data centres — but that hosting is conditional on subscribing from a European country. We found no public information on a data processing agreement, on where the sending infrastructure runs, or on the locations of named suppliers such as Google, Intercom, Amplitude, Planhat and Leexi, which are covered by standard contractual clauses with supplementary measures rather than European processing. 1 2

Report an error

Pricing transparency

Show 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.

Report an error

The CRM Manager

Three plan prices are public — Send at 110 EUR, Automate at 300 EUR, Grow at 450 EUR, plus a 14-day free trial at 0 EUR — and the offers point to a price-calculator URL, with a published API pricing article in the help centre. The captured pages never state the billing period, what contact or send volume those prices cover, or overage and VAT treatment, so I cannot compute the real invoice from public pages alone. 2 11

Report an error

The Deliverability Engineer

Three plans carry public prices — Send at 110 EUR, Automate at 300 EUR, Grow at 450 EUR — beside a 14-day free trial with no credit card required, and an API pricing article exists. The captured pages state no billing period, contact or send limits, overage rates or add-on prices, so the real invoice for a given list size and send volume cannot be computed from public pages alone. 2 11

Report an error

The Data Protection Officer

Three plans are priced publicly — Send at 110 EUR, Automate at 300 EUR, Grow at 450 EUR — alongside a zero-cost 14-day trial and documented API pricing. I found no public information on the billing period, contact or send limits, overage rates, feature boundaries or VAT treatment, so a real invoice cannot be computed from the captured pages. 2 11

Report an error

The Shop Owner

Three tiers carry public prices — Send at 110 EUR, Automate at 300 EUR, Grow at 450 EUR — alongside a 14-day free trial, a price-calculator page and an API pricing article. But I found no public information on contact or send volumes per tier, the billing period, overage rates or VAT treatment, so I cannot compute the real invoice for my list from what is published. 2 11

Report an error

The Integrator

Three plans carry public prices — Send at 110 EUR, Automate at 300 EUR, Grow at 450 EUR — alongside a 14-day free trial at 0 EUR with no credit card required, and API pricing is documented in the help centre. The offer URLs point at a price-calculator page, but the captured pages give no billing period, contact or volume tiers, feature boundaries or overage rates for those figures. I cannot compute an annual invoice for a given list size from the public information captured. 2 11

Report an error

The Skeptic

Three plans carry public euro prices — Send at 110, Automate at 300, Grow at 450 — next to a 14-day free trial without a credit card, and an API pricing article exists. But we found no public information on the billing period, contact or volume limits per tier, overage rates or VAT treatment, and although the offers point at a price-calculator page we found no public information on what that calculator shows, so the real invoice for a given list size cannot be computed from what is published. 2 11

Report an error

European sovereignty — proven facts

2 of 6 dimensions proven

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

Hosting location EU by default unverified
Why unverified?

European hosting is conditional on subscribing from a European country, and the page is silent on where non-European customers' platform data is hosted.

2/4 pts 2 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 Apsis One

Is Apsis One European?

Not determined: the vendor’s pages as captured do not say where Apsis One is based. Its vendor, Apsis AB, is incorporated in Sweden, per the vendor’s page captured 10 Nov 2026.

Where does Apsis One store data?

Apsis One stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 10 Nov 2026.

Does Apsis One have a free plan?

Not stated on the vendor’s pages as of 10 Nov 2026.

What are the best alternatives to Apsis One?

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: Apsis One alternatives.

Where this could be wrong

What we left out

A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.

Sources (12)

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

  1. 1 Vendor page www.apsis.com Checked 10 Nov 2026 Details →
  2. 2 Privacy policy — found from the homepage www.apsis.com Checked 10 Nov 2026 Details →
  3. 3 Campaigns & automation — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  4. 4 Campaigns & automation — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  5. 5 Deliverability infrastructure — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  6. 6 Deliverability infrastructure — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  7. 7 Consent, proof & tracking limits — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  8. 8 Consent, proof & tracking limits — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  9. 9 List ownership, import & exit — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  10. 10 List ownership, import & exit — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  11. 11 Integrations & API — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →
  12. 12 Integrations & API — found from sitemap help.apsis.one Checked 10 Nov 2026 Details →