Zaprex
/
Docs menu

Admins

Back-office and admin

Turn Zaprex on per plan or user, cap spend, choose models, read logs, and the kill switch.

Ingot admins control Zaprex in the back-office. Staff can view; admins can change. Every change is written to the admin audit log.

Who gets Zaprex

  • Enable it per plan and override it per user (enable or disable, minutes, concurrent runs, spend cap).
  • Plan limit overrides.

Spend

  • Global daily and monthly spend caps.
  • Per-user spend caps.

Models

  • The default model, fallbacks and the models users may pick for a task.
  • What is behind "Ingot" is changed on the back-office Models page.

Dashboard

Running runs, runs awaiting approval, queue depth, success rate, spend today and this month, compute minutes and top users.

Runs

Every run with its redacted run log and approval history. Admins can cancel a run.

Kill switch

One switch, with a confirmation step, that pauses Zaprex everywhere: it cancels every unfinished run, blocks new runs and makes the scheduler skip routines until it is turned off.