Early access
Capability-scoped agents with provenance on their work, change IDs that survive history rewrites, and cryptographic per-file permissions — one system for how software actually ships now. Scroll to watch a change move through it.
Every agent gets an expiring, delegable token bounded by repository, path, lane, operation and secret clearance. An out-of-scope read is refused before a byte is decrypted, and the work it does carries signed provenance. Scroll to watch a change move through it.
TOVIO reads a change as symbols rather than lines: a semantic diff names the entities that moved, landing checks them against the lane you are merging into, and conflicts survive as data instead of markers. Implemented today; artifacts are not published yet. Scroll to watch a change move through it.
01 · the change model
The working copy auto-snapshots into a chg: — a random, stable id that survives amend, rebase, absorb, and landing.
Why it matters Review threads and automation attach to the work itself, not a commit hash that history keeps throwing away.
02 · permissions
Protected paths are encrypted at snapshot, before they ever hit storage — content keys wrapped only to authorized recipients.
Why it matters An unauthorized clone can hold the entire repository and still hold nothing but ciphertext. Ship code that can't all be public.
03 · agents
Agents get expiring, delegable tokens bounded by repository, path, lane, operation, and secret clearance — a whole fleet on parallel lanes, provenance on their work.
Why it matters Run a fleet of AI agents without handing any of them your keys. An out-of-scope read is refused before a byte is decrypted.
04 · resolve & scale
Merges can produce typed, durable conflict objects; FastCDC gives large binaries the same verified path as source; commit, inspect, and merge with no server.
Why it matters Teams keep moving — no blocked merges, no LFS tax, no hard dependency on being online to be correct.
$ tovio policy show secrets/prod.env
✓ policy · matched secrets/** · read: role=release
$ tovio agent list
◆ claude · branches agent/claude/** · 8h left · clearance=false
$ tovio commit -m "api: paginate /repos"
✓ chg:9fk2m1 · change recorded
$ tovio rebase --onto main
✓ chg:9fk2m1 · id survives the rewrite
$ tovio policy set "secrets/**" --read role=release
✓ sealed · encrypt-at-snapshot to entitled keys
$ tovio cat secrets/prod.env
! ciphertext only · no entitled key present
$ tovio agent new cursor --model claude --task "web ui"
✓ cap_1004c16a · protected paths excluded · no clearance
$ tovio cat config/prod.env
✗ TVO-TOKEN-001 · path outside agent scope
$ tovio land agent/claude agent/cursor
! conflict object · typed, durable, resolvable
$ tovio status --no-sync
✓ local core intact · network optional
Built on guarantees, not adjectives
Release readiness · 2026-08-03 — Phases 0-4 are implementation-complete under their documented profiles. Phase 5 productization, publication, hosted-service, Tier-2 Enterprise, and independent evidence remain in progress.
Where it runs
The local engine, an on-premise Forge, and the evidence-gated commercial control plane speak the same versioned objects and authorization contracts.
The LicenseRef-TOVIO-Commercial Forge runs inside your perimeter under agreement — authenticated sync, proposals, review, locks, audit, and administration, with protected content staying ciphertext at the service boundary.
Read the Forge trust model →Managed hosting, metering, billing, and tenant operations are implemented behind release, hosted-parity, identity, legal, and independent-review gates. Not generally available today.
Inspect the launch gates →Tier-2 cryptography, federation, longer audit retention, dedicated tenancy, and the proposed SLA cannot be sold until the Enterprise evidence and counsel gates pass.
Review the accepted prelaunch catalog →Built for scale
The hosted Forge is edge-native by design, not the on-premise server binary lifted into someone else's datacenter. It runs the same verified engine you run locally — one engine, no fork — distributed across Cloudflare's global network, so collaboration executes nearest the person, or agent, making the request, and capacity scales out with the network instead of with a machine we remembered to provision.
Network figures are Cloudflare's published platform capacity — infrastructure TOVIO Cloud is built to run on, not a measurement of a TOVIO service.
Still gated This is the architecture TOVIO Cloud is built on — not an availability claim. Hosted service stays behind its release, hosted-parity, identity, legal, and independent-review gates, and no infrastructure supplier is contractually appointed while that review is open. Inspect the launch gates →
Start with the real implementation
No artifact is advertised until its checksum, provenance, upgrade, platform, and acceptance evidence is complete. Everything you need to try it is already in the open.
