34 named edge services.

Your app database under Zipper. Paste a phpMyAdmin dump. Connect with SQL, REST, or live updates.

In plain English — A real Postgres database for your app, run by Zipper. You get a connection string, a REST API, live updates, and a studio to browse your rows — with encryption and row-level rules always switched on.

• Hatch: capability seal, fail-closed Origin
• Scoped sessions — narrow tables + ops per user
• +9 more

Spent-cartridge warrants for mobile and web. Each write fires once, bound to a rack, hatch, and device. Not a JWT farm and not Firebase.

In plain English — A ready-made backend for mobile and web apps: sign-in sessions, a database where each collection has its own encryption key, and live updates. Like Firebase, but sealed — and a collection can be crypto-shredded forever.

• Spent-cartridge write warrants (zw.…)
• za1 sealed musters — per-collection keys, crypto-shreddable
• +8 more

Sealed Postgres with every write posted to a hash-chained ledger. Replay any table to any moment, or ask for a signed receipt for a row. Not a blockchain.

In plain English — A Postgres database that writes every change into an unchangeable running ledger at the same moment it happens, so you can prove what changed, when, and under whose key — without trusting a log file.

• Ledger posting inside the write transaction
• Hash-chained assay entries
• +6 more

Field-sealed documents with blind indexes — we store ciphertext we cannot read, and your queries still find rows. Not a column toggle on The Cellar.

In plain English — A document store that seals every field before it leaves your app: we keep text we cannot read, and blind match tokens still let your queries find the right rows. Only your key opens it.

• Field-level envelope encryption before upload
• Blind equality and coarse range indexes
• +5 more

A key-value store your app and Edge Functions share over one API, with feature flags and gradual rollouts built in.

In plain English — A fast shared cupboard for small pieces of data — settings, flags, and counters — that your app and your edge code can both read and write in milliseconds.

• REST API plus an Edge Functions binding
• Feature flags with percentage rollouts
• +3 more

Full serverless runtime with 60s timeout, npm packages, WebSockets, streaming, and Web APIs.

In plain English — Small pieces of JavaScript that run on Zipper the moment a visitor makes a request — great for custom logic, redirects, or APIs without running a whole server.

• 60s wall-clock, 10s CPU
• Web APIs: fetch, crypto, streams, structuredClone
• +7 more

Builds your site from git. Static or SSR. Each branch gets its own stage and preview URL.

In plain English — Connect your git repo and Zipper builds and hosts your website. Every branch gets its own stage with a preview link, and you can roll back at any time.

• Git deploys
• SSR Node origins
• +2 more

A background list for work that should not slow a visitor down.

In plain English — A to-do list for slow background work. Webhooks and long tasks go on the list and get done without slowing the visitor's page down.

• Jobs retry
• Dead-letter queue
• +2 more

Answers from Zipper’s own docs, on Zipper. Not a GPU LLM farm.

In plain English — A small assistant that answers questions using Zipper's own help documentation. It is not a general chatbot.

• zip-fast / zip-large
• embed-v1 vectors
• +2 more

Versioned automation wires that trigger, branch, call Zipper connectors, run grounded AI, and pause for human approval — on Zipper’s global edge network.

In plain English — Build automated workflows that run on a schedule or a webhook, call your services, use AI that stays grounded in your data, and pause for a human to approve — without writing glue code.

• Standalone product — not included in Cloud Edge plans
• Free Spark · Circuit $19/mo · Current $49 · Grid $99
• +4 more

Typeform-style forms with drag-and-drop fields, conditional logic, file uploads, and real-time responses — on Zipper’s global edge network.

In plain English — Drag-and-drop online forms with conditional questions and file uploads. Share a link, collect answers, and trigger automations or email notifications.

• Drag-and-drop field builder
• Public submission with Portcullis captcha
• +4 more

Verify your domain, mint a send key or SMTP credential, and ship DKIM-signed mail through Zipper’s mail transport — plus inbound store and routes.

In plain English — Send and receive email from your own domain through Zipper, with signed outgoing mail, spam suppression, and a webmail inbox included.

• Domain verify: SPF + DKIM + DMARC wizard
• HTTP API (zm_) on every plan · SMTP on Starter+
• +5 more

An embeddable support pilot that refuses to guess, learns your site, and queues page-aware WebRTC booths. Agents pick with the thread, citations, and URL already in hand.

In plain English — An embeddable support chat and call system. The assistant only answers from your own docs, and agents can pick up calls with the visitor's page already in view.

• Fail-closed answers with citations — never a GPU guess
• Pilot bots: named teammates, shared workspace, skills, routines, approvals
• +4 more

Serves your original image files from Zipper. No transcode, no Polish.

In plain English — Stores your images and serves them fast from Zipper's cache. It sends back the exact file you uploaded — no resizing or conversion.

• Original bytes only
• Stored objects
• +2 more

A locked file store with signed links. You can drop a folder from cache at once.

In plain English — A locked file box in the cloud. Files are encrypted, you can share them with time-limited links, and you can clear cached copies instantly.

• Instant purge
• Signed URLs
• +2 more

