The infrastructure foundation for estates you own. Provisioning, segmentation, backup, and operations run on premises, self-hosted, or hybrid. No external control plane sits in the critical path.
What Keystone is
Keystone is the substrate other Wilkes & Liberty platforms run on. Your organization owns the foundation and the materials needed to operate it.
What you get
Provisioning and configuration as code. Network segmentation inside your boundary. Backup and restore under your team's control.
Where it runs
On premises, self-hosted, or hybrid, as the work requires. Public surfaces sit on a defined ingress. Internal systems do not depend on a third-party management plane. An air-gapped estate or a Linux host is a delivery choice when the work requires it.
Boundary
Keystone composes Anvil for software delivery, Atlas for observability and intelligence, and Paladin for identity and access. Each platform retains its own role.
What you keep
Documentation, infrastructure-as-code, tests, and runbooks your team operates.
Start with the estate
Choose Keystone when your priority is an infrastructure foundation your team can operate. Bring the environment boundaries, ownership requirements, and handoff expectations to the readiness assessment.
The practice behind this platform
Private Infrastructure is the practice behind Keystone.
Mission impact
Your organization keeps authority over the infrastructure its mission depends on. Keystone brings the foundation into an estate you control. The operating knowledge transfers with it.
Key capabilities
Provisioning as code
Stand up and converge the estate from version-controlled source.
Segmentation inside your boundary
Network and environment boundaries your operators control.
Backup and restore
Backup and restore under your team's control.
Defined ingress
Public surfaces meet the estate at a defined ingress.
Customer-operated
Documentation, IaC, tests, and runbooks transfer at close.