Skip to content
Madsoft
← All capabilities
07Cloud, Data & Infrastructure

Infrastructure you own, and can point at

sovereign

For organisations that cannot put their data on somebody else's platform — for cost, for sovereignty, or because procurement says so — and need it run properly rather than handed over as a box.

01How we work

Sovereignty is an operational question

The real question is not where a server sits on a map; it is who you can call at two in the morning, what happens to your data if a contract ends, and whether you could move it next quarter if you had to. We answer those three in writing before choosing anything, and the answer sometimes is a hosted platform.

Mail is infrastructure, and it is the hard one

Self-hosted mail is where most sovereignty projects quietly fail, because delivery is unforgiving: SPF, DKIM, DMARC, reverse DNS, warm-up and reputation all have to be right or your invoices land in spam. We deploy it end to end, prove delivery to the major providers, and hand over the runbook for the day a record changes.

Reproducible, monitored, and recoverable

Containerised deployment with migrations that run the same way every time, backups that are restored on a schedule rather than assumed, monitoring that pages a person, and documented recovery. A backup nobody has restored is a belief, not a backup.

02What this covers
  • Server provisioning, hardening and TLS
  • Containerised deployment and CI pipelines
  • Self-hosted mail with SPF, DKIM and DMARC
  • Database design, backups and monitoring
03What you are handed
  1. 01Provisioned, hardened servers with TLS and a documented firewall
  2. 02Containerised deployment and a CI pipeline you can run
  3. 03Mail with SPF, DKIM, DMARC and verified delivery
  4. 04Backups with a tested restore, monitoring and a runbook
04Recognisable by
  • Data residency is a procurement requirement you cannot currently meet

  • Your platform costs scale with success rather than with use

  • Nobody has restored a backup, and nobody wants to be the first to try

06Questions we are asked

Do you host it for us or do we?

Either, and the accounts are yours in both cases. Where we operate it, the arrangement is one you can end: the runbooks, credentials and infrastructure are already in your name, so leaving is a notice period rather than a migration project.

Can you work with our cloud provider?

Yes. The same practices apply on a managed platform, and the sovereignty questions get answered in writing either way.

Is self-hosted mail really worth it?

Sometimes not, and we will say so. It is worth it when correspondence cannot sit on a third-party service for procurement or legal reasons, or when per-mailbox pricing has become the budget. It is not worth it to save a small amount of money, because deliverability is a standing obligation.

What about disaster recovery?

Backups with a restore tested on a schedule, documented recovery steps, and a recovery time you have agreed rather than discovered. The procurement page sets out what is committed at handover.

Start here

Bring us the problem nobody has solved.

A 30-minute technical briefing. We will tell you what we would build, roughly what it costs, and honestly whether we are the right people for it.