Dengel documentation
Dengel hosts Git repositories in the EU and gives teams a way to review changes made by people and coding agents before those changes reach the shared branch.
Choose what you want to do
- Start free: create an account, verify your email, and create or join a workspace.
- Push your first Git change: create a repository, clone it over HTTPS, and push a candidate branch.
- Run a managed Build in an enabled workspace.
- Bring your own agent and submit a candidate for review with Guard.
- Check pricing and limits: see what free Git includes and how managed Build spending is approved.
- Connect an MCP client if your operator has provisioned a Dengel MCP endpoint.
- Look up CLI commands, API endpoints and scopes, or workflow states, errors, and Receipts.
Open-source releases
- Dengel Git and RustGit (AGPL-3.0-or-later) include the smart HTTP server and the bundled Rust Git storage engine. Browse the canonical source on Dengel, download v1.0.0 on GitHub, or follow the standalone quickstart.
- Dengel CLI (Apache-2.0) is the client for the hosted Gateway. The CLI quickstart and downloads include the installer, binaries, checksums, and source archive.
How Git, Build, and Guard fit together
Dengel Git is where your code lives. Use a standard Git client to clone, fetch, and push. A candidate branch lets you share a commit for review while keeping the shared branch unchanged.
Dengel Build runs a managed coding agent for a change you want made. The technical approver reviews the plan, and the named sponsor approves the quote and spending cap. Build produces a candidate. An independent verifier checks the exact candidate against the approved requirements.
Dengel Guard evaluates the proposed change and its evidence before it can land. You can bring a candidate from your own tools or review one from a managed Build. A passing check is evidence for the review. A separate authorized human decision is required to land the change. A signed Receipt records a completed landing.
The public offer is for early-access Git hosting. Ask about managed Build or Guard access before planning work that depends on those workflows.
For agents
Start with the machine-readable index and use the Markdown Git quickstart or Markdown Guard guide for commands and handoff steps. Get the repository URL, intended task, and approved credential from your operator. Report the exact commit and candidate ref after pushing, then hand off to a human for the next decision. A successful push only confirms that Git stored the candidate.
