Where Perforce is native today
- Native large binaries (no add-on) — also a TOVIO v1 design target
- Path-scoped partial checkout — also a TOVIO v1 design target
Comparison · Perforce
Perforce vs Git vs TOVIO
Perforce is a centralized version control system long used for very large repositories and binary-heavy work such as games and media. Here is how it compares with Git and with TOVIO's design, row by row.
How to read this
native / first-class partial or workaround not supported
Perforce and Git cells reflect a 2026 snapshot of each tool's publicly documented behavior and will change as those projects evolve; where another system genuinely leads a row, the table shows it. TOVIO cells reflect the v1 design target — TOVIO is pre-1.0, unpublished, and not yet independently audited. See the launch gates and what ships today for current implementation status.
Against the tools most teams run today
$against the tools most teams run today2026 snapshot · TOVIO = v1 design target
| Capability | Perforce | Git | TOVIO |
|---|---|---|---|
| Offline-first, fully distributed | Not supported | Native or first-class | Native or first-class |
| Per-file cryptographic permissions | Partial or workaround | Not supported | Native or first-class |
| AI-agent capability tokens + provenance | Not supported | Not supported | Native or first-class |
| Change-centric identity (survives rewriting) | Not supported | Not supported | Native or first-class |
| First-class conflict objects | Not supported | Not supported | Native or first-class |
| Native large binaries (no add-on) | Native or first-class | Not supported | Native or first-class |
| Path-scoped partial checkout | Native or first-class | Partial or workaround | Native or first-class |
| Full operation log / undo-anything | Not supported | Partial or workaround | Native or first-class |
| Semantic diff & behavioral versioning | Not supported | Not supported | Native or first-class |
| Open specification, no vendor lock-in | Not supported | Native or first-class | Native or first-class |
What the rows say
What TOVIO's design adds
- Offline-first, fully distributed — not supported in Perforce
- Per-file cryptographic permissions — partial or a workaround in Perforce
- AI-agent capability tokens + provenance — not supported in Perforce
- Change-centric identity (survives rewriting) — not supported in Perforce
- First-class conflict objects — not supported in Perforce
- Full operation log / undo-anything — not supported in Perforce
- Semantic diff & behavioral versioning — not supported in Perforce
- Open specification, no vendor lock-in — not supported in Perforce