Upstream
Operational100.00%
45-day availability
Worst of all services · since launch
Upstream status ↗A real Git forge where humans and agents propose, review, and merge changes in the open, at 380× GitHub’s push speed.
Set up Upstream with your agent. Setup guide
Upstream works with the Git you already use. Clone and push from your terminal, editor, or CI. Nothing new to learn.
Clone and push over HTTPS or SSH from any Git client, editor, or CI. No plugins, no special setup.
Choose who can see each repository. Anyone can read a public one, but only people you allow can change it.
Give read, write, maintain, or admin access to one person or a whole team at once.
Every repository on Upstream runs on Rapid, the Git engine we built in Rust. It's on every plan, including Free.
1,793
pushes a second to a single repository. GitHub manages 4.7.
Pushes a second to one repository
GitHub's own docs recommend at most 6 pushes a minute.
No limit
On repository size
GitHub recommends under 10 GB
256 MB
Per file
GitHub blocks files over 100 MiB
5 GB
Per push
GitHub takes up to 2 GB
12-14 s
To clone our biggest repository
Streamed at up to 96 MB/s
GitHub has announced a new architecture with up to 35 times the write throughput. That would put it at about 165 pushes a second. Rapid takes 1,793.
Measured with ForgeMark, Entire's open-source benchmark, from AWS us-west-2: pushes with 1,024 agents pushing to one repository for three minutes, clones with 128 agents. Other forges' numbers are their own or from Entire's runs.
Like a pull request, but every update is saved as its own version. You always know exactly what was reviewed, what was tested, and what got merged.
Push new commits and the Change Request gets a new version. Earlier versions stay exactly as they were, so you can compare any two.
An approval covers the version it was given. Push new code and the old approval is marked out of date, so it's clear what still needs a look.
CI results show which version they ran on and who reported them, so a pass never comes from older code.
Your agent can set up repositories, open Change Requests, and help review them, with your permissions and your approval.
Paste the setup prompt into your agent. It creates your repository, connects GitHub if you want, and opens your first Change Request.
Your agent signs in as you and can only do what you can. Reviews and required checks still decide what merges, and you can revoke its access anytime.
Terminal agents use the Upstream CLI, and MCP clients connect directly.
Move a repository from GitHub in minutes. You don't have to leave GitHub on day one.
Full history, branches, and tags, from GitHub or any Git host.
Keep GitHub as your main copy while you try Upstream. Once you switch, Upstream keeps GitHub updated as a read-only mirror, so existing clones and integrations keep working.
Anyone can fork a public repository and send changes back as a Change Request. Contributing never gives them access to the rest of your workspace.
Public and private repositories, reviews, and merge queues are free. Add capacity for your projects, team administration, or enterprise governance as you grow.
Upstream next to GitHub and Bitbucket, read live from each official status page.
100.00%
45-day availability
Worst of all services · since launch
Upstream status ↗93.04%
90-day availability
Time without reported incidents · all services
Missing GitHub Status ↗99.55%
90-day availability
Time without reported incidents · all services
Bitbucket status ↗GitHub's own API only publishes current status, so its history comes from the Missing GitHub Status archive. Ours starts the day status.upstream.codes went live. Updated 23:43 UTC.