Dashboard
The same engines as /api/v1 \u2014 with keys, traces, workspace policy, and a playground behind your session.
Included surfaces
Everything you need to operate Verixet day-to-day without juggling scattered admin tools or raw curl.
- API keys — issue, scope, rotate with overlap, revoke
- Request log — latency, outcome, and metadata aligned with requests_log
- Playground — run engines with your session, not pasted secrets in the browser
- Webhooks — inbound Stripe, outbound delivery attempts where configured
- Workspace — policy mode, packs, and team-facing controls
- Billing — Stripe Checkout and portal when env vars are wired
Why it matters
One pane of glass
Operators see the same signals CI consumes \u2014 request IDs, outcomes, and engine names \u2014 without spelunking production logs first.
Session-scoped
Dashboard auth uses secure cookies; the playground calls your server-side session instead of stashing long-lived keys in local storage.
Ready for review
Export-friendly trails for security reviews: who ran what, when, and whether automation blocked a deploy.
Faster iteration
Tune snapshots and policy, then immediately re-run pre-deploy or validation from the playground before you merge the workflow YAML.
Get in
Continue with your XFlow ecosystem account, resolve the shared workspace, and keep API access segmented by scoped keys.