About
A small, focused edge cache.
Larus Edge started as an internal tool to serve build artifacts closer to the teams using them. Today it runs a handful of regional points of presence and keeps the configuration surface intentionally small.
How it works
You point a hostname at the nearest PoP. Requests are matched against your cache rules; hits are served straight from the edge, misses are fetched from origin and stored for the next visitor. Everything travels over HTTP/2 with TLS 1.3.
Where we run
PoPs are placed in a few regions in Europe. Each node is single-purpose and stateless —
it holds cached objects and nothing else. This eu-north node is one of them.
Contact
Questions about a deployment? Reach the team at hello@example.com.