Platforms
Own the stack your mission runs on.
Seven sovereign platforms. One foundation. Zero external dependencies. Deployed on your metal, in your cloud, or behind your air gap — and operable by your people without anyone's permission, including ours.
Built for ownership
In high-stakes environments, renting the foundation is a risk decision someone else gets to revisit annually. Wilkes & Liberty builds sovereign technology platforms for organizations where ownership is not optional: no hyperscaler dependency, no commercial SaaS license required to function, no shared-tenant risk. Each platform stands alone; together they form a coherent stack — because they were built together, run together, and are sold by the people who operate them in production every day.
The Foundation
Everything below the stack is yours too.
Keystone · Sovereign Infrastructure
Provisions, deploys, segments, backs up, and operates the entire environment. The complete sovereign suite, and the substrate every other platform runs on. Explore Keystone →
The Planes
Three platforms that touch everything.
Paladin · Zero-Trust Identity
Every request, human or machine, passes here (NIST SP 800-207). Explore Paladin →
Atlas · Observability
Sees every layer; telemetry never leaves the boundary. Explore Atlas →
Anvil · Software Factory
Builds and ships everything, with SBOM and build provenance. Explore Anvil →
The Mission Surfaces
What your teams touch every day.
Chronicle · Enterprise CMS
Content management, governance, and delivery, with a governed AI write-plane. Explore Chronicle →
Memento · Knowledge & Data
Answers, not document lists; the Manifest data layer underneath. Explore Memento →
Horizon · Market & World Intelligence
The world's signals, structured into decisions. Explore Horizon →
The AI Stack
The brains, the rules, the memory. The memory lives in Memento's Manifest layer; the working example of all three composed is Chronicle's governed write-plane.
Helios · Private AI / LLM
Your models, inside your boundary. Explore Helios →
Sentinel · Enterprise AI Governance
Policy as an enforced control plane; shipping today as Sentinel for Drupal (open source). Explore Sentinel →
The path of a request
Keystone provides the ground. Paladin verifies who's asking — person or machine — against least-privilege policy. The request lands on a mission surface: Chronicle for content, Memento for knowledge, Horizon for intelligence. Atlas watches the whole exchange, and every component involved was built and shipped through Anvil. One stack, one discipline.
The AI thread
Helios supplies the brains — private models that never see the public internet. Memento's Manifest layer supplies the memory — what an agent knew, decided, and did, in storage you own. Sentinel supplies the rules — what any agent may read, write, or never touch, enforced at the system of record. And Chronicle is where agents already do real work: governed, logged, revocable, with publish authority reserved for accountable humans. This isn't an AI roadmap; the pattern is in production today.
Proven on our own estate
We do not sell architecture we do not run. wilkesliberty.com — the page you are reading — is delivered by this stack: Chronicle managing the content, Paladin holding the identity perimeter, Atlas watching it, Anvil shipping it, Keystone underneath it all, self-hosted on infrastructure we control with no third-party platform in the critical path. When we describe a deployment model, we are describing our operating reality.
Common questions
No. Each platform is independently valuable and deploys alone. The stack is a composition, not a bundle — start where the mission pressure is and compose from there.
Yes — that is a design constraint, not a feature tier. Every platform deploys and functions inside a disconnected enclave.
Your team, by design: everything is defined in Infrastructure-as-Code and deployable from version-controlled source. We implement and sustain through our capability engagements; we don't hold your keys.
Shipping today. Sentinel for Drupal — mcp_sentinel plus the Drupal MCP Connector — is open source and governs the AI content operations on this very site.
Sovereignty is a design constraint, not a feature.
Tell us which layer the mission is bleeding at — we'll show you the deployment path.