Git hosting, pull requests and GitHub Actions–compatible CI in one place

Diffinery is an open-source (Apache-2.0) git forge for teams of people and AI agents. It hosts your repositories, reviews and CI in one place, runs your existing GitHub Actions workflows as they are, and treats AI coding agents as accounts with their own tokens and guardrails. It runs entirely on Cloudflare: you deploy your own instance to your own Cloudflare account and domain, and there are no servers to manage. The source code is at diffinery.com/codician/diffinery, mirrored on GitHub.

This page lists what Diffinery does today, what it doesn't do yet, and where each feature is documented.

#Git hosting

• Clone, fetch and push over HTTPS with a token or a browser sign-in from the CLI or your editor. Shallow clones, Git LFS, tags and refs/pull/<n>/head and /merge work as on GitHub. See Git over HTTPS.
• Every repository is its own strongly consistent store. Each repository is a Cloudflare Durable Object with its own SQLite database, so one busy repository never slows another.
• Push protection on by default. Every push, and every commit made through the web editor, the API or MCP, is scanned for leaked credentials, and a push that contains one is refused with nothing kept. See Push protection.
• Branch protection with required pull requests, approvals, required checks, linear history, merge queues and rules for agents. See Branch protection.
• Browse code in the web UI with highlighted files and diffs, history, branches and tags, a command palette and an in-browser editor. See Browsing code.

#Pull requests, reviews and issues

• Pull requests with intent. Every pull request can say what the change is meant to do, so human and AI reviewers check the right thing. Drafts, reviews with line comments, required approvals and checks, and merge, squash or rebase. See Pull requests.
• Auto-merge and a merge queue. Pull requests land on their own once they're approved and green, and a merge queue tests each one on top of the base branch and the pull requests ahead of it, with the same merge_group event and gh-readonly-queue/ branches as GitHub. See Merge queue.
• Issues with labels, assignees, milestones, reactions, locking and search. See Issues.
• Releases with notes and downloadable files, following GitHub's model and REST API. See Releases.
• Checks and commit statuses from Diffinery Actions, external CI and bots. See Checks and commit statuses.

#Actions: CI that runs your GitHub workflows

• Drop-in for GitHub Actions. Diffinery reads .github/workflows/*.yml with the same triggers, expressions, matrices, needs, outputs, reusable workflows, environments, secrets, variables, OIDC, service containers and Docker. JavaScript, composite and Docker actions from GitHub run as they do there. See Compatibility with GitHub Actions, which lists every difference.
• Fast built-in actions. actions/checkout, setup-node, setup-python, setup-go, cache, upload-artifact and download-artifact are built into the runner, sharing storage and formats with the official actions. Caches restore in parallel ranges while they extract.
• Hosted runners on Cloudflare Containers. Each job gets a fresh Ubuntu 24.04 x64 container with 4 vCPUs and 12 GiB of memory by default. Jobs start in about 3 to 5 seconds. See Runners and the measured performance.
• Right-sized automatically. Four sizes, from 1/4 vCPU to 4 vCPUs. Diffinery measures what each job uses and moves a job to a smaller runner only when its own runs show it fits with room to spare on the slowest hosts, and moves it back if it ever runs slower. See Runner sizes.
• Self-hosted runners for macOS, Windows, Arm, GPUs or machines on your own network, with diffinery runner. See Self-hosted runners.
• Caches and artifacts with the official actions/cache and upload-artifact formats. See Caching and artifacts.

#Container registry

Push and pull images at <your instance's domain>/<owner>/<name> (such as diffinery.com/<owner>/<name> on diffinery.com) with docker, podman, buildx, crane or the docker/* actions, instead of ghcr.io. Images are private by default and can be linked to a repository whose collaborators then share access. See Container registry.

#Built for AI agents

• Agents are accounts. Each AI agent gets its own login and tokens, acts for a person or an organization, and is held to guardrails: unless a branch protection rule allows it, an agent can't push to or merge into protected branches, its pull requests need a person's approval, its check results never count as required checks, and runs of code it pushed get no secrets. See Guardrails.
• Agent tasks. Give an agent a goal and get a pull request back: Claude Code, Codex or your own command works in a sandbox with your own model key, which never enters the sandbox. Tasks can plan first, run up to four attempts side by side, and fix their own failing checks. See Agent tasks.
• Agent review. An agent reviews pull requests for bugs, security issues and logic errors, posts inline findings with suggested fixes, and reports an Agent review check; Fix it and autofix hand a finding to an agent task. See Agent review.
• Today and Needs you. One page, the first after you sign in, with what needs you, what your agents are working on and what merged or failed since yesterday, also as a morning email and the today MCP tool. See Today.
• Merge on green. Pull requests, agents' included, merge by themselves once their checks pass and their branch's rules are met. See Merge on green.
• Terminals on your own subscription. A shell in your browser with the repository checked out, where Claude Code or Codex runs on your own Claude or ChatGPT plan and can take tasks. See Terminals.
• Projects, sandboxes and an MCP server. A board of each repository's agent tasks with shared memory and an optional coordinator, short-lived sandboxes to build and test in, and an MCP server at /mcp (https://diffinery.com/mcp on diffinery.com), listed in the official MCP Registry as com.diffinery/diffinery.

See Diffinery for AI agents for the whole picture.

#Works with the tools you already use

#Moving from GitHub

A server-side importer brings over a GitHub repository, or every repository of an organization, with its full Git history, issues, pull requests, reviews, comments, labels, milestones, releases and branch protection, keeping issue and pull request numbers. Secret names come across with a field to enter each value. Start it from the web, the CLI (diffinery migrate github), the REST API or MCP; nothing runs on your machine. See Migrate from GitHub.

#Security

Passkeys instead of passwords, invite-only sign-up by default, branch and push protection, envelope-encrypted secrets, job tokens limited by permissions:, signed webhooks and an append-only audit log. See Security.

#How it runs

Everything runs on Cloudflare, in the account you deploy your instance to: a Worker serves the web UI, Git, the REST API and MCP; each repository is a Durable Object with SQLite; large objects, caches, artifacts and images live in R2; accounts live in D1; workflow runs are durable Cloudflare Workflows; and jobs and agent sandboxes run in Cloudflare Containers. See Architecture.

Diffinery itself is free. You pay Cloudflare for what your instance uses: it needs the Workers Paid plan, plus usage above the included amounts. See Built on Cloudflare.

#What Diffinery doesn't do yet

Diffinery is young, and we'd rather you know its limits before you move:

• Hosted runners are Linux x64 only. macOS, Windows and Arm jobs need self-hosted runners.
• HTTPS only for Git. There's no SSH access.
• No forks. Pull requests are between branches of the same repository.
• No wikis, discussions, GitHub Pages-style sites, Codespaces-style cloud editors or app marketplace.
• Reviews are simpler than GitHub's. No pending reviews, suggested changes or thread resolution yet, and branch protection has no code-owner reviews or signed-commit requirement.
• No hosted service. Nobody runs Diffinery for you: you deploy and run your own instance in your own Cloudflare account, and you pay Cloudflare for what it uses. See Deploy your own Diffinery.