Zipper
ServicesPlansDocsSupport
Sign inCreate account

Start

  • Honest production
  • Getting started
  • Quickstart in ten minutes
  • What to use Zipper for
  • Plans and quotas
  • Migrate from Cloudflare
  • Migrate from Vercel
  • Auth, tokens, and SSO
  • Control plane API

Delivery

  • The Crown
  • The Drawbridge
  • The Gallery
  • The Archives
  • Video Delivery

Security

  • The Keep
  • Portcullis
  • The Moat
  • The Scepter
  • Visitor Queue
  • Palace Guard

Compute

  • Edge Functions
  • Site Hosting
  • Job Queues
  • Edge AI

Data

  • The Cellar

Identity & access

  • The Herald
  • The Vault
  • The Throne Room
  • Origin Connect
  • Emails

Observe

  • The Watchtower

Start

  • Honest production
  • Getting started
  • Quickstart in ten minutes
  • What to use Zipper for
  • Plans and quotas
  • Migrate from Cloudflare
  • Migrate from Vercel
  • Auth, tokens, and SSO
  • Control plane API

Delivery

  • The Crown
  • The Drawbridge
  • The Gallery
  • The Archives
  • Video Delivery

Security

  • The Keep
  • Portcullis
  • The Moat
  • The Scepter
  • Visitor Queue
  • Palace Guard

Compute

  • Edge Functions
  • Site Hosting
  • Job Queues
  • Edge AI

Data

  • The Cellar

Identity & access

  • The Herald
  • The Vault
  • The Throne Room
  • Origin Connect
  • Emails

Observe

  • The Watchtower

Start here

Honest production

What Zipper actually runs: two VPS nodes, application-layer DDoS and WAF, in-process cache, DNS-JSON, and original-byte image delivery.

The sentence

This is honest production on two VPS nodes: application-layer DDoS and WAF, in-process cache, DNS-JSON (not port 53), and image delivery (not transcoding). It is not anycast or a GPU LLM farm.

The two nodes

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

Zipper B (72.61.95.36) stores Gallery, Archives, and Video objects. Zipper A 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 on Zipper A.
  • ▸WAF — The Keep: HTTP expression rules before origin.
  • ▸In-process cache — The Crown: Map in the Zipper A Node 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 B. No resize, AVIF, or EXIF strip.
  • ▸Edge AI — grounded Zipper corpus on Zipper A. Not a GPU LLM farm.

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"

Gate (WAF + cache)

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

Next: Getting started · All docs · Create a free account

Zipper

Honest production on two VPS nodes: application-layer DDoS and WAF, in-process cache, DNS-JSON, and image delivery. A Spatial Regal Technology platform by Spatial Regal Digital Ltd.

Product

  • Services
  • Pricing
  • Docs
  • Honest production
  • vs Cloudflare
  • Cloudflare alternative
  • Workers alternative
  • Turnstile alternative
  • Create account
  • Support

Services

  • The Crown
  • The Keep
  • Portcullis
  • The Moat
  • The Herald
  • The Vault
  • The Scepter
  • The Watchtower

Legal

  • Terms
  • Privacy
  • Cookies
  • AUP
  • DPA
  • Security
  • Subprocessors
  • Billing
  • DMCA

© 2026 Spatial Regal Digital Ltd. Zipper is part of Spatial Regal Technology.

Powered by Spatial Regal · tinyzipper.com