Platform / Infrastructure / Edge Networking
Infrastructure

Global Edge
Networking

Route traffic intelligently across 300+ points of presence. Sub-50ms latency, automatic failover, and zero-config DDoS mitigation built into every layer.

Deploy to Edge → Read Documentation
300+PoPs
24msAvg Latency
10.2TbpsCapacity
Architecture

How Edge Routing Works

Requests are intercepted, optimized, and served from the closest available node before ever hitting your origin.

🌐
Client
→
📡
DNS / Anycast
→
⚡
Edge Node
→
💾
Origin
🔀

Intelligent Load Balancing

Real-time health checks and geographic-aware routing distribute traffic across available edges automatically.

🛡️

Layer 3/4 DDoS Shield

Scrubbing centers absorb volumetric attacks up to 10Tbps before they impact your application layer.

🔄

Automatic Failover

If a node degrades, traffic seamlessly shifts to the next optimal PoP with zero packet loss visible to clients.

edge_config.toml
# Route definitions for .git edge
[routing]
strategy = "geo_latency"
failover = true

[cache]
ttl = "3600s"
stale_while_revalidate = "600s"

[security]
ddos_protection = "strict"
waf_rules = ["owasp", "custom/01"]

Declare Your Network

Configure routing, caching, and security policies as code. Changes propagate globally in under 30 seconds with automatic rollback capabilities.

  • Version-controlled infrastructure
  • Preview deployments with isolated edge contexts
  • Automated syntax validation & diff analysis
  • CLI & API support for CI/CD pipelines
n
Performance

Benchmarks & Comparisons

Independent third-party tests across major metropolitan regions.

Metric.git EdgeTraditional CDNBare Metal
Global Avg Latency 24ms68ms142ms
Cache Hit Ratio 94.2%78.5%~40%
DDoS Mitigation Time < 200ms2-5sNot included
Config Propagation 12s60-120sManual
FAQ

Common Questions

How does edge caching interact with my origin servers?
.git uses a pull-based cache model. The first request bypasses the edge and fetches from your origin, setting cache headers. Subsequent requests are served directly from the edge. You control TTLs, bypass rules, and purging via config or API.
Can I run custom logic at the edge?
Yes. .git supports WebAssembly modules and lightweight edge functions. They execute in isolated sandboxes with cold starts under 15ms, perfect for request rewriting, auth checks, or A/B testing.
What happens during a regional outage?
Our global routing mesh detects failures in real-time. Traffic is automatically rerouted to the next healthiest PoP. DNS TTLs are optimized, and session stickiness is preserved where possible to prevent drop-offs.
Is there a limit on bandwidth or requests?
Standard plans include generous baseline allocations. Enterprise customers get dedicated capacity pools, custom rate limiting, and guaranteed bandwidth SLAs. Oversharing never results in dropped packets.

Ready to reduce latency?

Connect your origin and let .git optimize your traffic globally. No long-term contracts.

Initialize Edge Network →