Start here

Honest production

What Zipper actually runs: multi-layered Global Server nodes, application-layer DDoS and WAF, in-process cache, DNS-JSON, and original-byte image delivery.

The sentence

This is honest production on multi-layered Global Server nodes: application-layer DDoS and WAF, in-process cache, DNS-JSON (not port 53), and image delivery (not transcoding).

Global Server layers

Zipper is the control plane and HTTP data plane: The Crown cache, The Keep, The Moat, Herald DNS-JSON, Edge Functions, Site Hosting, Edge AI.

Object storage holds Gallery, Archives, and Video objects. Zipper fetches them and can cache the response in process.

What that means for each job

These are the production paths. Analogues to Cloudflare products are named so you can map a skill, not so we claim the same network.

▸Application-layer DDoS — The Moat: per-IP HTTP cap → 429.
▸WAF — The Keep: HTTP expression rules before origin.
▸In-process cache — The Crown: Map in the Zipper process, TTL + SWR, gzip/brotli.
▸DNS-JSON — The Herald: GET /dns-query, Content-Type application/dns-json. No UDP/TCP 53.
▸Image delivery — The Gallery: original bytes from Zipper object storage. No resize, AVIF, or EXIF strip.
▸Edge AI — grounded Zipper corpus. Not a GPU LLM farm.
▸The full substrate catalog lives at Docs → What is not Cloudflare or Neon scale.

Try it

You do not need nameserver cutover to exercise the data plane.

DNS-JSON

curl -sS "https://tinyzipper.com/dns-query?name=example.com&type=A" -H "Accept: application/dns-json"

Original-byte image (transform params ignored)

curl -sS -D- "https://tinyzipper.com/gate/YOUR_HOSTNAME/cdn-cgi/image/width=800,format=avif/hero.jpg"

Gate (WAF + cache)

curl -sS -D- "https://tinyzipper.com/gate/YOUR_HOSTNAME/"

Next: What is not Cloudflare or Neon scale · All docs · Create a free account