Git hosting built for agents and people working together
Every repository runs as its own object on Cloudflare, so the server writes commits, merges and live edits as fast as your agents make them. Clone, push and CI work as they always have.
Invite-only beta, free while it lasts. Already invited? Sign in.
Built for agent scale
A team with agents opens and merges branches all day, thousands of them. Git hosts built around one shared database slow down for everyone at once. Rebasely gives every repository its own Durable Object on Cloudflare: its refs, its sandboxes and its live edits live in one place, and a busy repository never waits on anyone else's.
- under 5 msfor a repository object's own transaction when it creates a sandbox branch
- 147,900agent edits accepted in 150 seconds from 100 agents on staging, each kept to its own limits
- 100% gitunderneath: the server writes real commits, so every clone, fetch and CI run sees plain history
Three primitives for working with agents
Give an agent a name, a place to try things and a branch to share. Each one is a command for people and a tool for agents over MCP.
Agent identities
Each agent gets its own name in the organization, such as acme/fixer, tokens limited to the repositories and branches you pick, and its own limits. Its pushes, edits and commits say who made them. Disable it and its writes stop at once.
export REBASELY_TOKEN=dga_…
rebasely mcplive:writesandbox:writerefs/heads/agent/*
Sandboxes
A hidden branch per task, created in 59 ms at the median without copying anything. Workflows check it, and Rebasely merges it on the server when they pass: fast-forward, merge or squash.
rebasely sandbox create \
--from main --name fix-login
rebasely sandbox merge fix-login \
--into mainsandbox.createchecks.runsandbox.merge
Live branches
Mount a branch as a folder and use any editor. Every save from a person or an agent reaches everyone on the branch, and Rebasely commits the edits as checkpoints. Git keeps working the whole time.
rebasely mount feature/login --createlive.readlive.writelive.subscribe
Git still works
People keep their tools. Clone, branch, commit and push with any git client, over HTTPS or SSH. Workflows in .rebasely/workflows run on Cloudflare Sandboxes for every push. Agents do the same work through the server, without a checkout.
$ git clone https://rebasely.com/acme/app.git
$ git switch -c fix/session
$ git commit -am "Expire idle sessions after 14 days"
$ git push -u origin fix/session
To https://rebasely.com/acme/app.git
* [new branch] fix/session -> fix/sessionsandbox.create({ repo: "acme/app", from: "main", live: true })
→ refs/sandbox/fixer/fix-session
live.write({ path: "src/session.ts", base_version: 3, edits })
→ version 4
checks.run({ sandbox: "fix-session" })
→ ci: success
sandbox.merge({ sandbox: "fix-session", mode: "squash" })
→ main 9e2c41dClone any public repository without an account
git clone https://rebasely.com/<org>/<repo>.gitPushing and private repositories take an access token as the password, or an SSH key (git@ssh.rebasely.com:<org>/<repo>.git). Getting started walks through it.
Your repository's memory
Agents start every task knowing nothing. Put a .rebasely folder in the repository: notes and decisions in kb/, the components and how they connect in architecture/. Rebasely shows them as the Knowledge and Architecture tabs, and agents read them before they change code.
kb.searchkb.readarch.get
rebasely kb check and rebasely arch check fail CI when a note or a component no longer matches the code. The .rebasely folder explains the format.
Measured on staging
Times from Cloudflare's network, on one scale. The line is the target for both: 200 ms.
Sandbox creates: 100 on staging, timed at the edge. Live saves: 200 saves between two connected clients. A client that reconnects after a gap gets 50,000 missed edits replayed in 525 ms.
Careful with your code
Passkeys for what matters
Creating a token, adding a key or deleting anything needs a recent passkey confirmation.
Tokens with a narrow reach
Tokens for people and agents work in one organization, on the repositories and scopes you choose. A token found leaked is revoked.
An admin console nobody can reach
Rebasely's own admin tools run only behind Cloudflare Access with a passkey, never on a public host.
Private means invisible
A private repository answers exactly like one that does not exist, to anyone without access.
How Rebasely handles security and how to report a problem.
Request an invite
Rebasely is free during the beta, within the published limits. We are letting people in a few at a time. Tell us where to reach you and what you want to build.
Invited people sign in with Google and accept the terms before anything is created. During the beta, data may be purged; keep your own copies.