The security brief your clients actually read.
It pulls CISA's list of actively-exploited vulnerabilities, keeps the ones that affect software small businesses run, and rewrites each in plain English — using a model that runs entirely on your own machine.
The problem
Small businesses don't read CVEs. They skim. Security advisories are written for engineers — full of jargon, severity scores, and exploit detail that means nothing to the person who owns the bakery.
AlertCadence translates. It takes the same advisories a security team reads and turns each one into three plain sentences: what happened, why it matters to your business, and what's being done about it.
How it works
Four steps, all running on your own hardware. No cloud API, no account, nothing to leak.
Pulls CISA's Known Exploited Vulnerabilities feed — every item is already confirmed exploited in the wild.
Keeps the last 30 days and the vendors small businesses actually run. Ransomware-linked items rank first.
A local open model rewrites each advisory into What happened / Why it matters / What we're doing.
Renders one clean, white-labeled brief you review and send. (PDF, email & scheduling on the roadmap.)
Why a local model
Privacy
The model runs on your own machine with Ollama. Your client list, the advisories you process — none of it is sent to anyone's API.
Cost
Because the model is local and open-weight, generating a brief costs nothing — no per-token bill, no usage meter, no surprise invoice.
Voice
Built on the same plain-English philosophy as The Security Dictionary — it says "we're patching this," not "CRITICAL VULNERABILITY DETECTED."
This week's issue, generated from live CISA data by a local model.
Open this week's brief →