Open
Open
Open
Open
The problem

Your contact list shouldn't live in someone else's account

Mailchimp, HubSpot, ActiveCampaign — every one of them is a SaaS account on shared infrastructure, priced per contact, with your audience, your behavioural data and your sending reputation held on a machine you don't control and can't see. Grow the list and the bill grows with it; leave and the data is theirs to make hard to export.

A Mautic environment is the other model. One tenant, one instance, one database — your contacts, your campaign history, your tracking data on hardware we own, under EU jurisdiction, with no per-contact tax and no lock-in. Open-source marketing automation, run the way self-hosting was supposed to work: isolated, sovereign, and yours.
high-performance-cloud-compute.jpg
What every environment includes

The full stack, provisioned and sending

Mautic installed and ready — current release, provisioned and migrated, admin account seeded on day one. Log in and build your first segment; nothing to install.
Your own MariaDB server — every contact, campaign, form submission and tracking event in a database that is yours alone, not a row in a shared multi-tenant table.
Real cron from the first minute — segment rebuilds, campaign triggers, the email send queue and scheduled broadcasts all fire on schedule as native platform jobs, the way Mautic requires. No "did the cron run?" guesswork.
A dedicated IP for your sending — your deliverability reputation is yours, built on an IP no spammer shares. For email marketing, the IP is the asset.
Contact tracking that just works — tracking pixels, links, forms and landing pages all derive from your own canonical domain over automatic TLS, so opens, clicks and page hits attribute correctly.
Nightly backups included — database plus uploaded media, on separate platform storage.
Everything every environment gets — sealed networking, dedicated IP, automatic TLS, reserved compute.
Sending, your way

Bring your own sending — or a dedicated one

Mautic is the automation engine; the mail transport is yours to choose. Point your environment at your existing SMTP relay or transactional provider from the Mautic UI, or run a dedicated cold/outreach sending setup on a separate domain to keep your marketing reputation cleanly isolated from your transactional mail. Either way the queue, the throttling and the bounce handling run inside your environment on your schedule — not shaped by a shared provider's limits.
Your transport, your rules — configure SMTP in Mautic; change it whenever you like.
Reputation isolation — a dedicated IP and, if you want, a dedicated sending domain, kept separate from everything else.
The queue is yours — send rate, retry and spool behaviour tuned to your lists, not a SaaS tier.
For marketers and the agencies who run them

We run the substrate. You run the marketing.

We guarantee the environment: the pods, the database, the cron worker, the network, uptime and provisioning. You run Mautic — your segments, campaigns, emails, landing pages, plugins and integrations. It's stock, current Mautic with the full admin, so everything you know and every guide you've read still applies.

Migrate in with a standard Mautic database export and media; migrate out the same way. Your audience is portable because it's yours.
Isolation is a compliance feature

Your audience data on your own ground

Contacts in your own database — names, emails, behavioural profiles and consent records in your own MariaDB server, not pooled with hundreds of other senders' lists.
A GDPR posture you can actually describe — one tenant, one sealed environment, EU hardware only. "Where does our marketing data live?" has a straight answer: Sofia or Amsterdam, on hardware Radibase owns.
Sovereign EU ground — no US parent, no CLOUD Act reach. A real answer for European marketing teams handling European personal data, not a region checkbox.
Reserved resources, no contact caps, no send-volume surcharge — you pay for the environment you reserve, not for how big your list grows or how much you send.

Under the hood

Compute
Dedicated Mautic (Apache/PHP) pods, resources reserved in-cluster (request = limit); Shared or Dedicated physical CPU clusters — your choice
Database
Your own MariaDB 11 pod on replicated Ceph block storage
Cron
Native scheduled jobs for segments, campaigns, message queue and broadcasts — continuous, not visitor-triggered
Storage
Distributed CephFS volume for config and uploaded media, replicated across nodes
Mail
Bring-your-own SMTP configured in Mautic, or a dedicated sending setup on a separate domain; dedicated IP for reputation
Network
Default-deny NetworkPolicies: environments cannot reach each other, period
Ingress
Dedicated IP per environment, TLS at our EU edge for your tracking domain, HTTP/2
Backups
Nightly database plus media archive, on separate platform storage
Releases
Every component version-pinned down to image digests; upgrades staged on test environments first
Jurisdiction
EU company, own network (AS202309), own hardware in Sofia & Amsterdam, own keys

Plans

Mautic is a light, steady workload — the periodic spike is the cron worker rebuilding segments and draining the send queue. Plans start at a full Standard environment because contacts, campaign history and tracking events deserve real reserved capacity, not a scrap of a shared box. Per environment, per month, excl. VAT. Dedicated IP and nightly backups included in every plan.
Plan
Resources
Sofia — Shared CPU ★
Sofia — Dedicated CPU
Amsterdam — Shared CPU ★
Amsterdam — Dedicated CPU
Standard
4 vCPU · 16 GB RAM · 100 GB SSD
€45
€105
€55
€130
Pro
8 vCPU · 32 GB RAM · 200 GB SSD
€90
€210
€110
€260
Enterprise
16 vCPU · 64 GB RAM · 400 GB SSD
€180
€420
€220
€520
Plan
Resources
Standard
4 vCPU · 16 GB RAM · 100 GB SSD
Pro
8 vCPU · 32 GB RAM · 200 GB SSD
Enterprise
16 vCPU · 64 GB RAM · 400 GB SSD
Plan
Sofia — Shared CPU ★
Standard
€45
Pro
€90
Enterprise
€180
Plan
Sofia — Dedicated CPU
Standard
€105
Pro
€210
Enterprise
€420
Plan
Amsterdam — Shared CPU ★
Standard
€55
Pro
€110
Enterprise
€220
Plan
Amsterdam — Dedicated CPU
Standard
€130
Pro
€260
Enterprise
€520
★ Shared CPU is our recommended option — same isolation and features in both modes; the price difference is the physical CPU guarantee level alone. Disk grows online; plan upgrades are applied in place. Volume pricing for multi-environment agencies on request.

Frequently asked

Is this the paid Mautic cloud?
No — it's self-hosted, open-source Mautic (GPL), the full community edition, running as your own instance. No per-contact pricing, no feature paywall, no seat metering. You get the whole product and a database that's yours.
Can it send my campaigns and newsletters?
Yes. Mautic runs the segments, campaigns, emails and landing pages; you connect a sending transport (your own SMTP/transactional provider, or a dedicated sending domain we help you isolate). The send queue and scheduling run inside your environment with a dedicated IP for reputation.
Do you configure my campaigns or deliverability?
No — same boundary as everywhere on the platform. We guarantee the environment: database, cron, network, uptime, provisioning. Your segments, campaigns, sending domain and warm-up are yours. We give you the isolated, dedicated-IP substrate that makes good deliverability possible.
Can I migrate an existing Mautic in?
Yes — the standard way: a database export plus your media. Out the same way. It's your instance and your data; no lock-in.
Is there a limit on contacts or sends?
No contact caps and no per-send surcharge. You reserve an environment; what you do inside it — list size, send volume — isn't metered. Sustained heavy sending is a reason to size up the plan, not a surprise on the invoice.
Where is my audience data?
Sofia or Amsterdam — your choice — on hardware owned by Radibase, an EU company on its own network. No US parent, no CLOUD Act exposure. Your contacts' personal data stays under EU jurisdiction.

Own your marketing stack