\n\n\n
\n
\n .git_\n
\n \n
\n
\n v2.0\n GitHub\n \n
\n
\n
\n\n
\n\n
\n \n\n
\n
\n Docs\n /\n Infrastructure\n
\n\n

Infrastructure Architecture

\n

Understand the global infrastructure powering .git, including our edge network, compute layers, storage systems, and security boundaries.

\n\n

Overview

\n

.git is built on a distributed, multi-region architecture designed for maximum availability, low-latency deployments, and seamless scaling. Our infrastructure abstracts away complex cloud operations while giving you full control over your deployment targets.

\n\n
\n
â„šī¸ Note
\n
Infrastructure configurations are declarative. You define your topology in .git/config.yaml and the platform provisions the underlying resources automatically.
\n
\n\n

Global Edge Network

\n

Our edge network spans 300+ locations across 6 continents. Static assets, CDN caches, and HTTP/3 connections are terminated at the nearest edge node before routing to your compute layer.

\n\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
LayerTechnologyLatency (p95)Use Case
Edge CDNCloudflare Workers / Fastly< 30msStatic assets, WAF, caching
Regional Load BalancersEnvoy Proxy / HAProxy< 5msTraffic routing, TLS termination
Compute NodesKubernetes / Serverless< 20msApplication logic, APIs
\n
\n\n

Compute & Auto-Scaling

\n

.git supports both provisioned and serverless compute models. Auto-scaling is handled via custom metrics and predictive algorithms that analyze traffic patterns 24h in advance.

\n\n
\n
\n .git/config.yaml\n \n
\n
# Compute configuration\ncompute:\n  model: auto  # provisioned | serverless | auto\n  min_instances: 2\n  max_instances: 50\n  scaling:\n    metric: cpu_utilization\n    threshold: 70\n    cooldown: 60s
\n
\n\n
\n
💡 Tip
\n
Use model: auto for production workloads. The platform will dynamically switch between serverless cold starts and provisioned instances based on traffic patterns.
\n
\n\n

Storage & Databases

\n

Persistent storage is decoupled from compute. We support multiple storage backends with automatic failover and cross-region replication.

\n\n \n\n

Networking & DNS

\n

All .git domains are provisioned on our private DNS network. You can attach custom domains with automatic SSL provisioning via ACME/Let's Encrypt.

\n\n
\n
\n Terminal\n \n
\n
$ git dns add example.com --type CNAME --value \"my-app.git.dev\"\n✓ DNS record created (propagation: ~30s)\n✓ SSL certificate issued (Let's Encrypt)\n
\n
\n\n

Security & Compliance

\n

Security is baked into every layer of the infrastructure. All data is encrypted at rest (AES-256) and in transit (TLS 1.3). Network isolation is enforced via VPC peering and zero-trust principles.

\n\n
\n
âš ī¸ Important
\n
Private networking requires an active VPC endpoint. Ensure your security groups allow inbound traffic on ports 443 and 8443 for internal service mesh communication.
\n
\n\n

Compliance Certifications

\n \n\n

Region Selection

\n

Choose your primary region based on your user base. Cross-region replication is available for disaster recovery and compliance requirements.

\n\n
\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n
RegionCodeAvailability
North Virginia, USus-east-1✅ Available
Frankfurt, Germanyeu-central-1✅ Available
Tokyo, Japanap-northeast-1✅ Available
Singaporeap-southeast-1🚧 Beta
\n
\n\n
\n ← Previous: Quickstart\n Next: Regions & Edge →\n
\n
\n\n \n
\n\n \n\n