openscion
Server-centric, Rust-based version control server for agent-heavy monorepos that lands changesets on trunk and serves sparse reads.
At a Glance
Self-hosted openscion server and scn client, dual-licensed under Apache-2.0 or MIT (alpha 0.x).
Engagement
Available On
Listed Nov 2026
About openscion
openscion is an independent, open-source implementation in Rust of the design described in Anthropic's "Redesigning source control" engineering post. It is a server for large monorepos written to mostly by AI agents, landing changesets on the trunk and serving sparse reads. The repository states it is not affiliated with or endorsed by Anthropic and contains no Anthropic code. It is marked alpha (0.x), with a v0.1.0 release.
What It Is
openscion is a version control server that moves the work of history, commits and rebases onto the server instead of the client. Clients send single-parent changesets to existing refs, and import and restore create repos and refs. There is no client branch or merge flow yet. Metadata is stored in PostgreSQL, and file contents go to a data directory.
How the Land Workflow Works
A changeset lists only the files that changed, and files and trees are stored once by BLAKE3 content hash. When an agent lands a changeset, the server replays it onto the newest main and moves main with a single compare-and-swap, provided none of the changeset's paths changed on main since its base. If a path did change, the land reports a conflict and prints the paths, and retrying the same land returns the first result. The agent loop uses three commands: scn cat to read a file without cloning, scn commit to create a changeset, and scn land to rebase onto main and move it. Every command accepts --json.
Components and Setup
The project ships scion-server (storage, commits, lands, reads, git import, fsck, gc, backup and restore), the scn command-line client (read, sparse checkout, experimental read-only NFS mount, commit, land, diff, log, blame), scion-cache as a regional read cache, and scion-daemon as a per-machine cache on a Unix socket. Building needs Rust 1.88+ and protoc, plus Docker or your own PostgreSQL 16-18 server. Git repositories can be imported into the server.
Current Status
The README describes the project as alpha, running as one server process on one machine, and not ready for production code yet. Linux on x86-64 and macOS on Apple Silicon are supported, Linux on arm64 is best effort, and Windows is not supported.
Community Discussions
Be the first to start a conversation about openscion
Share your experience with openscion, ask questions, or help others learn from your insights.
Pricing
Open Source
Self-hosted openscion server and scn client, dual-licensed under Apache-2.0 or MIT (alpha 0.x).
- Licensed under either Apache License 2.0 or MIT license at your option
- Self-hosted: requires your own PostgreSQL 16-18 server and data directory
- Alpha (0.x): one server process on one machine, not ready for production
- Independent implementation, not affiliated with Anthropic
Capabilities
Key Features
- Server-side commits, rebases and landing of changesets
- Sparse reads and sparse checkouts
- Content-addressed storage using BLAKE3
- Compare-and-swap move of main on land
- Conflict detection with path reporting
- Idempotent land retries
- Git repository import
- Regional read cache and per-machine daemon cache
- gRPC API
- JSON output for all scn commands
- Backup, restore, fsck and gc
- Experimental read-only NFS mount
