25 named edge services.

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.

• 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

crown

The Drawbridge is a list of your origin servers. Zipper checks they answer. If one is sick, traffic goes to the others. You can weight them and keep a visitor on the same origin.

• Health checks
• Weighted pools
• Sticky sessions
• Fails over by itself

drawbridge

The Gallery stores the image you uploaded and sends those same bytes. The Crown may cache them. You can block other sites from hotlinking. Zipper does not resize, convert to AVIF/WebP, strip EXIF, or transcode.

• Original bytes only
• Stored objects
• Crown cache
• Hotlink guard

gallery

The Archives keep files for your workspace. Metadata lives on Zipper; bytes sit in object storage. Every object is AES-256-GCM. You can give a time-limited signed URL, and you can purge a path from The Crown’s cache. Encryption cannot be turned off.

• Instant purge
• Signed URLs
• AES-256-GCM at rest
• Your workspace only

archives

Video Delivery stores the file you PUT and plays those bytes. Playback links can expire. The file is AES-256-GCM. Zipper does not encode, transcode, watermark, or build adaptive HLS.

• Encrypted files
• Signed playback links
• Crown cache
• No transcode

video

The Keep looks at HTTP requests on Zipper. It blocks common attacks (SQL injection, script tricks, odd protocols) and your own rules. Your origin only sees what passes. This is an application-layer WAF, not a packet filter.

• Common-attack rules on
• Your own rules
• Bot hints
• Challenge or block

keep

Portcullis is Zipper’s own human check. Visitors see a short widget. Zipper looks at the browser, does a small puzzle, and hands your page a one-time token. You send that token to Siteverify. It is not a third-party CAPTCHA network.

• Widget on your page
• Browser signals plus a small puzzle
• One-time tokens
• Siteverify API

portcullis

The Moat is application-layer DDoS on Zipper. If one IP sends too many HTTP requests, Zipper answers 429. It does not swallow raw network packets.

• Cap requests per IP
• On by default
• 429 when someone floods
• Written in Watchtower

moat

The Scepter sits in front of your APIs. It counts requests, checks a token, and can refuse a body that does not match a schema. Use it with Portcullis on login so password guessing is slower.

• Token checks
• Limits per route
• Body shape checks
• Abuse lists

scepter

Visitor Queue holds people on a waiting page when a path is over its limit. They see an estimated wait. Signed-in teammates can skip the line.

• Session budget
• Estimated wait
• Bypass for teammates
• Protects origin

waiting

Palace Guard is Zipper’s antivirus at the gate. It looks at uploads and stored objects while they are still in flight: known malware hashes, EICAR, a Zipper canary, web-shell names, filename tricks, and ZIP headers without opening a bomb. Bad Gallery, Archives, Video, Site Hosting HTML, inbound mail, and function source is held. Quarantined hashes stay held when served. You can watch the scan on the dashboard.

• Cordon-before-disk ingest
• Filename tricks + polyglots
• SVG / PDF / GIF smuggle
• Detonation-free ZIP headers
• Animated live patrol

guard

Edge Functions run your JS in a timed Node vm on Zipper. Use them to rewrite a response, sit in front of origin, or run on a schedule. This is not Cloudflare Workers and not a GPU.

• Timed Node vm
• Cron + scheduled()
• Zipper env bindings
• Watchtower log drain

functions

Site Hosting connects a git repo. Zipper builds it, gives each branch a preview URL, and lets you roll back to an earlier deploy. Secrets sit encrypted. Attach your own domain when you are ready.

• Git deploys
• Preview URLs
• Instant rollback
• Encrypted env vars

hosting

Job Queues take webhooks, mail, and retries off the page request. Zipper retries failed jobs. Poison messages go to a dead-letter queue. Payloads are AES-256-GCM and cannot sit in plaintext.

• Jobs retry
• Dead-letter queue
• AES-256-GCM payloads
• Functions can consume

jobs

Edge AI answers from Zipper’s own help text (zip-fast, zip-large) and can embed text (embed-v1). It is the same engine as Zipper AI on Support. It is not a rented GPU and not a general chatbot.

• zip-fast / zip-large
• embed-v1 vectors
• Answers from Zipper docs
• Not a GPU LLM

ai

Zipper Wire is Zipper’s AI automation control plane. Publish a wire (workflow), attach a manual, schedule, or webhook trigger, and run linear steps: map, branch, grounded AI, HTTP (SSRF-guarded), Function invoke, Job enqueue, email draft, delay, and human approval. Wire orchestrates; it does not replace Job Queues, Edge Functions, Edge AI, Pilot bots, or The Cellar. Runs, step logs, and approvals stay on this process with Palace RBAC and Watchtower audit. Not Zapier’s global farm, not Temporal’s multi-service cluster, and not Cellar’s PGWire adapter.

• Wires, runs, step logs, and HITL approvals
• Triggers: manual, cron drain, webhook (zw_ secret)
• Steps call Functions, Jobs, grounded AI, and HTTP
• SSRF-guarded egress · step retries · dead runs
• wire.tinyzipper.com product host
• Not Cellar PGWire — different product

