system.console — engineering deck

whole systems, rendered visible.

holos.dev is a development surface for holistic system design — a single interface to observe, traverse, and reshape architectures from microservices to monoliths. No marketing gloss. No friendly abstractions. Just the topology, exposed.

latency 04.7ms
edges 28
depth L4 / L7
// system.map x:000 y:000
service boundary passive

primitives

02 / 04
// 01.topology

Topology Synthesis

Static and runtime sources fold into a single graph. Each node preserves its provenance trace; each edge carries its protocol envelope. Nothing inferred is unsourced.

graph.depthunbounded
// 02.boundary

Boundary Inspection

Every interface is a contract. holos.dev surfaces the raw protocol surface of each boundary — schemas, error envelopes, retry posture, idempotency keys — with no editorial layer.

protocolshttp · grpc · ws · amqp
// 03.signals

Signal Channel

Telemetry overlaid directly onto the topology — saturation, error rate, p99, queue depth. Signals are not aggregated into vanity scores. Each channel can be read in its native shape.

resolution1s · 100ms ringbuffer
// 04.lineage

Causal Lineage

Trace every event from origin to outcome — across asynchronous boundaries, replays, and partial failures. The lineage is a first-class object you can query, fork, and compare.

horizon30d retained, infinite addressable

live diagram

03 / 04
drag to reposition · hover to inspect · click to pin
node.— idle
kind
protocol
p99
edges