Fetching from the wire…
Public story · 2026-08-24 · high
Tobias Lütke's walgit keeps every git repository in S3, and treats each server as a disposable cache.
Why now: Cursor described the Continuity architecture on August 18, and walgit's README credits it five days later, on August 23.
Shopify CEO Tobias Lütke published walgit as a single commit on August 23, and it passed 720 stars within a day. It's a single-binary git server written in Rust that stores the whole repository in S3 instead of on local disk.
That matters for anyone who's ruled out self-hosting git because of the operational weight of keeping a server's disk in sync with a repository. Walgit removes local disk from that equation, since state lives in S3 and any machine that can reach the bucket can serve requests.
There's no database and no leader node. Every machine running walgit acts as a cache that can vanish without losing data. It handles smart HTTP v0 and v2 fetch and push, and serves bundle-uri clones as static files. It also supports Git LFS and comes with a web UI and webhooks. The code is MIT-licensed.
The README credits the approach to Continuity, the architecture Cursor described on August 18. Walgit adapts that idea for a git server small enough to run on hardware smaller than the repository it serves. The data lives in S3, not on the machine itself.
What the README doesn't say is how walgit performs against dedicated git hosting at scale, or whether Shopify runs it internally. A single commit and a day of star growth is early traction; it isn't a production track record yet.
Continuity's premise was that a client machine doesn't need to hold more of a codebase than it's actively using. Walgit applies that premise to the server side. The machine serving git requests doesn't need to hold the repository either, only access to the S3 bucket.
Each link below shares sources, entities, or timing with this story.
Claude Code competes with Cursor / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code competes with Cursor); both cover Cursor, GitHub, HTTP, MIT; reported by the same outlet (github.com).
Codex CLI uses Rust / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Codex CLI uses Rust); both cover CEO, Cursor, GitHub, MIT; reported by the same outlet (github.com).
Vercel partners with Shopify / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Vercel partners with Shopify); both cover August, Cursor, GitHub; reported by the same outlet (github.com).
Codex CLI uses Rust / Shared entities / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Codex CLI uses Rust); both cover Cursor, GitHub; reported by the same outlet (github.com).
Claude Code competes with Cursor / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Claude Code competes with Cursor); both cover Cursor, GitHub, Rust; reported by the same outlet (github.com).
Vercel partners with Shopify / Shared entities / Same source domain / Earlier coverage / Tension
Linked by a graph relationship (Vercel partners with Shopify); both cover Cursor, GitHub, Rust; reported by the same outlet (github.com).
Claude Code competes with Cursor / Shared entities / Same source domain / What happened next
Linked by a graph relationship (Claude Code competes with Cursor); both cover Cursor, GitHub, MIT; reported by the same outlet (github.com).
Cursor benchmarked against Kiro / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor benchmarked against Kiro); both cover Cursor, GitHub; reported by the same outlet (github.com).