Ctrl K
How fast.site Works
fast.site sits between your origin server and your visitors, acting as a high-performance shield and accelerator.
The Request Sequence
1
Browser Request
Visitor's browser sends a request to your domain.
2
GeoDNS Resolution
Resolves the domain to the IP of the nearest Edge Server.
3
Edge Server Processing
Cache HIT
Cached copy found. Content is served in under 5ms. The origin server is never contacted.
Cache MISS
No cached copy found. The Edge Server fetches from Origin and then caches it.
4
Real-time Logging
Metrics pushed to Stats Collector and Dashboard.
Core Components
| Component | Function |
|---|---|
| Cache | High-performance HTTP cache engine running at every Edge Server. |
| Edge Server | A server running cache, deployed globally to handle traffic and TLS. |
| DNS Server | Uses GeoDNS to resolve your domain to the nearest Edge Server IP. |
| Stats Collector | Reads request logs in real time and pushes metrics to Redis. |
| Redis | In-memory store for real-time stats, configuration distribution, and rate limiting. |
| PostgreSQL | Primary database for users, domains, rules, and historical stats. |