the whole system, visible at once
Systems fail at their boundaries. holos dissolves those boundaries entirely — treating infrastructure, application code, configuration, and deployment as facets of a single coherent volume. When you can see the whole architecture at once, edge-lit and transparent, the pathologies of fragmentation become impossible.
Every component exists as a transparent volume in an isometric space. Kubernetes manifests, Helm charts, CUE definitions, platform configurations — these are not files in directories. They are facets of a three-dimensional model that can be rotated, inspected, and understood as a unified whole.
package holos
// Define the whole system as one volume
Platform: {
Components: [...#Component]
Resources: [...#Resource]
Topology: #Topology
}
#Component: {
name: string
layer: "platform" | "application"
rendered: #Manifest
}
The rendering pipeline transforms abstract definitions into concrete artifacts. Like a holographic display reconstructing a three-dimensional image from interference patterns, holos takes your declarative specifications and projects them into fully-realized Kubernetes resources — every dependency resolved, every configuration unified.
A single entry point into the entire system. No context-switching between tools, no manual orchestration across boundaries. holos presents one surface that encompasses the complete architecture — from cluster topology to application routing, from secrets management to observability pipelines.
The topology view renders every relationship, every dependency, every flow — simultaneously visible in isometric space. Not a flat diagram but a volumetric model where infrastructure layers, service meshes, and data flows exist as transparent overlapping geometries that can be comprehended at a glance.
the whole is visible
holos.dev