Skip to content

Run the Forge on your own infrastructure

The Forge is TOVIO's collaboration server. It hosts repositories, runs the proposal and review workflow, coordinates locks and AI-agent sessions, delivers webhooks, and serves as the synchronization point your team pushes to and pulls from. It runs inside your own perimeter, with no dependency on any TOVIO-operated service.

The operator documentation is entitled, not public

The Forge is licensed LicenseRef-TOVIO-Commercial, and its binary is distributed through an entitled channel rather than a public download. Running it on your own infrastructure is a dedicated-enterprise deployment under a commercial agreement.

The guides for operating it — deployment, day-two administration, the Key Authority, identity federation, org governance, scaling and HA, and hardening — are served to customers under that agreement rather than published here. If you hold an agreement, your operator documentation is at enterprise.docs.tovio.dev, reached with the identity TOVIO added to your account. If you believe you should have access and do not, contact your TOVIO representative.

You may not need the Forge

The Apache-2.0 engine, CLI, and SDKs carry no commercial requirement, and they are documented in full on this site. In particular, tovio serve gives you networked version control with cryptographic per-file permissions — clone, push, pull, and sync over real TLS — without the collaboration platform and without an agreement. See the free-tier answer in the FAQ for what it is and where to be deliberate about running it.

What tovio serve does not give you is the Forge edge: proposals and review, lane protection, the connection ACL, required checks, webhooks, and lock coordination. Lane protection, required checks, and the connection ACL are server-enforced write-side gates; the rest are the delivery and coordination surfaces around them, and together they are what the commercial product adds.

Locking is the one to read precisely. The Forge arbitrates who holds a lock, breaks a stuck one, and audits both — but no push or land path consults the lock store, so a lock held by someone else does not yet refuse a write. The refusal that does ship is holder-agnostic and client-side, in the Apache-2.0 CLI: a divergent edit to a path declared exclusive-lockable is refused at land, because a binary cannot merge into a conflict.

The permission model is not what you are buying

Confidentiality does not come from the server in either case. A protected file is encrypted on the client before it is ever pushed, so a Forge — hosted or self-run — receives ciphertext for protected payloads and never needs recipient private keys or unwrapped DEKs merely to host them. The Forge is a distribution and coordination layer; authorization to read is a property of keys held by identities. That model is public, and it is described in the security overview.

Where this connects

Last reviewed September 9, 2026

Suggest an improvement to this page Not for security reports — see disclosure