Aspen
A self-hostable Git server for agent-scale traffic that stores packs in object storage and per-branch history in PostgreSQL.
At a Glance
Aspen self-hostable Git server under Apache License 2.0; pre-alpha with no published releases. Self-hosting infrastructure (PostgreSQL, object storage) is an external cost.
Engagement
Available On
Alternatives
Listed Nov 2026
About Aspen
Aspen is an open-source Git server from Reason Machines, built for repositories that hundreds of agents, CI jobs and people push to and fetch from at the same time. It speaks plain Git over HTTP and SSH, so stock git works without client changes. It is labeled pre-alpha and has no published releases, and a live demo called place runs a shared pixel canvas where every pixel is a git push.
What It Is
Aspen is a Git server you run yourself. Packs are stored in object storage (S3-compatible stores or a local file system), and branch history lives in PostgreSQL, or SQLite on a single machine. It can run as one binary on one machine or on any cloud, and a mirror mode can sit in front of GitHub or GitLab over HTTP(S) so it can be tried without migrating.
How the Design Works
Each branch moves independently through a compare-and-swap on its tip, so pushes to different branches do not wait on each other. Pushed packs are checked, completed into self-contained packs and kept as immutable objects, then reused to answer fetches. Fetches stream the stored packs a client is missing or hand out packfile URIs for a CDN or pack cache. Small packs are merged in the background in levels, like an LSM tree. The README says the design follows OpenAI's Pando write-up and draws on Cursor's Origin write-up, and it describes Aspen as an independent implementation.
Setup Path
There are no published binaries, so Aspen is built from source with a Rust toolchain and a C compiler. aspen dev runs the whole server in one process with SQLite and a local pack directory, listening on 127.0.0.1:7070. Further options in the README are token-based auth with aspen serve, a Docker Compose stack with PostgreSQL and MinIO, and Helm or Terraform deployments for AWS, Google Cloud, Azure and Hetzner.
Current Status and Known Limits
The README marks Aspen as pre-alpha, says storage formats may still change, and warns against storing data you cannot afford to lose. Documented limits include no partial clones, no SHA-256 repositories, no web UI, code review or issues, SSH support only for Ed25519 and ECDSA keys, and no Azure Blob Storage support yet. Force pushes and branch deletes need -o force, a lease or the branch-scoped URL. The performance figures in the README, such as 567 pushes a second on one 8-core server, come from the project's launch post and the README calls them indicative.
Community Discussions
Be the first to start a conversation about Aspen
Share your experience with Aspen, ask questions, or help others learn from your insights.
Pricing
Open Source (Self-Hosted)
Aspen self-hostable Git server under Apache License 2.0; pre-alpha with no published releases. Self-hosting infrastructure (PostgreSQL, object storage) is an external cost.
- Licensed under Apache License 2.0
- Self-hosted Git server over HTTP and SSH
- Packs in object storage, branch history in PostgreSQL
- Runs on one machine or any cloud (Docker Compose, Helm, Terraform)
- Status: pre-alpha, no published releases
Capabilities
Key Features
- Plain Git over HTTP and SSH with stock git clients
- Per-branch compare-and-swap pushes with no repository-wide lock
- Packs stored in S3-compatible object storage or a local directory
- Branch metadata in PostgreSQL or SQLite
- Fetch via stitched packs or packfile-uri links to a CDN or pack cache
- Background LSM-style pack compaction
- Mirror mode in front of GitHub or GitLab
- Optional server-side merge queue and group commit
- Token, OIDC and SSH key authentication
- Single-process dev server via `aspen dev`
- Deployment via Docker Compose, Helm and Terraform
