Runtime
The open-source runtime layer — and the foundation the whole stack runs on.
The runtime layer of the stack, and its open-source foundation (MPL 2.0). Runs autonomous workloads across cloud, edge, on-device, and on-robot — with first-class awareness of tokens, models, memory, and embodiment, routing over open-weight models so cognition stays in your walls.
Lattice Runtime is a primitive of the Visca stack — it ships with the stack, versions with the stack, and audits with the stack. It is not separately purchasable.
What it is
Lattice Runtime is where autonomous actors execute, on compute you control — and it is the open-source foundation the rest of the stack is built on. It is the wedge: anyone can read it, fork it, and run the full substrate inside their own walls under MPL 2.0, with no accounts, no telemetry, and nothing calling home. It schedules, runs, and supervises actors across heterogeneous compute with awareness of the dimensions that distinguish autonomous workloads from generic ones: token budgets, model availability, tool dependencies, memory lifecycle, latency objectives, embodiment constraints. Every actor runs under its Sigil, a budget, a model routing policy, a memory binding, and a safety envelope — and every execution is recorded to Chronicle. Model routing favors open weights in-perimeter, so inference need not leave your boundary. Built on durable execution: when a process crashes, work resumes from the last checkpoint — state is never lost.
The problem
Generic schedulers are blind to the dimensions that determine whether an autonomous workload succeeds. Kubernetes does not understand token budgets. Lambda does not understand provider fallback. Robotics middleware does not understand cost ceilings. Operators are left running autonomous workloads on infrastructure designed for stateless requests, with autonomy-specific concerns built into application code, inconsistently, across every team — and routed out to hosted model APIs that send regulated data straight past the perimeter.
Capabilities
Open and commercial
Lattice Runtime has two surfaces: an open-source reference in Lattice Runtime (MPL 2.0), and a managed delivery as part of the Visca stack on Visca Cloud. Features in the open never move behind the paywall.
Open
MPL 2.0 · self-hostable · foundation-track governance
Commercial
Your tenancy · dedicated · self-managed · air-gapped
LIFECYCLE · same plane
The data-model layer of the self-hosted stack.
The data-model primitive of the stack, run inside your perimeter. Declare what should exist as versioned source; agents write it as source, humans edit it as a spreadsheet. Plan, apply, drift-detect — all against state that stays in your tenancy.
The packaging layer of the self-hosted stack.
The packaging primitive of the stack, run inside your perimeter. Immutable, content-addressed, Sigil-signed bundles — everything an autonomous actor needs to execute, packaged as a single attestable artifact and registered in your own registry.
The build surface — for humans and agents.
Where humans and agents build autonomous systems. CLI, SDKs, local runtime, eval harness, replay, documentation, templates — and an agent-facing surface so agents can author, evaluate, and ship other agents.
Across the stack
The identity layer of the self-hosted stack.
The identity primitive of the stack, run inside your perimeter. Issues, verifies, and revokes the cryptographic identity every autonomous actor holds — bound to principal, runtime, and lineage from the moment of instantiation. The one identity every other primitive trusts.
The authority layer of the self-hosted stack.
The authority primitive of the stack, run inside your perimeter. Brokers every access from an autonomous actor to a consequential resource against its Sigil — identity-bound, scoped, time-limited, and recorded to Chronicle. Long-lived credentials disappear.
The fabric layer of the self-hosted stack.
The fabric primitive of the stack, run inside your perimeter. Discovery, mTLS, and routing across every autonomous actor and every resource an actor reaches — rooted in the same Sigil identities, not hardcoded URLs, and never crossing your boundary.
The record layer of the self-hosted stack.
The record primitive of the stack, run inside your perimeter. The one audit trail every other primitive writes to — a queryable knowledge graph of every actor, plus the append-only, cryptographically chained log of every action, keyed to Sigil and Capability Grant.
The whole stack. Self-hosted. One ecosystem.
Models, identity, tools, voice, payments, runtime, and audit — as one integrated ecosystem, self-hosted, sovereign, air-gapped. Nothing stitched from vendors. Nothing leaves your perimeter. Open at the core. No license rug-pulls, ever.