A Git Forge Without a Center
Blog post from Entire
As AI agents create large numbers of disposable cloud workspaces that must clone repositories, centralized Git forges risk becoming a storage and throughput bottleneck despite Git’s inherently distributed design. Entire introduces EntireDB, a Git-compatible forge architecture that stores complete repository copies in regional “cells” near agent workloads, using PostgreSQL for strongly consistent mutable refs and multiple storage nodes for immutable Git objects and packfiles. Pushes stage and replicate objects across at least two availability zones before a compare-and-swap ref update makes changes visible, while fetches are generally served directly from a local node without accessing external storage. The company contrasts its approach with GitHub’s quorum-based Spokes replication and Cursor’s S3-backed Continuity system, arguing that its design combines local object serving with independent ref coordination. Entire reports benchmark results of up to 418 pushes per second, or up to 89 times faster than major existing forges, while noting tradeoffs including asynchronous object and cross-region replication and support for only one writable cell per repository. The system is tested through deterministic failure simulations, supports GitHub mirroring and regional placement, and is planned for open-source release.
No tracked trend matches for this post yet.
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.