Preview. These maps are our reading of public sources and haven't been checked with the projects' maintainers yet.
Grace
Centralized, cloud-native VCS (Orleans, Azure, Aspire) by a single author: every change stored as an event, 'promotions' instead of merges, continuous AI-assisted review, built for agents and very large repos.
Alpha; last push 2026-09-11 (GitHub API); README says 'not ready for or intended for production usage'. (checked 2026-10-25)
In Version control beyond git
Where it stands apart
- How is it mainly sustained? individual side project, no revenue (0% of 16 others)
- How does it relate to git repositories? own storage format, one-time import or no git interop (21% of 19 others)
- Can you commit, branch, and read history with no network connection? no (0% of 17 others)
- Is it designed with AI coding agents in mind? yes, agents are a primary design target (20% of 20 others)
- Which layer of the stack does it mainly replace? version control and hosting together, as one system (15% of 20 others)
- What is the basic unit of history? (pick the most specific that applies) fine-grained operations or events (5% of 19 others)
- How are merge conflicts mainly handled? avoided or resolved automatically by default (CRDTs or merge rules) (6% of 17 others)
- What size of project is it designed for? very large monorepos or large binary assets (21% of 19 others)
What it shares with most of the community
- Is it actively maintained? active (90% of 20 others)
- How is the main thing licensed? permissive open source (MIT/Apache/BSD) (53% of 19 others)
- Can it run entirely on your own device or infrastructure, without the maker's servers? yes (79% of 19 others)
- Do you need an account to use it? no account (67% of 18 others)
- Who is it for? developers (90% of 20 others)
Not documented
The public sources we read don't say:
- Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow?
Nearest neighbors
- DeltaDB (Zed) 86% of 7 shared answers match
- Sturdy 54% of 13 shared answers match
- Lore (Epic Games) 50% of 16 shared answers match
Every answer
| Question | Answer | Source |
|---|---|---|
| Is it actively maintained? | active Pushes in Sept 2026 but alpha; one main author. | source 2026-10-25 |
| How is the main thing licensed? | permissive open source (MIT/Apache/BSD) MIT (GitHub API). | source 2026-10-25 |
| How is it mainly sustained? | stands apart individual side project, no revenue Alpha, single author; no pricing, sponsors or funding found. | source 2026-10-26 |
| Can it run entirely on your own device or infrastructure, without the maker's servers? | yes Aspire supports local deployment of the server; depends on Azure services in the cloud. | source 2026-10-25 |
| Do you need an account to use it? | no account You run your own Grace Server; no maker-hosted account. | source 2026-10-26 |
| Who is it for? | developers | source 2026-10-25 |
| Which shared standard or format does it mainly build on? | none of these (its own format or interface) Own event-sourced store; no git interop. | source 2026-10-26 |
| How does it relate to git repositories? | stands apart own storage format, one-time import or no git interop Can share a working directory with git (.grace ignored by git), but no git interop. | source 2026-10-25 |
| Where does the authoritative copy of a project live? | one central server per project (hosted or self-hosted) | source 2026-10-25 |
| Can you commit, branch, and read history with no network connection? | stands apart no Centralized; a 'grace cache' mirror is on the roadmap, not built. | source 2026-10-25 |
| Is it designed with AI coding agents in mind? | stands apart yes, agents are a primary design target 'grace agent bootstrap'; captures agent prompts, specs, and model versions for review. | source 2026-10-25 |
| Which layer of the stack does it mainly replace? | stands apart version control and hosting together, as one system | source 2026-10-25 |
| What is the basic unit of history? (pick the most specific that applies) | stands apart fine-grained operations or events Event-sourced saves, checkpoints, commits, and promotions. | source 2026-10-25 |
| Are stacked changes (a chain of dependent changes reviewed separately) a first-class workflow? | Not documented | source 2026-10-25 |
| How are merge conflicts mainly handled? | stands apart avoided or resolved automatically by default (CRDTs or merge rules) Promotion conflicts resolved automatically by rules and confidence levels. | source 2026-10-25 |
| What size of project is it designed for? | stands apart very large monorepos or large binary assets | source 2026-10-25 |
| Is code review part of the product? | yes, it has its own review interface Continuous review with deterministic checks and AI prompts, promotion queues and gates. | source 2026-10-25 |
Sources
This page was derived from:
- GitHub · github.com/ScottArbeit/Grace · read 2026-10-25
- GitHub · raw.githubusercontent.com/ScottArbeit/Grace/main/README.md · read 2026-10-25
RSS for this project · Its own release feed
Are you a maintainer? Claiming and correcting projects is coming soon.