System Health

Error Reports 0

Diagnostic

Cron diagnostics run at 6pm, 9pm, 11pm and 1am Mexico time using the fixture image + production prompt at 2K resolution. Every real client generation also feeds these metrics, so the more you use the system the better the baseline gets. No magic numbers: each component's status comes from its own measured history (last 7 days). The card shows the current avg (last hour), then the baseline p50/p95 from that history, and n=recent/baseline sample counts so you can see how strong each verdict is. OK = current ≤ p95 (within historical normal). Warn = above p95 but ≤ 2×p95. Fail = > 2×p95. Observing = we have current data but no baseline yet. Idle = no current traffic but we have historical data. No data = never observed yet. Skipped steps (e.g. R2 skipped because xAI returned no image) don't count against the skipped component.

Revenue

Transactions (all time)

Disputes

Stripe chargebacks. When a customer disputes a charge with their bank, Stripe debits the amount automatically and we have a deadline to submit evidence. Every charge.dispute.* webhook is captured and a snapshot of the customer's usage (photos generated, gallery) is recorded for defense. An alert email goes to support@kruder1.com on creation.

Users

Generations