Show HN: R/place for Git – Open-source Git server sustaining 567 pushes/s
hey hn, sven from Reason Machines (YC F26). we've been experimenting with how fast we can push our ci/cd and code storage systems when swarms of coding agents are all pushing at once. turns out giving 100 agents git push basically ddos'es normal git servers. so we wrote aspen: an open-source git server (apache 2.0) that hits 567 pushes/sec on a single 8-core box with stock git clients. to stress test it live, we put up a shared canvas where every pixel is a real git push: https://place.reasonmac
Read original source
Source record
Recorded metrics
points · 1 votes
2026-11-06 15:45:18.071Z
cumulative since publication
Research analysis
Project record
Source account: hey hn, sven from Reason Machines (YC F26). we've been experimenting with how fast we can push our ci/cd and code storage systems when swarms of coding agents are all pushing at once. turns out giving 100 agents git push basically ddos'es normal git servers. so we wrote aspen: an open-source git server (apache 2.0) that hits 567 pushes/sec on a single 8-core box with stock git clients. to stress test it live, we put up a shared canvas where every pixel is a real git push: https://place.reasonmac
Observed adoption & comparisons
Source votes: 1 votes (Nov 6, 2026 UTC; cumulative since publication) Recent records to compare: “Show HN: Current – Change control for AI agents (Elixir)” (Show HN, Nov 6, 2026); “Show HN: Agentic Identity Broker, OAuth Delegation for AI Agents” (Show HN, Nov 6, 2026). Shared themes are navigation hints; they have not been verified as the same need or independent corroboration.
Adoption decision
Evaluate it against the tool or manual workflow it would replace. The stored record supports discovery; it does not yet establish reliability, lower operating cost or commercial adoption.
Unverified requirements
Not verified: license permissions, required hardware, installation steps, maintenance status and a representative task with its failure cases.
Next test
Choose one real task and a current alternative. Record the commit, environment, input, output, elapsed time and failure behavior; retain the result before recommending adoption.