What happened
On October 28, 2026, Entire announced that developers in the United Kingdom can use the UK as the primary region for repositories on its platform. Entire describes itself as a Git forge for agent-human collaboration. The announcement covers two ways of using the new region: mirroring an existing repository from GitHub into Entire, or hosting a repository natively on Entire.
A mirror is a synchronized copy of a repository. In Entire's description, the source of origin remains GitHub, while the copy resides on Entire in the selected region and continuously synchronizes changes back to the source. A developer configuring GitHub access on Entire can choose existing repositories to mirror and select a region from a dropdown. The command-line route is entire repo mirror add; the terminal then prompts the user to choose a hosting region from Entire's available list.
For native hosting, Entire asks users to create a project first. A project holds repositories in the chosen region. In the web interface, the stated flow is to select an organization, open Projects in the sidebar, create a project, choose its name and owner, and select UK as the primary region. Repositories can then be created beneath that project. The corresponding CLI example creates a project with entire project create afternoontea --owner buckingham --region uk, creates a repository using entire repo create crumpets --project afternoontea, and checks its status with entire repo view /et/afternoontea/crumpets.
Entire says that pushing, pulling, and cloning near the place of work should reduce latency, and that natively hosted repositories have significantly faster push times. It also says the UK joins available regions in the US, EU, India, and Australia, with further regions planned. The regional option arrives alongside capabilities Entire says it launched that week: Trails, a mechanism for reviewing and merging AI-generated code beyond the pull request; Continuous Memory, which turns a repository into a memory system for agents and development teams; and migration of GitHub Actions pipelines to Buildkite and Depot.
The announcement does not change the basic choice available to a GitHub-centered team. A team can retain GitHub as the origin and use a UK-hosted synchronized mirror, or start with a UK-based Entire project for native repositories. The source provides setup paths for both, but it does not publish latency measurements, price information, capacity figures, or a migration timetable.
What the archive adds
This is a new fact on a known story: Entire, led by ex-GitHub CEO Thomas Dohmke, launches a Git forge built for agent-human collaboration covered the forge's launch, including Trails, Continuous Memory, and distributed Git hosting. The UK is now a named primary region and a documented configuration choice, rather than only part of the launch positioning.
Trend signal
No supplied pattern is genuinely specific enough to characterize a regional repository-hosting expansion.
Why now
The timing is close to Entire's launch-week product rollout. The source presents the UK region together with the Trails, Continuous Memory, and CI-migration capabilities introduced that week, while the archive records the forge launch on October 27. The regional addition makes the distributed-hosting component more concrete for a particular developer population.
Connections to other events
The earlier Entire Field Note described a forge intended for agent-human collaboration, with agent-scored review trails and repository-based memory. This regional update does not introduce another agent workflow. Instead, it adds a location choice to the repository layer underneath those workflows: a UK team may use the same collaboration features while choosing UK as its primary region.
Why it matters
For an AI development team, source control increasingly holds more than hand-written diffs. Entire positions the repository as the location for agent review and team-and-agent memory as well as code. A hosting-region setting therefore becomes relevant wherever a team needs its operational repository copy in a particular place, even if GitHub remains its source of origin.
The immediate practical consequence is modest and clear. UK-based teams evaluating Entire do not need to choose between the platform's agent-oriented features and a UK primary region. They can mirror selected GitHub repositories or begin native projects in the UK. Teams should still distinguish this from a demonstrated performance result: Entire makes a latency and faster-push claim, but supplies no measured comparison in this announcement. The announced feature is a deployment-location option, not evidence that an agent workflow is faster or safer by itself.
What happens next
- Entire will name at least one additional hosting region. (3 months, 70%). Watch for: a company announcement that adds a selectable primary region.
- Entire will provide more operational detail on regional hosting. (6 months, 55%). Watch for: documentation covering availability, replication behavior, or region-specific limits.
Limits and uncertainty
The source is an Entire company announcement, so it establishes that the company says UK mirroring and native hosting are available, and it provides example setup commands. It does not establish independently measured latency, the size of any push-time improvement, uptime, replication timing, data-handling details, pricing, or feature parity across regions. It also does not say which organizations are eligible, whether every repository type can use every region, or whether choosing the UK affects Trails, Continuous Memory, Buildkite migration, or Depot migration. “More launching imminently” is a plan, not a dated commitment.
Skill to build now
Make repository location an explicit item in an agent-platform evaluation. This week, inventory which repositories must remain GitHub-originated and which could be created in a new forge; then test the two Entire paths separately. For a mirror, configure one non-critical GitHub repository, select UK when prompted, and verify the synchronization behavior. For native hosting, create a disposable UK project with --region uk, create a repository beneath it, and check its reported status. Record observed push, pull, clone, and workflow behavior rather than treating vendor performance language as a benchmark.
Reader takeaway
Entire's UK addition is a practical hosting choice, not a new agent capability. It lets UK teams use either a synchronized GitHub mirror or a native Entire repository with UK as the primary region, while retaining access to the forge's recently announced review, memory, and CI-migration features.
Open question
How do latency, synchronization behavior, pricing, and feature availability differ between a UK mirror and a natively hosted UK repository in production use?