Version control for continuous human and agent work.
Fervion records work continuously, then lets you promote what should become history — one accountable place to change state without overwriting anyone else's work.
Early system. No spam. We will only email about beta access and product updates.
The beta is for people exploring version control beyond Git ceremony.
Fervion is early. The best testers are builders who care about API-first workflows, continuous history, scoped visibility, offline tradeoffs, and auditable agent output.
Good fit for
- Developers experimenting with AI-generated or automated changes.
- Tool builders who want version-control primitives exposed as APIs.
- People who care about reviewable history more than perfect Git compatibility.
- Teams exploring private, team, and public visibility boundaries.
- Builders willing to test early workflows and report sharp feedback.
Not trying to replace yet
- Every Git hosting workflow on day one.
- General semantic merge resolution.
- Production-grade binary coordination and soft-locking.
- Claims that revocation can recall already materialized copies.
- Public promotion without explicit review gates.
- Browser workflows that depend on local filesystem access.
Git assumes local filesystems. Fervion starts from storage primitives.
Fervion separates immutable objects and snapshots from mutable refs, raw logs, and curated history. Each reference change validates against expected version token, so stale agents can't overwrite state — you review, undo, promote explicitly.
Raw work becomes reviewable history
Record saves, snapshots, and agent activity continuously as it happens.
No silent overwrites
Prevent stale clients and automated systems from clobbering each other's changes.
Every agent action has an owner
Trace agent tasks and model/version context back to the triggering user.
Capture first. Curate later. Promote deliberately.
Fervion is designed around a different workflow: raw work is cheap and automatic, semantic history is intentional, and promotion across visibility scopes is explicit.
1. Work through the API
CLI, browser clients, serverless systems, and agents use the same storage primitives. The filesystem can exist as a materialized view, but it is not the foundation.
2. Store immutable snapshots
Objects and snapshots are content-addressed records. Once written, they do not change, which makes caching, syncing, and review easier to reason about.
3. Move refs with version tokens
Refs point at snapshots and move only through expected-version checks. When state has changed, clients must reconcile instead of overwriting another actor’s work.
4. Turn raw activity into semantic history
Raw logs preserve reality. Semantic entries group that activity into useful human-readable history for review, undo, and promotion.
Questions before joining
Help shape version control for continuous, agent-era work.
Join if you want to test an API-first VCS built around immutable snapshots, scoped visibility, explicit promotion, and auditable actors.
No spam. Only beta access and product updates.