Integrity checks
Stored Git data is checked for corruption.

Git Mirroring
Serve clones and fetches from mirrors near your workloads. Reduce traffic to your Git host while keeping your existing origin.
Clone from a mirror
Same-region mirrors serve clones and fetches from local disk, reducing repeated requests to your origin as CI and agent traffic grows.
Keep a mirror in each region where you run CI, sandboxes or agents. Clones and fetches use the mirror. Push changes to your existing Git host.
Regional Git mirrors. eu-north, us-east, us-west, apac
Clones, fetches and shallow reads are served by the mirror near the workload.
Push changes to your origin. Reviews and branch protection stay with your host.
Refs are advertised after their objects are available. Mirrors that fall behind are removed from rotation.
Scope agent credentials to specific repositories and branches. Keep protected merges behind approval.
Trace activity to the credential that made each change. Works with Claude Code, Codex and tools that use Git or the API.
Stored Git data is checked for corruption.
Avrea can restore repository state from retained versions.
Clone your repository and keep its full Git history.
Pay for repository storage and data transfer, with no per-operation charge.
See Git Mirroring rates →Create a mirror for a repository you have connected to Avrea. Its history, pull requests and issues stay on your Git host.
Keep your branches, pull requests, reviews and merge policies. Connect through your editor, terminal, CI, API or webhooks.
Clone and fetch with the Git clients and tools you already use. The mirror is a read-only copy, so your origin stays the source of truth.
Choose a location for a connected repository, then clone from its mirror. Mirror creation requires an organization admin.