Infrastructure Architecture
\nUnderstand the global infrastructure powering .git, including our edge network, compute layers, storage systems, and security boundaries.
\n\nOverview
\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.git/config.yaml and the platform provisions the underlying resources automatically.Global Edge Network
\nOur 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| Layer | \nTechnology | \nLatency (p95) | \nUse Case | \n
|---|---|---|---|
| Edge CDN | \nCloudflare Workers / Fastly | \n< 30ms | \nStatic assets, WAF, caching | \n
| Regional Load Balancers | \nEnvoy Proxy / HAProxy | \n< 5ms | \nTraffic routing, TLS termination | \n
| Compute Nodes | \nKubernetes / Serverless | \n< 20ms | \nApplication logic, APIs | \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# 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 model: auto for production workloads. The platform will dynamically switch between serverless cold starts and provisioned instances based on traffic patterns.Storage & Databases
\nPersistent storage is decoupled from compute. We support multiple storage backends with automatic failover and cross-region replication.
\n\n- \n
- Object Storage: S3-compatible buckets with 99.999999999% durability \n
- Managed Databases: PostgreSQL, Redis, and MongoDB with automated backups \n
- Blob Cache: Redis-backed distributed cache with edge invalidation \n
Networking & DNS
\nAll .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$ 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 Security & Compliance
\nSecurity 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\nCompliance Certifications
\n- \n
- SOC 2 Type II \n
- ISO 27001 \n
- GDPR Compliant \n
- HIPAA Ready (Enterprise tier) \n
Region Selection
\nChoose your primary region based on your user base. Cross-region replication is available for disaster recovery and compliance requirements.
\n\n| Region | \nCode | \nAvailability | \n
|---|---|---|
| North Virginia, US | \nus-east-1 | \n â Available | \n
| Frankfurt, Germany | \neu-central-1 | \n â Available | \n
| Tokyo, Japan | \nap-northeast-1 | \n â Available | \n
| Singapore | \nap-southeast-1 | \n đ§ Beta | \n