What's new in Sazabi this month
October brought Sazabi 1.0, with dashboards and log search built on the logs you already send. It also brought cve.now, a free vulnerability feed for agents.
✨ Featured

Sazabi 1.0 is here
Sazabi 1.0 is here! We're excited to announce that Sazabi is officially out of public beta. You can sign up and get started in about ten minutes without talking to a human. Just paste this prompt into your coding agent:
Set up Sazabi: run `npx -y @sazabi/cli start` and follow what it prints.
Automatic issue detection, Sazabi's core feature, is ready for general use and on by default for every project. It finds issues in your logs without you setting up monitors, and gives each one its impact, root cause and a suggested fix.
Read announcement
🔒 Cyber defense and threat detection
BYOC
Sazabi now officially offers BYOC (Bring Your Own Cloud)! With BYOC, the part of Sazabi that receives, processes and stores your logs runs in your own cloud account, and your logs stay in a database your organization owns. Sazabi still runs and operates all of it, and Automatic Issue Detection, Log Search, Dashboards and Cyber Defense all work as usual.
Read the BYOC announcement
cve.now: a free vulnerability feed for agents
Sazabi launched a free security tool, cve.now, which merges sources such as the CVE List, GitHub Advisory Database, OSV, NVD and CISA KEV into one entry per vulnerability. No login or API key is required. Sazabi customers benefit from cve.now automatically: Sazabi automatically subscribes to the cve.now feed, cross-references it with your stack, and creates new issues when you're exposed. Also, the cve.now connector is on by default, so Sazabi's agent can look up CVE information on the fly.
Read the cve.now announcement
Security scans for your code
Sazabi scans code in your project's connected repositories for vulnerabilities and files confirmed findings as issues over time, following your delivery rules. It's on by default, and an owner or admin can turn it off per project in Settings > Code.
Read the security review guide
⚡ More improvements
Dashboards built from your logs
Ask the Sazabi agent for a dashboard, or create one with the CLI, API, MCP or Terraform, with no separate metrics to set up. Every project also includes two built-in dashboards, Issues & alerts and Log health.
Read the dashboards guide
Log search for you and your coding agent
Query your logs from the CLI, API or MCP to dig deeper into an issue Sazabi surfaced. Questions about recent logs read up to the moment you ask, so an investigation sees the newest lines.
Read the log search guide
Hand an issue to your coding agent
Each issue has a prompt you can paste into Claude Code, Codex or Cursor. It tells the agent to check Sazabi's analysis against your live logs, fix the code and open a pull request linked back to the issue.
See how it works
Status sync with your issue tracker
Turn on Status mapping, and resolving, ignoring or reopening an issue updates its Linear, Jira or GitHub Issues ticket. Moving a Linear or Jira ticket updates the issue too.
OpenTelemetry traces
Point your trace exporter at the OpenTelemetry Traces log source. Spans and their exceptions become searchable, so a trace ID finds a request's spans, exceptions and logs.
Set up OpenTelemetry Traces
🔧 Smaller updates
- Change an issue's severity with a short note from the dashboard, CLI, API, SDK or MCP.
- Sign-in now asks for a code sent to your email first, with your password as an option.
- New users with a verified company email can join their team's existing organization.
- Sazabi checks existing issues first, and two investigations in a project that find the same problem at once fold into one issue.
- If your rules send issue updates to Slack or Microsoft Teams, a reopened issue now posts there as a new alert.
💬 We'd love to hear what you think! Just reply to this email with any questions or feedback.