wire

The Cellar is a sealed database for your app. You get a connection string, REST, live updates, and an import hatch. Paste a phpMyAdmin SQL dump (or CSV / JSON) and Zipper turns those tables into chambers. Browse and edit rows in Studio. Mint, revoke, and regenerate capability seals. Encryption and row rules stay on. SQL is Zipper’s dialect — it never hits the host Postgres parser. It is not Amazon RDS, not stock MySQL, and not a second Supabase. Live updates run on this Zipper process, not a world bus.

• Hatch: capability seal, fail-closed Origin
• Climate: AES-256-GCM and RLS always on
• Import phpMyAdmin SQL / CSV / JSON
• Studio: browse, insert, edit, delete rows
• Mint · revoke · regenerate seals
• SQL, REST, live hatch, and agent setup
• Email/password seals for your users

cellar

The Armory is Zipper’s warrant mesh for iOS, Android, and the web. You mint a hatch-bound session, then a warrant that names a rack. A write warrant is a spent cartridge — reuse returns 409. Musters hold sealed documents with revisions. Kit is cordoned by Palace Guard, including JSON bodies. The roll is real SSE on this node: writes publish put/patch/unput. Rotate anon and service keys from the dashboard anytime. Twenty Docker racks isolate duties. This is not Firebase, not Appwrite Cloud, not FCM/APNs, and not Kubernetes. Without Docker the same twenty racks run in-process and still fail closed.

• Spent-cartridge write warrants (zw.…)
• Hatch-bound sessions — Origin is identity
• Rotate / regenerate anon and service keys
• Live roll SSE on this node (not FCM)
• Musters with revision stamps
• Palace Guard on kit and JSON
• Twenty Docker racks, one duty each

armory

The Herald is where you keep hostname records. Apps look them up with GET /dns-query (JSON). Zipper does not listen on UDP/TCP 53, does not publish nameservers, and does not sign DNSSEC.

• GET /dns-query
• JSON answers
• Add records with the API
• Not port 53

herald

The Vault gets a certificate for each hostname, renews it, and keeps the private key off the tenant dashboard. You can also upload your own certificate.

• Renews by itself
• Your own certificates
• HSTS helpers
• Keys stay in The Vault

vault

Zipper Mail (also called Zipper Email) is transactional email on Zipper’s own MTA. Add a domain, publish SPF (include:_spf.tinyzipper.com), DKIM, and DMARC, verify DNS, then send with POST /api/v1/email/send (all plans) or SMTP at smtp.tinyzipper.com:587 on Starter+. Messages are DKIM-signed on this Global Server node and relayed by Postfix. Attachments, batch, schedule, tags, webhooks, and one-click unsubscribe are built in. Inbound stores encrypted messages and routes to mailbox, webhook, or function. Webmail at mail.tinyzipper.com. Not a marketing blast tool — batches cap at 50 recipients per message.

• Domain verify: SPF + DKIM + DMARC wizard
• HTTP API (zm_) on every plan · SMTP on Starter+
• DKIM-signed outbound on Postfix
• Send keys, SMTP credentials, and dashboard test send
• Send log + suppressions
• Inbound store + routes still included
• Zipper Mail webmail + native app

email

The Watchtower is your log book. You see who hit Zipper, what The Keep blocked, cache hits, and Portcullis results. Other workspaces cannot see yours.

• Live request log
• Threat timeline
• CSV export
• Only your workspace

watchtower

The Throne Room puts a Zipper sign-in in front of an internal app. Only people in your workspace (with MFA if you require it) get through. The origin stays off the public internet.

• Sign-in in front
• MFA grants
• Signed cookies
• Audit trail

throne

Origin Connect runs a small program on your server that dials Zipper. Zipper never needs an inbound hole. The Throne Room can then require sign-in. No public IP on the origin.

• Connector dials out
• Hostname routing
• Private origins
• Heartbeat health

connect

Zipper Pilot is Zipper’s embeddable support copilot and bot service: named bots (Research, Operations, Support) on a shared hall workspace, MCP and Zipper connectors, skills and routines, multi-bot delegation, and approval gates before external actions. It is better than PSTN because the booth is the product: page URL, selected text, citations, and the chat are on the agent’s desk before they pick — no phone number, no voicemail, tab callback if UDP is blocked. It is better than Intercom Fin because it answers only from your scrolls (site, OpenAPI, Zipper services) and records a knowledge gap instead of inventing policy. Cloudflare Workers AI composes on this node when configured. Voice is Starter+: WebRTC with STUN, optional TURN, HTTPS relay, agent-picked queue. Transcripts stay sealed on this process.

• Fail-closed answers with citations — never a GPU guess
• Pilot bots: named teammates, shared workspace, skills, routines, approvals
• Tab callback with page, selection, and thread (not PSTN)
• After-hours scrolls beat voicemail: agents read the page you were on
• Agent copilot drafts from scrolls; resolved chats teach the hall
• HTTPS relay when corporate UDP is blocked

chamberlain