Plays the video file you uploaded. No encode, no HLS ladder.

In plain English — Stores the video file you uploaded and streams those exact bytes to viewers. Playback links can expire, and the file is encrypted.

• Encrypted files
• Signed playback links
• +2 more

Keeps copies of your pages in Zipper’s memory so repeat visits load faster.

In plain English — Zipper keeps copies of your pages and files in its own memory, so repeat visitors get them instantly instead of waiting for your server.

• Saves pages in memory
• Can serve a slightly old copy while it refreshes
• +2 more

Store DNS records and answer them as JSON on /dns-query — not port 53.

In plain English — A simple phone book for your domain. Apps look up your records over HTTPS and get easy-to-read JSON answers back.

• GET /dns-query
• JSON answers
• +2 more

Gets HTTPS certificates for your hostnames and keeps them renewed.

In plain English — Zipper gets the padlock (HTTPS) for your domain names, renews certificates on its own, and keeps the private keys safe.

• Renews by itself
• Your own certificates
• +2 more

Sends visitors to healthy origin servers, and skips ones that are down.

In plain English — Spreads visitors across several of your servers and automatically sends them elsewhere when one server is sick.

• Health checks
• Weighted pools
• +2 more

Puts a private server on a Zipper hostname without opening a public port.

In plain English — Connects a private server to Zipper without opening any public ports — the server dials out to Zipper instead of being exposed.

• Connector dials out
• Hostname routing
• +2 more

Answers reusable requests from a shared cache in front of the app — fewer trips to origin, faster loads.

In plain English — A cache gate in front of everything Zipper hosts: reusable pages and files are answered straight from a shared copy, so most requests never wake up the app behind the gate.

• Cacheable GETs answered at the gate
• Private and no-store never stored
• +2 more

Probes your sites from the edge on a schedule, watches certificate expiry, and alerts you when a site stops answering.

In plain English — A watchtower for your websites. It checks each one is answering and its security certificate is still valid, and tells you the moment something goes wrong.

• Scheduled probes from the edge
• Certificate expiry warnings before it bites
• +2 more

Checks each web request for attacks before it reaches your site.

In plain English — A security guard for your website. It reads every incoming request and turns away the ones that look like attacks before they ever reach your server.

• Common-attack rules on
• Your own rules
• +2 more

A check that tells Zipper a visitor is a person — not a silent token.

In plain English — A quick check that proves a visitor is a real person, not a bot. Visitors tap a small widget; your site gets a one-time token confirming they're human.

• Widget on your page
• Browser signals plus a small puzzle
• +2 more

Slows or stops HTTP floods from one address. Not Magic Transit.

In plain English — If one computer floods your site with requests, Zipper starts answering 'too many requests' so everyone else can still get through.

• Cap requests per IP
• On by default
• +2 more

Limits how often an API can be called, and checks tokens and body shape.

In plain English — A traffic cop for your APIs. It counts requests, checks access tokens, and rejects bodies that don't match the shape you allowed.

• Token checks
• Limits per route
• +2 more

Puts extra visitors in a waiting line when your site is too busy.

In plain English — When your site is overloaded, extra visitors wait in a branded virtual line with an estimated wait instead of crashing your server.

• Branded holding page (headline, message, accent, logo)
• Position + estimated wait
• +5 more

Eighteen engines scan every upload in flight and hold the bad ones before they touch disk.

In plain English — An antivirus scanner at the gate. Every upload is checked for malware, hidden payloads, and leaked secret keys before it is stored or shared.

• Eighteen engines, detonation-free
• Entropy sweep for packed payloads
• +6 more

Lets signed-in teammates reach a private app. The public does not see the origin.

In plain English — A sign-in wall in front of your private apps. Only teammates in your workspace (with two-factor if you require it) get in, and the origin server stays hidden.

• Sign-in in front
• MFA grants
• +2 more

Roles, allow and deny policies, conditions, a policy simulator, and “who can reach this?” reports — on Palace roles. Not an external identity provider.

In plain English — The rulebook for your workspace: decide which teammates, keys, and apps may touch which services, under which conditions — with a plain-English report of who can reach what, and a test run before you publish.

• Workspace → project → service hierarchy
• Allow and deny policies with conditions
• +4 more

Request extra rights with a justification, get approved by a named person, receive a pass that expires on its own. Not standing admin keys.

In plain English — Need admin rights for an hour? Write down why, get a named approver to clear it, and receive a pass that expires by itself — leaving a full paper trail behind you.

• Justification required on every request
• Named approval — never self-approve
• +4 more

Shows requests, blocks, cache hits, and human checks for your workspace only.

In plain English — Your private logbook: who visited, what got blocked, how caching is doing — visible only to your workspace.

• Live request log
• Threat timeline
• +2 more

Counts visits, top pages, and referrers for the sites Zipper hosts — recorded at the edge, private to your workspace.

In plain English — A private visitor log for your website. It shows how many people came, which pages they read, and where they arrived from — without following anyone around the internet.

• Counts visits at the edge, no client script
• Top pages, referrers, and device classes
• +2 more