Federal Frontier vs Komodor Klaudia
Our stack first — FFO, Warrant, Remuda, local-first, posse/SME catalog — with commercial K8s assistants as a comparison point, not the design north star.
Audience: operators and stakeholders comparing commercial K8s assistants to the Federal Frontier SRE stack.
This page leads with our architecture. Commercial products (including Komodor Klaudia) are useful reference points for operator expectations; they are not the design north star.
Federal Frontier architecture (lead)
| Pillar | Role |
|---|---|
| Investigator | ONE opencode-runner Job for unknown alerts (local scout -> quality gate -> Opus escalate) |
| SME catalog | Platform specialists: named Remuda harness shapes (playbooks), not separate binaries |
| Posse roles | Scout / Sage / Wrangler / Marshal productized onto Remuda tool slices and prompts |
| Remuda (MCP) | Product MCP registry/router (Wanaku engine); Investigator selects the SME namespace slice |
| FFO | TypeDB facility graph for topology and remediation scope |
| Warrant / FAS | Statute-backed risk and authz before remediation |
| Local-first | Gemma hot path on-prem; Bedrock Opus cold path with transcript |
The Investigator routes alerts to SMEs from the catalog. Maturity (ga / lab /
planned) is honest roadmap depth for each specialist - the inventory is the
platform roadmap made visible, not a marketing headcount.
See ADR-033 (harness shaping) and /docs/sre/sme-catalog/.
Where commercial assistants typically differ
Klaudia-class products often optimize for SaaS multi-cluster K8s UX, vendor-hosted correlation, and a large packaged playbook library in public-cloud environments.
Federal Frontier optimizes for sovereignty, facility truth (FFO), Remuda MCP on FMC, Warrant authz, and local-first inference - constraints that define the product shape.
| Concern | Federal Frontier |
|---|---|
| Air-gap / sovereignty | Local Gemma scout; cloud only on quality-gate miss |
| AuthZ | Warrant PEP + FAS / Keycloak OIDC on Remuda |
| Facility truth | FFO TypeDB, not events alone |
| Tool plane | Remuda namespace slices per SME |
| Runtime model | One Investigator; catalog grows as playbook + Remuda entries |
What we do not claim
- Drop-in UI parity with any commercial assistant.
- That every
plannedSME already has a dedicated Remuda tool pack online. - That maturity badges are a substitute for lab verification.
Grow the catalog by wiring Remuda tools and classifiers - the Investigator stays one image.
Eupraxia Labs · Federal Frontier · Platform docs