Demo atdemo.gravixar.com
Gravixar

module · audit

Daily security-watch cron

Sweeps the audit log nightly for anomalies (mass-signup spikes, DELETE bursts, lockout cascades, classifier blackouts, stuck inquiries) and emails admins when something trips. Quiet when nothing is wrong.

The right shape for ops monitoring is "email me when something is off," not "email me a dashboard every night." The security-watch cron sweeps the previous day's audit log against a small set of anomaly patterns: signup volume vs. rolling baseline, DELETE bursts beyond a per-actor threshold, lockout cascades that might indicate a credential-stuffing attempt, AI classifier blackouts (model down, fallback path hit), inquiries stuck in a state past their stage SLA.

If nothing trips, the cron exits silently. If anything trips, an email lands with the matching audit rows inlined and a one-paragraph summary of what looks unusual. Three months in, you stop reading emails for what's working and only look when there's a subject line. That's the discipline.

next step

Bring me a real operations problem. I'll show you the system before you sign anything.

30-minute discovery call. If we're not a fit, you walk with notes you can use anyway.