Operators
Integrate & deploy
TideGuard is a Worker you own. Deploy it, claim /admin, smoke-test without flooding your site, then go live when the launch checklist is green.
1. Deploy
Generate a TOKEN_SECRET on the token page (or openssl rand -hex 32), then use Deploy to Cloudflare or clone and npm run deploy. Keep the same secret for the Claim step in /admin.
- Getting started — local, Deploy button, first claim
- Deploy to Cloudflare
2. Demo mode (smoke-test safely)
After setup, origin proxy stays off — Demo mode. Exercise join → wait → admit at /demo or /wait?return=/demo in an incognito window. The control room banner offers Go live when you are ready to gate real paths.
- Protecting a domain — Demo mode → Go live
- Launch checklist — pre-production gates
3. Origin proxy & tokens
Sit TideGuard in front of your site, or verify HMAC admission tokens in your own app. Admitted visitors carry a signed token (cookie, Bearer, or query).
- Verifying admission — proxy headers vs app verify
- API —/join, /status, operator routes
- OpenAPI 3.1— machine-readable contract
4. Embed & custom UI
Use /wait?embed=1 for an iframe-ready room, or call join/status from your own front end. Site demos show the look; your Worker is the real queue.
- Simulated demos — full page, widget, API-shaped JSON
- Capabilities — full feature catalog
5. Cost before the surge
Estimate Workers and Durable Objects spend for one event with the cost calculator. Software is MIT; you pay Cloudflare for usage.