ladder99/clawborrator-bench repository overview

⁠clawborrator-bench

Single-tenant SaaS shell that sits in front of one customer's clawborrator-hub_v1⁠ instance. Used by Bench⁠ (the multi-operator Claude Code platform's B2B layer) to give each customer a dedicated deployment isolated by infrastructure, not by application logic.

Source: https://github.com/clawborrator/bench⁠ License: MIT

---

⁠What you get when you run this image

• An HTTP server on port 8080.
• A landing page that introduces the customer's Bench instance, shows the connected hub URL, the live hub-reachability status, and the masked prefix of the service token in use.
• A small JSON API:
  • GET /healthz — liveness
  • GET /api/bench/info — customer slug, hub URL, token prefix (no plaintext)
  • GET /api/bench/hub-status — proxies the hub's /healthz

The image is identical across customers; per-customer configuration arrives through Fly secrets (or any equivalent env-var injection).

⁠Required runtime environment

Optional: PORT (default 8080), HOST (default 0.0.0.0), LOG_LEVEL.

⁠Security posture

• Runs as uid 65532 on Chainguard glibc-dynamic.
• Service token plaintext is held in memory only; never logged, never returned by any endpoint.
• All hub traffic is HTTPS (the hub enforces it).

⁠Typical deployment

Bench's provisioning scripts (bench/provision/bench-hub-provision.sh + bench-app-provision.sh in the source tree) are the intended way to stand this up alongside a customer's hub_v1.