Inxmail and rapidmail split the bench by criterion rather than by judge. Inxmail is ahead on integrations (6.8 to 4.0; six judges lean Inxmail), its verdict crediting self-service SOAP and REST APIs with public documentation plus named connections to Shopify, Magento, Shopware, OXID, Salesforce and Microsoft Dynamics. rapidmail is ahead on sovereignty (6.8 to 2.7; six lean rapidmail), consent and proof (5.0 to 3.5; six), campaign and automation (6.2 to 5.2; five lean, one tie) and pricing transparency (5.2 to 0.5; six — rapidmail shows prices at the 500-contact step, and Inxmail publishes no prices, noted as a B2B norm). The genuine splits are deliverability (4.0 vs 4.2; five ties, one lean to rapidmail) and list data control (5.7 vs 6.0; four ties, two leans to rapidmail). Weighted totals are on record for five judges; rapidmail scores higher in each, and we found no totals for the e-commerce owner.
Choose Inxmail if
You build your own connectors and need documented self-service APIs — six judges lean Inxmail on integrations (6.8 to 4.0), crediting public SOAP and REST documentation and a Commerce API for transactional workflows.
Your stack includes Shopify, Magento, Salesforce or Microsoft Dynamics — Inxmail documents named connections to these platforms; rapidmail's documented integration surface is Shopware 6 and Plentymarkets.
You send transactional email and need an SMTP mail relay module alongside newsletters — both are named modules in Inxmail's line-up.
You synchronise recipient responses, delivery information and subscription states into your own warehouse or CRM — Inxmail documents bidirectional export for this.
Choose rapidmail if
You need your provider contracted in Germany with servers in Germany — rapidmail's data processing agreement assures server location Germany, and sovereignty runs 6.8 to 2.7 with six judges leaning rapidmail.
Your security review requires an ISO 27001-certified datacenter and daily encrypted backups on German servers — rapidmail documents both.
Your compliance team limits subprocessor exposure to the EU — rapidmail's attribute is EU-only; Inxmail's is US Cloud Act.
You must export consent records together with your lists — rapidmail's CSV and Excel exports include the double opt-in record, and consent and proof runs 5.0 to 3.5 with six leans to rapidmail.
You want to see prices before talking to sales — rapidmail shows prices at the 500-contact step (pricing transparency 5.2 to 0.5, six leans), while Inxmail publishes no prices.
Read this comparison as one judge. Each weighs the same scores by what they care about.
The CRM Manager
Owns the lifecycle programme and measures it. Wants segmentation on real behaviour, journeys that branch, and testing that reports significance rather than a bigger number. Treats a tool that can only broadcast as a mailing list with invoicing.
Inxmail
rapidmail
This judge's pick
Criterion by criterion
Campaigns & automation
Inxmail
A visual drag-and-drop workflow editor with templates for common sequences, an audience editor that segments on attributes and purchasing behaviour, and dynamic personalised content as a documented add-on are the bones of a real lifecycle programme. I found no public information on A/B testing, send-time optimisation or holdout measurement, so I cannot credit anything on the testing and measurement side that a programme owner would build on.
rapidmail
The functions pages show a real journey tool: if/then branching, triggers on signup, recipient activity and date, unlimited steps, workflow templates and a visual overview — plus per-email automation statistics. What I cannot find is any A/B testing with significance reporting, dynamic content per segment or send-time optimisation, and segmentation leans on tags and signup-interest questions rather than behavioural filters, so it is a solid multi-step programme short of measured experimentation.
Deliverability infrastructure
Inxmail
Automatic handling and tracking of delivery errors is documented, and a deliverability team with consulting plus a stated spam-rate guardrail of 0.3 percent is more substance than a marketing inbox figure. But the captured pages name no authentication protocols and I found no public information on SPF, DKIM or DMARC setup, dedicated IP options, warm-up or inbox-placement testing.
rapidmail
DKIM, SPF and DMARC are documented in real depth — policy options explained, SPF set as a CNAME, advice for sends above 5,000 recipients, status indicators and timing expectations. I found no public information on hard-bounce suppression, complaint-loop handling, dedicated-IP options or inbox-placement testing, so the operational half of deliverability rests on the vendor's Zustellbarkeit claims rather than documented process.
Consent, proof & tracking limits
Inxmail
Tracking and reporting are an optional integration rather than always-on, which I rate, and double opt-in appears in the Shopware and Meta Lead Ads integrations with consents named as data you can transfer to a leading system. Beyond that I found no public information on a platform-wide consent record, its source and wording, unsubscribe handling across lists, or retention rules for inactive subscribers.
rapidmail
Double opt-in is applied automatically, and the consent record is genuinely exportable — IP address, date and time for both the signup and the confirmation, plus current status. Tracking, however, is documented as always present (tracking pixel and tracking links for every mailing), and I found no public information on switching tracking off per campaign, a pixel-free mode, versioned form wording or preference-centre granularity.
List ownership, import & exit
Inxmail
Bi-directional synchronisation is genuinely evidenced: recipient responses, delivery information, tracking data, subscriptions and unsubscriptions flow into your campaign management tool or data warehouse, alongside automated CSV import and a self-service API. I found no public information on documented deletion of a subscriber across all records, export throttling, or exporting campaigns and templates, which is the line between a good sync and a true exit.
rapidmail
Recipient lists export as CSV or Excel with subscription status and the double-opt-in record, and per-mailing recipient activity — opens, clicks, bounces, unsubscribers — is exportable in selectable categories, so my engagement history can leave with the list; list duplicate, merge and restore-from-backup operations are documented too. I found no public information on exporting campaigns or templates, on a full-account export, or on deletion being evidenced rather than asserted; no export throttling is mentioned either way.
Integrations & API
Inxmail
The strongest surface in the captures: a documented REST and SOAP API usable without a partner agreement, an API to create and send mailings from your own application, a Commerce API that triggers events and returns transaction results, and named integrations across Shopify, Magento, OXID, Salesforce, Dynamics and the Zapier, Make and n8n layer. I found no public information on documented rate limits, a sandbox, or webhook retries, which is what holds it short of the top band.
rapidmail
There is a documented API with its own developer site that can send mailings and manage recipients, plus native Shopware 6 and plentymarkets connections — decent coverage of the German shop stack. But the captured pages name no CRM integration, and I found no public information on webhooks, rate limits or a sandbox, which is precisely the event surface I build lifecycle triggers on.
European sovereignty
Inxmail
The contracting entity is evidenced as Inxmail GmbH with a German CEO and a German-language home market, and that is where confirmation ends. I found no public information on data residency, ownership or a subprocessor list on the captured pages, so the chain a DACH buyer must audit before sign-off is unverifiable from what is published.
rapidmail
A German contracting entity in Freiburg, German hosting stated with an online-signable data processing agreement, an ISO 27001-certified datacenter and an external data protection partner — the operation reads sovereign on its face. But the datacenter operator goes unnamed, a complete subprocessor list for the send chain is not published, and the broadest all-data-in-Germany wording sits on the marketing page, while the vendor's own website runs Google, HubSpot and Mixpanel tooling — as a buyer who weights this heavily, I cannot verify the chain end to end from public pages.
Pricing transparency
Inxmail
No price figures appear in the captures at all; what exists is a scope description for the SMTP relay — hosting and administration, one hour of user support per month and deliverability team assistance included, open and click rate tracking as an optional service — with a demo request as the entry point. A buyer cannot compute any invoice for their list size or send volume from these pages.
rapidmail
Three tiers are priced per month at 500 contacts with the feature boundaries spelled out — one, five or unlimited automations, sender addresses and recipient lists per plan — plus a pay-per-send option and a free start. I found no public information on overage rates, VAT treatment or prices for contact counts above 500, so the real invoice for a growing list is not computable from the captured pages alone.
Sovereignty, side by side
Dimension
Inxmail
rapidmail
Legal entity
Not determined
Incorporated in DE
Ownership
Not determined
Not determined
Data residency
Not determined
EU only
Subprocessors
Not determined
EU only
Facts, side by side
Only facts both products carry under the same definition — anything else would not be a fair row.