About

Operating sovereign backup infrastructure since 2013.

We were founded by a small group of operators who had spent the previous decade running storage and recovery teams inside regulated banks, hospitals, and a national grid operator. We started Local Datacenter because we wanted to deliver the operational standards we had been held to as customers — and to do it without the leverage of public-cloud lock-in.

Mission

To make immutable, jurisdiction-stable backup the default for organisations that cannot afford a bad recovery — without forcing them onto infrastructure they do not control.

How we operate

Three regional datacenters, two of them owned facilities and one a long-term colocation contract with an audited tier-III provider. Replication is engineered between sites at the storage layer; we do not depend on a single SAN vendor or hypervisor for cross-site durability.

Every customer is assigned a named primary and secondary engineer who handle onboarding, runbooks, and recovery rehearsals. Tickets exist for tracking, not as the relationship.

Engineering principles

  • Restore is the product. A backup that has not been restored within 90 days is treated as untested. We test on a schedule, not on incident.
  • Erasure is a feature. Retention floors are enforced cryptographically; retention ceilings are enforced operationally. Both are auditable.
  • Vendors are replaceable. No single vendor — including ourselves — should be the only path to a customer's data.
  • Plain language contracts. SLAs say what they mean. RPO, RTO, and durability targets are all numbers, not adjectives.

Leadership

Our leadership team carries combined operational experience across central banking infrastructure, electronic health record systems, transmission-grid SCADA networks, and large-scale tape archives. Biographies are available under NDA to evaluating customers.

2013
Founded
62
Engineers and operators
3
Regional datacenters
240+
Active enterprise customers

Want to know who would actually own your account?

Most evaluation calls end with a 30-minute introduction to the engineering team that would run your environment.

Schedule an introduction