Visitor Queue

What it is

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.

Cloudflare analogue: Cloudflare Waiting Room. SLA 99.99% · p99 12ms. Operators tune the budget. Admins attach queues to paths.

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

How it works

When concurrent origin sessions exceed the budget, extra visitors see a holding page with estimated wait.

Signed-in operators can bypass. Attach one queue per path.

Use cases

Concrete ways teams use this service on day one.

Set it up in the dashboard

Dashboard → Services → Visitor Queue. Name, path, starting queue size (usually 0).

API

Control-plane: GET|POST /api/v1/waiting. 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.

curl -sS -X POST https://tinyzipper.com/api/v1/waiting \
  -H "Authorization: Bearer tz_live_YOUR_TOKEN" \
  -H "Idempotency-Key: $(uuidgen)" \
  -H "Content-Type: application/json" \
  -d '{"name":"Checkout","path":"/checkout","queue_size":0}'

const res = await fetch("https://tinyzipper.com/api/v1/waiting", {
  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

Set the budget to measured origin capacity, not a guess. Watchtower shows queue depth.

• ▸SOC 2
• ▸Queue fairness

Runbook

Set the session budget to origin capacity. Enable estimated wait. Bypass only signed-in operators.