Git-connected sites
Site Hosting
Site Hosting builds from your repository. Each branch gets a preview hostname. Production attaches to The Crown automatically, with rollback to the last healthy build. This is a Cloudflare Cloudflare Pages alternative included on every Zipper plan.
Cloudflare analogue: Cloudflare Pages
What it is
Site Hosting builds from your repository. Each branch gets a preview hostname. Production attaches to The Crown automatically, with rollback to the last healthy build.
Cloudflare analogue: Cloudflare Pages. SLA 99.95% · p99 40ms. Admins connect the repository. Viewers may inspect preview URLs.
- ▸Git deploys
- ▸Preview hostnames
- ▸Functions on routes
- ▸Instant rollback
How it works
Connect a git branch. Each push builds; production attaches to The Crown. Previews get their own hostname.
Rollback restores the last live build.
Use cases
Concrete ways teams use this service on day one.
Next.js marketing site
Repo on GitHub, production on www.
- Framework Next, Node 22, auto-deploy on, preview URLs on. Production URL https://www.example.com.
Set it up in the dashboard
Dashboard → Services → Site Hosting. Connect site name, branch, production URL.
API
Control-plane: GET|POST|DELETE /api/v1/hosting. 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.
Connect a site
curl -sS -X POST https://tinyzipper.com/api/v1/hosting \
-H "Authorization: Bearer tz_live_YOUR_TOKEN" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"name":"www","branch":"main","production_url":"https://www.example.com"}'List the same resource in JavaScript
const res = await fetch("https://tinyzipper.com/api/v1/hosting", {
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
Pin production to main or production. Do not auto-deploy from feature branches.
- ▸SOC 2
- ▸Git-signed
Runbook
Pin the production branch. Roll back from the last live build if a deploy fails health.
Next: Job Queues · All docs · Create a free account