Introducing Sazabi BYOC: Run Sazabi in Your Own Cloud

Today, we're excited to announce Sazabi 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 are kept in a database that your organization owns. Everything else is the same: Sazabi's Automatic Issue Detection, lightning-fast Log Search, live Dashboards, and Cyber Defense features are all available to you like normal. There's also no maintenance overhead for your team - Sazabi operates and runs everything. BYOC is available on AWS starting today, with GCP and Azure variants coming soon. We're onboarding our first customers now. Book a demo to get started.

Why BYOC? Why Now?

Today's security environment is perhaps the most challenging we've ever encountered in the software industry. Engineering leaders at every organization, from early-stage startups to large enterprises, have been quick to respond.

One part of this response, which Sazabi has directly observed, involves scrutinizing vendors and data custodians. The importance of this is underscored by last week's Railway incident. Railway's platform was down for more than 60 hours during what it later disclosed as a security incident, and it told customers to rotate the credentials stored in their Railway environment variables. The lesson is clear: every vendor that holds your data expands your attack surface.

For observability and security, this problem is particularly severe. Sazabi ingests a single type of data: logs (or more generally, event streams). The company was founded on the position that "logs are all you need," which implies something profound. Log data is extremely rich and valuable, especially when combined with AI agents that can process this data and derive insights efficiently at scale.

In a security-challenged environment, this advantage becomes a risk. Logs reveal how your system is architected and how it operates. Log data often holds sensitive information such as user IDs, request payloads, and stack traces. Occasionally, it includes tokens and personal data that haven't been properly redacted.

Agent traces are even more sensitive than traditional application or infrastructure logs. Sazabi ingests these too, converting them to logs at intake.

In other words, the data that Sazabi ingests, processes, and stores on behalf of our customers is extremely sensitive.

While Sazabi has gone to great lengths to secure our managed solution - including a SOC 2 Type II report and annual third-party penetration tests - we recognize that the most surefire way to guarantee the security of customer data is to allow customers to store that data themselves.

We also think this is where the industry is heading. Keeping logs in your own cloud used to be for banks, healthcare, defense, and other regulated industries. No longer.

Going forward, Sazabi believes the industry will begin to shift from storing data across many small third-party clouds and platform-as-a-service providers (such as Render, Vercel, and Railway) to "onshoring" that data in larger, trusted clouds controlled directly by organizations themselves.

How It Works

With BYOC, the parts of Sazabi that touch your raw logs move from our cloud to yours. As usual, your systems send logs to an OpenTelemetry-compatible intake address - except this time, the service lives within your own network. Parsing, enrichment, and indexing also run in your own cloud. After logs have been processed, they're stored in a database account that your organization owns, under your own retention policies. (A secondary benefit of BYOC is that you can configure whatever retention you want.)

Everything else - the Sazabi dashboard, our agent, notifications, integrations, billing, etc. - continues to run in Sazabi's cloud. Your team can use Sazabi exactly the same way, through the same UI, CLI, API, and MCP. You also don't need to register your own OAuth applications with essential third-party platforms like GitHub and Slack.

Importantly, BYOC doesn't require you to take on operations. Although these components run in your cloud, Sazabi's team continues to deploy, upgrade, monitor, and support them, just like we do for every Sazabi customer today.

We do this through a deployment role that your team creates during onboarding. The role can only manage the resources it creates for Sazabi, which are tagged and fenced off from the rest of your account. The broader access needed for initial setup is removed as soon as setup finishes. After that, most updates are rolled out by a deployment controller that runs inside your BYOC deployment.

Passing Security Review

We designed BYOC around the questions we know your security team will ask.

First, you review and approve the access Sazabi gets before anything is provisioned in your cloud. No one at Sazabi has standing access to your account. Instead, changes go through an automated approval process, and the broader setup access is removed once your deployment is up. You can also revoke our access at any time. While it's revoked, the Sazabi team won't be able to operate or update the service, and your data stays exactly where it is.

We're also upfront about what data still reaches our cloud. Some vendors promise self-hosted or BYOC offerings without making it clear that metadata or control plane data is sent back home. Not Sazabi. With BYOC, Sazabi's control plane continues running in our cloud, which means some data is sent back to us. This includes:

• The results of searches and investigations
• Sample log lines that appear in issues
• Prompts containing log excerpts, sent to our model providers when the agent investigates (these providers are contractually barred from training on your data)
• Member names, emails, and activity
• Operational data required to keep the service up and running, which can include log content
• And more

The full list is available in our docs.

Last but not least, if you ever decide to end your relationship with Sazabi, your logs stay with you. There's nothing to export or wait for - they already reside in a database your organization owns. We've worked very hard to make it easy to onboard to Sazabi. It should be easy for you to offboard, too.

Sazabi for Cyber Defense

BYOC allows customers to bring AI-native observability to their organizations with minimal risk. But Sazabi can also bolster your cyber defenses:

• cve.now: Sazabi's native, first-party integration with cve.now - a free vulnerability feed we launched last week - gives the Sazabi agent real-time access to new CVEs and security advisories, and lets it check your project's dependencies against them to find out if you're affected. It's on by default in every project.
• Security Scans: Sazabi scans your connected repositories for security gaps and flaws that attackers could exploit. Each confirmed vulnerability is surfaced to your team the way they've come to expect: as a regular Sazabi issue.

Most importantly, Sazabi's Automatic Issue Detection extends to security. Sazabi can flag unauthorized activity, exploit attempts, credential stuffing, and other unwanted behavior as it shows up in your log stream. This works exactly the same way as Sazabi's Automatic Issue Detection for bugs, outages, and reliability issues, and our team is steadily expanding the security signals Sazabi detects and investigates.

Pricing and How to Get Started

Sazabi BYOC is relatively painless, but it does require some upfront lift from both our team and yours. Hence, we're reserving this option for customers that are committed to partnering with Sazabi over the long term.

BYOC requires an annual agreement, and because the service runs in your cloud, you're responsible for any cloud costs incurred. Sazabi's BYOC pricing reflects this: customers that opt for BYOC receive no charges for log ingestion, storage, retention, or queries.

To learn more about Sazabi and our BYOC offering, book a demo here. Bring your security or infrastructure team. We'll break down Sazabi's architecture, show you exactly what runs in your cloud versus ours, and walk through the access we need.

We're excited to bring AI-native observability and security to your cloud!

Sherwood Callaway
CEO & Founder
sherwood@sazabi.ai