· Joseph Katsioloudes

Here’s How Entire Stores Your Code In-Region

Engineering

The word "region" can mean different things to various developers based on their backgrounds. For those more familiar with cloud and AWS, it can mean an isolated deployment with its own blast radius. To those with a web background, it can mean an edge cache with a TTL, and for those who run databases, it may be a standby trailing a primary. These are reasonable interpretations of the word, but none are correct when it comes to what we shipped last month in Singapore, Brazil, and the UK, in addition to existing regions in the US, Europe, India, and Australia.

What Is a Region?

A region is built from one or more cells, with each cell hosting a complete copy of your Git repository. Clones and pulls use the regional copy your remote points to, or the closest one if you clone with --nearest (e.g. ). Pushes route through the repository's home cell, in the region you chose to host it upon creation. Nothing here is a cache, but a deliberate design choice of a distributed architecture from day one that you can learn more about in our CTO’s blog post, A Git Forge Without A Center.

With this architecture in place, your repo can live in multiple regions, and if it lives on GitHub, then GitHub remains the source of truth. Then, when you mirror to Entire, regions will serve clones and pulls from the copy nearest to your agents. On the write path, Entire is the fastest Git forge in production today, sustaining 418 pushes per second, up to 89x faster than GitHub and 6x faster than Cursor Origin in our open-source benchmarks. You can mirror from GitHub to Entire using our documentation.

Why Is a Region Not a CDN?

Content Delivery Networks (CDNs) are meant to solve a narrow problem: content that is written once and will be read millions of times by users without writing something back. Think of Netflix or npm.

Your repository is actually the opposite. It takes writes all day from you and agents, with infrequent reads.

A git fetch is not a file download because there are client-server negotiations taking place between haves against wants, as part of the Git protocol. A cache serves finished artifacts, and it expires. A stale cache of a film is a rerun. A stale cache of a repo is a bug.

The biggest difference is that a cache cannot deliver uncached artifacts when its origin is down while an Entire region holds every byte of your repository, so it keeps serving when the origin does not.

So Is It a Read Replica?

A read replica is slightly closer in architecture to an Entire region because reads are local everywhere. For example: when you clone, fetch, and pull from Singapore, changes will hit Singapore. On the other hand, writes are anchored, as every repository has a home cell that is the region where it was created, and pushes through any other region are forwarded there.

When mirroring your repository, GitHub is that primary. So pulls never leave your region, while a push from Australia to a US-homed repository crosses the Pacific first. Between cells, replication is asynchronous.

So on the write path, yes, a region behaves much like a read replica: reads are local, writes go to one home cell. What matters for agents is that each region holds the complete repository, so clones and pulls keep working when the home region or GitHub is unreachable. Agents read far more than they write, so most of their work continues.

Do Entire Regions Fail in Isolation like AWS Regions?

Yes, they do. An Entire region fails in isolation the same way an AWS region does: the failure stays contained, and the other regions keep serving. The difference is what sits inside the isolation boundary. In AWS, each region holds only what you deployed there, so surviving a regional failure is an architecture you design, with cross-region replication as your homework. On Entire, every region that hosts your repository holds the complete copy by default. A region can fail on its own; every other placement of your repository keeps serving.

Create Your First Repository on Entire Today

The fastest way to learn about Entire regions is to create a repository in one yourself by following our documentation or this YouTube walkthrough. Then let us know what you thought by joining our Discord community.

Happy building!