The Factory
A Visca factory can plan, build, deploy, and maintain software because identity, credentials, runtime, audit, and resident operators were designed as one system. It runs inside the institution's network, under its controls, with one record from objective to operation.
Factory film · coming soon
An early preview of Visca planning, building, verifying, approving, deploying, and maintaining software inside an institution's network.
Objective
Intent enters with constraints.
These are not point products. They are the structural controls that let an autonomous factory work inside a regulated institution.
Identity
Every agent is a first-class identity with a recorded human sponsor — not an API key taped to a service account. Delegation chains stay intact: which human authorized which agent to act, all the way down. When a security team asks who did this, the answer is a principal, not a guess.
Credentials
Authority is granted, never assumed: scoped, short-lived credentials that map to exactly what the agent may do. Grants are proposed, reviewed, signed, and revocable. Least privilege is the default state, not an aspiration in a policy document.
Runtime
Governed execution inside the perimeter. Every model call and tool call passes through one gateway, under the agent's identity and scopes — so what an agent can reach is decided by policy, enforced at the chokepoint, and visible after the fact.
Audit
One tamper-evident ledger across the whole stack. Every action — by product agents, by operators, by humans — lands signed, attributed, and queryable. This is the document your security team actually reads, generated as a by-product of how the stack works.
The operators
The stack ships with its own operators: agents that deploy, upgrade, patch, rotate credentials, and answer incidents — inside the perimeter, under the same identity, credentials, and ledger as everything else. Self-hosted, without the ops burden that always came with it.
Identity roots credentials. Credentials bound the runtime. The runtime feeds the ledger. The operators run on all four. Stitch the equivalent from separate vendors and every seam is a contract, a breach surface, and a review that never ends. Adopt the stack, and the seams disappear — along with the questions about them.
Install an autonomous software factory that plans, builds, tests, deploys, and maintains software inside your network, under your controls.