Fresh object, cached
The node has the object and it is inside its freshness window, so it answers directly. Your origin sees nothing.
Static delivery
Your assets, served from the nearest node
Point a hostname at Northlane and we cache your images, bundles, fonts and release artifacts on regional nodes. Origin stays quiet, first paint stops depending on where the visitor happens to live.
- Regional nodes
- 34
- Median edge response
- 18 ms
- Cache hit ratio
- 96.4%
What actually happens on a request
Stale or missing
The node revalidates against your origin with the stored
ETag. A 304 refreshes the entry without
moving the body again.
Never cached
Responses marked no-store and anything carrying an
Authorization header are forwarded and never retained
on the edge.
Regions
Every region runs at least two nodes. If one drains, traffic shifts to the sibling without a DNS change.
| Region | Nodes | Edge p95 | State |
|---|---|---|---|
| Frankfurt | 4 | 14 ms | operational |
| Helsinki | 3 | 16 ms | operational |
| Ashburn | 5 | 21 ms | operational |
| Singapore | 3 | 28 ms | draining |
Pricing
Starter
€0/mo
- 100 GB egress
- One custom hostname
- Shared cache tier
Team
€29/mo
- 2 TB egress
- Ten hostnames
- Tag-based purge API
- Origin shielding
Scale
Custom
- Committed egress
- Dedicated node capacity
- Log delivery to your bucket
Questions people actually ask
Do you rewrite my URLs?
No. Paths pass through untouched, so an object at
/build/app.a91f.js on your origin stays at the same
path on the edge.
How fast is a purge?
Tag purges propagate to every node in a few seconds. Purge is accepted from the control API only — never from the edge itself.
Can I serve a whole site?
You can, as long as it is static. Northlane has no server-side rendering and no database; dynamic responses belong on your origin.