In-process cache
The Crown
The Crown remembers recent pages and files in Zipper’s own process. If a visitor asks for something we already have, they get it from memory. If not, Zipper fetches it from your site (or from object storage) and keeps a copy for a while. This is in-process cache on multi-layered Global Server nodes. This is a Cloudflare Cloudflare CDN / Caching alternative included on every Zipper plan.
Cloudflare analogue: Cloudflare CDN / Caching
What it is
The Crown remembers recent pages and files in Zipper’s own process. If a visitor asks for something we already have, they get it from memory. If not, Zipper fetches it from your site (or from object storage) and keeps a copy for a while. This is in-process cache on multi-layered Global Server nodes.
Cloudflare analogue: Cloudflare CDN / Caching. SLA 99.9% · p99 42ms. Admins publish cache policy. Operators may purge.
- ▸Saves pages in memory
- ▸Can serve a slightly old copy while it refreshes
- ▸Shrinks HTML and compresses files
- ▸Last good copy if your site is down
How it works
Point an A/AAAA at tinyzipper.com (191.215.40.237) or call https://tinyzipper.com/gate/{hostname}/. Visitors hit Zipper’s in-process cache on multi-layered Global Server nodes.
The Crown applies cache level and TTLs from Policy, then fetches origin only on a miss. gzip (and brotli when requested) run in the same process.
Purge a prefix when you ship a new asset. Purge drops keys from Zipper’s memory — there is no extra PoP to wait on.
Use cases
Concrete ways teams use this service on day one.
Speed up a marketing site
A brochure site on a single origin is slow for visitors in Europe and North America.
- Add the zone, proxy the A/CNAME record.
- Set cache level to Standard. HTTP/3 is QUIC on Zipper unicast UDP/443 when nginx has ngx_http_v3_module; otherwise HTTP/2.
- Purge / after a deploy: POST /api/v1/archives/purge with prefix "/".
Survive origin outages
The origin goes down during a deploy.
- Keep Always Online on (default).
- The Crown serves last-known-good HTML and static objects.
- Watchtower shows origin 5xx separately from edge 200s.
Set it up in the dashboard
Dashboard → Services → The Crown.
Publish cache level, TTLs, minification, and gzip.
Use Purge prefix for /assets/* after a release.
API
Control-plane: POST /api/v1/archives/purge. Send Authorization: Bearer tz_live_YOUR_TOKEN.
Creates count against the plan quota. A 402 plan_limit means you are at the cap — upgrade or delete an unused resource.
Purge a path
curl -sS -X POST https://tinyzipper.com/api/v1/archives/purge \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"prefix":"/assets/*"}'List the same resource in JavaScript
const res = await fetch("https://tinyzipper.com/api/v1/archives/purge", {
method: "GET",
headers: {
Authorization: `Bearer ${process.env.ZIPPER_TOKEN}`,
"Content-Type": "application/json"
}
});
const json = await res.json();
if (!res.ok) throw new Error(json.error ?? res.statusText);
console.log(json);Tips
Use Bypass only on HTML that is personalised per cookie.
Aggressive cache is for hashed `/static/` folders.
- ▸Global Server
- ▸In-process cache
Runbook
Purge by prefix on Zipper. The Crown is an in-process cache.
Next: The Keep · All docs · Create a free account