Skip to main content
Brand My Inbox
Get started

On-premise and private cloud

Marketing automation, CRM and AI agents that run inside your own network

Yes, the whole platform can be installed at your site. Email marketing, SMS, WhatsApp, CRM, marketing automation and AI agents run on your servers, in your data centre or in your own cloud account, with the same features as our cloud. Customer lists, consent records and conversations stay in your database, under your security policy.

Plan an installationHow a deployment works

Every installation is scoped with your IT and information-security teams.

2
CPU architectures, amd64 and arm64, so the images run on the servers you already own
9,000+
automated tests in four suites, run before a change is merged, including tenant isolation in the database
3
interface languages: English, Hebrew right-to-left, and Spanish

What runs inside your network, and what leaves it?

Everything that holds data runs with you. Only what must travel leaves: the message, through the email or SMS provider, to its recipient, and the call to the AI provider you chose.

Your servers or private cloud

Database, contacts, consent, files, logs, dashboard

Sending layer

Email, SMS and WhatsApp from your verified domain and number

Email sending provider, then the recipient inbox
SMS provider and Meta, official API
Your AI provider, on your key

Everything in the cloud product, installed with you

Data that never leaves

Contacts, consent records, deals, tickets, conversation transcripts, files and audit logs live in your PostgreSQL, under your backup policy.

Email marketing and transactional email

Campaigns, newsletters and system email signed with your domain's DKIM, with suppression that applies across every channel.

SMS and WhatsApp

Text messages through your SMS provider and WhatsApp through Meta's official Business API only, from one contact list and one consent record.

Marketing automation

Behaviour-triggered journeys with versions, simulation before activation and rollback, run by the same engine as the cloud.

AI agents and chatbots

Assistants that answer from your own content, file every lead in the CRM and hand over to a person, on your organisation's AI key.

Isolation enforced in the database

Departments, brands and clients are separated by row-level security in PostgreSQL, so a misconfigured screen cannot leak another team's list.

The EmailPro dashboard with campaign, contact and automation activity, the same screen an on-premise installation runs
The same EmailPro dashboard runs in the cloud and inside your network.

Cloud, private cloud or on-premise: which one fits?

The same software in three places. What changes is who owns the servers, who upgrades them and where the data sits.

OptionWhere the data livesWho operates itBest for
EmailPro cloudOur infrastructure in EuropeUsMost businesses, live the same day
Your private cloudYour own cloud accountAgreed per projectOrganisations with an existing cloud policy
On-premiseYour data centreYour team; our part agreed per projectBanking, insurance, health, government, defence

All three run the same code. What differs is location and responsibility.

How do you deploy the platform on your own infrastructure?

  1. 1

    Scoping with IT and security

    We map your network, identity systems, backup policy and the systems to connect: ERP, existing CRM, website and contact centre. You leave with a written requirements document.

  2. 2

    A staging environment on your infrastructure

    An isolated environment with synthetic data, so your security team can test it before a single real record goes in.

  3. 3

    Channels and systems connected

    Your sending domain is authenticated, your SMS provider, WhatsApp Business account and AI key connected, and lists migrated with each recipient's consent record.

  4. 4

    Go-live and handover

    Training and documentation for your team are agreed in the project and written during it. Releases are versioned images, and you choose when to install each one.

What is ready today, and what is agreed per project?

An installation has two halves: the software, which already supports running on your infrastructure, and the service around it, which is set for each organisation. This is where each part stands.

Ready in the software

  • The same code as the cloud product for every channel, the CRM and the AI agents
  • Container definitions for the mail API, relay, app and marketing service, built for amd64 and arm64
  • PostgreSQL with tenant isolation enforced by row-level security
  • AI agents on your organisation's own provider key, or switched off entirely
  • WhatsApp through Meta's official API only

Agreed per project

  • Who installs the platform and who operates it
  • Support hours, channel and response times
  • Who installs upgrades, and when
  • The licence, price and contract terms
  • Integrations with your ERP, CRM or contact centre
  • Training and documentation for your team

Not built yet

  • Sending email through your own mail server instead of an email sending provider
  • SAML, or an identity provider configured for your organisation (Google and Microsoft accounts already sign in)
  • The MCP layer for AI assistants inside your network: it runs only in our cloud, on managed infrastructure
  • Streaming audit logs into your monitoring system
  • A published installation and operations guide
  • An independent penetration test or a security certification

Why regulated organisations want marketing automation inside their walls

A marketing automation platform holds some of the most sensitive data a company has: who the customers are, what they bought, what they consented to receive, and what they said to an agent or a chatbot. In a bank, an insurer, a health provider or a public body, that data falls under regulation and information-security policy that will not let it move into a vendor's multi-tenant cloud. So those organisations either kept legacy tools or spent years building their own.

An on-premise installation removes that trade-off. The engine that sends a campaign by email and SMS, runs behaviour-based automation, manages deals and tickets in the CRM, and deploys AI agents that talk to customers runs on your infrastructure. Permissions are enforced in the database itself, so one department cannot see another's lists even if someone gets a setting wrong.

AI agents run on your organisation's key with the provider you selected. Every action an agent takes is written to an audit log your security team can read, and every send still needs a person to approve it. If you also need something the platform does not do yet, our custom development team builds it as an extension, alongside your own developers.

When on-premise is the wrong choice

An installation inside your network is a project with an owner. These are the cases where we will recommend the cloud instead.

Nobody will operate the servers

A server inside your network needs someone to back it up, patch it and answer when it fails at night. Without that team, our cloud is safer than an installation nobody owns.

You need to send this week

In our cloud you open an account and send the same day. An on-premise deployment goes through scoping, a security review and integrations, which takes weeks. Start in the cloud and move inside when the project is ready.

The only requirement is EU data residency

If policy only needs the data to stay in Europe, our cloud already does that. On-premise earns its cost when data may not leave your network at all.

Related: EmailPro email marketing · CRM · AI agents · AI assistants over MCP · how the mail layer works · email security · data sovereignty

Clear answers

On-premise installation: questions from IT and security teams

Plan the installation for your organisation

A scoping call with the people who build the platform, and a written requirements document at the end of it. No commitment.

Book a scoping call