About
Infrastructure organized around identity-aware calls.
Dodona is an early application substrate that connects service naming, workload identity, delegated authority, execution, and audit.
The name
A literal place to ask what exists and what is permitted.
Dodona was the oldest Hellenic oracle: a place to ask where to go and what was permitted.
The product name is Dodona; the command is `dona`. The metaphor stops there. The system itself is concrete: resolve a name, prove the peer, authorize the call, run the workload, record the decision.
FAQ
Direct questions, direct boundaries.
Why not just use k3s?
k3s is a mature, lightweight Kubernetes distribution and is the direct choice when the Kubernetes operating model and ecosystem are the goal. Dodona starts from a different operating model: names, workload identity, delegated authority, execution, and audit share one object model; Kubernetes is an optional view. This is a fit distinction, not a superiority claim.
What came from Vanadium?
Dodona retains useful Vanadium ideas around hierarchical naming, authority concepts, and identity-aware resolution while using gRPC, TLS, and current ecosystem tooling rather than Vanadium’s custom wire stack. This is lineage, not affiliation or compatibility.
Is the Directory a hosted product?
No public hosted Directory fleet exists. Relay, connector, delegation, and MCP gateway flows have implemented local evidence. Hosted operations and design-partner deployment remain early-access work.
Is Dodona Kubernetes certified?
No. One local two-node rig passed all 408 tests selected by the official Kubernetes v1.31.14 `[Conformance]` run. That is pinned local evidence, not CNCF or cloud-provider certification and not evidence for later minors.
Does this site run on Dodona?
Yes. The 2026-07-16 launch deploys the built static artifact as service `dodona.www` and routes `dodona.dev` and `www.dodona.dev` through Dodona ingress. Deployment provenance and rollback are recorded in the website runbook.
Go deeper
The engineering showcase remains separate.
Architecture tours, subsystem detail, and current implementation evidence live at the engineering deep-dive and documentation sites.
Next step
Early access starts with a concrete workload or agent call.
There is no generic signup funnel yet. Ask the person who shared this site to arrange a signed checkpoint and a scoped evaluation.