Try five live demosdemo.gravixar.com

Module library

Daily security watch

Every night it checks the audit log for trouble: a flood of signups, a burst of deletions, many accounts locking at once, the AI classifier going down, or inquiries stuck in place. It emails the admins when something trips and stays 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." This reads the day's activity every night and only writes when something looks wrong. Three months in, you stop reading emails for what's working and only look when there's a subject line.

Under the hood

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.

Related modules

Also in Audit and records

Bring me a real operations problem. I will show you the system running before you sign anything.

The Ops Leak Audit is the fixed-price first step: I count the hours your tools cost your team, then price the fix. Rather talk first? Book a 30-minute call. If it is not a fit, you still leave with notes you can use.