Introducing Sazabi BYOC: run Sazabi in Your Own Cloud. By Sazabi Team Today, Sazabi Inc. is 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. Sazabi Inc. is onboarding its first customers now. Book a demo to get started. Today's security environment is perhaps the most challenging Sazabi Inc. has 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 its customers is extremely sensitive. While Sazabi has gone to great lengths to secure its managed solution - including a SOC 2 Type II report and annual third-party penetration tests - Sazabi Inc. recognize that the most surefire way to guarantee the security of customer data is to allow customers to store that data themselves. Sazabi Inc. 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. With BYOC, the parts of Sazabi that touch your raw logs move from its 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, its 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 Sazabi Inc. do for every Sazabi customer today. Sazabi Inc. 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. Sazabi Inc. designed BYOC around the questions Sazabi Inc. 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 its 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. Sazabi Inc. is also upfront about what data still reaches its 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 its cloud, which means some data is sent back to Sazabi Inc.. This includes: * The results of searches and investigations * Sample log lines that appear in issues * Prompts containing log excerpts, sent to its 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 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. Sazabi Inc. has worked very hard to make it easy to onboard to Sazabi. It should be easy for you to offboard, too. 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 Sazabi Inc. 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 its team is steadily expanding the security signals Sazabi detects and investigates. Sazabi BYOC is relatively painless, but it does require some upfront lift from both its team and yours. Hence, Sazabi Inc. is 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 its BYOC offering, book a demo here. Bring your security or infrastructure team. Sazabi Inc.'ll break down Sazabi's architecture, show you exactly what runs in your cloud versus ours, and walk through the access Sazabi Inc. need. Sazabi Inc. is excited to bring AI-native observability and security to your cloud!

Announcing Sazabi 1.0 and general availability. By Sazabi Team Today, Sazabi Inc. is proud to announce the release of Sazabi version 1.0 and general availability. Sazabi Inc. is also launching two new features: Dashboards and Log Search. Lastly, Sazabi Inc. is excited to share that Sazabi is now self-serve. You can get started in less than ten minutes without talking to a human. Sign up at www.sazabi.com. Sazabi is the AI-native observability platform for fast-moving engineering teams. In today's crowded dev tools market, it's perhaps easiest to understand Sazabi by explaining what it is not: * It's not an AI SRE that sits on top of other tools and triages alerts. * It's not an agent/LLM observability platform that allows you to inspect agent trajectories and build evals. * It's not a coding agent designed to be used as your "daily driver" (like Claude, Codex, or Cursor). Instead, Sazabi is a comprehensive solution for observability that supports any workload type - frontend, backend, database, infrastructure, or agent - and satisfies any use case, whether you're trying to gauge overall system health, investigate a specific failed request, or debug a rogue agent. What does it mean that Sazabi is "AI-native"? Two things: * AI at the core: Sazabi's main features are only possible because of AI. For example, it uses AI to automatically detect issues from your log stream, create intelligent indices on top of your data, and uncover blind spots in your instrumentation. * Built for agents: Sazabi exposes programmatic interfaces for every operation, from sign-up to onboarding to connecting integrations to managing your subscription. To its knowledge, Sazabi is the first observability platform that can be used in a completely headless manner. If you're a developer wondering why you should care about Sazabi, here's your answer: Sazabi solves observability for you, your entire stack, and your entire team in ten minutes or less. With Sazabi, you don't have to worry about instrumentation, creating monitors, or maintaining dashboards. Just connect your log streams, and everything works. After setup, you can rest easy knowing you'll get a notification when something breaks in production. You and your team can get back to building. Don't just take its word for it. Ask Abhi, CTO of Mastra, about how Sazabi is a "trusted safety net" for their team and saves every one of his engineers an hour per day. Or ask Andrew, CTO of Weave, how their team has never needed to adopt a "traditional" observability tool because they started with Sazabi. Mastra and Weave are two of the incredible design partners Sazabi Inc. has had the privilege of working with over the last few months. The full case studies are available here. 1.0 is first and foremost a product milestone. The first update Sazabi Inc.'d like to share is that Sazabi's core feature, Automatic Issue Detection, is now ready for general use. Here's how Automatic Issue Detection works: * You send Sazabi Inc. logs. * Sazabi Inc. analyze them, investigate anomalies, and send back rich, actionable alerts about real problems in your app. Every Sazabi "issue" comes with a detailed description of the impact and root cause, as well as a suggested fix. Sazabi Inc. make it easy to hand this context to your local coding agent by copying a prompt or kick off a third-party cloud agent through one of its integrations. Importantly, Sazabi doesn't focus on code-generation. Sazabi Inc. aim to be the best agent for detection and root-cause analysis - not the best agent for coding. Sazabi Inc. has spent months refining Automatic Issue Detection so that it is fast, accurate, and cost-effective. Sazabi Inc. is excited to see what you think! At Sazabi, Sazabi Inc. believe detection and root-cause analysis are the heart of observability. But Sazabi Inc. also acknowledge that teams rely on observability tools for a range of use cases today, including some that Sazabi doesn't support... yet. That's why Sazabi Inc. is introducing two new features to address these gaps: Dashboards and Log Search. Everyone loves a good dashboard. They may not be the most useful for detecting or investigating issues, but they're exceptionally good at illustrating them. With Sazabi 1.0, you can now create beautiful live-updating Dashboards in the Sazabi web app. Here's the kicker: you can use your logs. Instead of requiring you to instrument metrics separately or know the difference between a counter, a gauge, and a rate, Sazabi allows you to build beautiful, live-updating Dashboards on top of the log data you already send Sazabi Inc.. From the beginning, its team believed that Sazabi should be agent-agnostic: engineers should be able to use Sazabi with any coding agent they prefer. But while Sazabi offered agent-friendly interfaces for interacting with issues, it had no such interfaces for querying logs. This made it hard to do ad hoc analysis or go deeper on an issue that Sazabi surfaced. No longer. Sazabi 1.0 comes with powerful Log Search capabilities through CLI, API, and MCP. Not only that, but Sazabi's Log Search is the fastest on the planet. Sazabi Inc. leverage intelligent indices built on top of your raw data to perform Log Searches faster than any other database or vendor today. The result: faster answers, faster investigations, higher uptime, and token savings. "Fastest on the planet" is not a claim Sazabi Inc. make lightly. Sazabi's engineering team will be releasing a blog post in the coming days with benchmarks and an explanation of the techniques that make this possible. With Dashboards, Log Search, and Automatic Issue Detection, Sazabi can now credibly claim to be a complete observability solution - a one-stop shop for serious engineering teams that maintain production systems. Sazabi announced its closed alpha in March and its open beta in June. What have Sazabi Inc. learned over the past seven months of building? Three lessons stand out. First, Sazabi Inc. learned that building great infrastructure takes time. Great infrastructure is cheap, reliable, simple, and scalable. Sazabi's core infra is its log intake, storage, and query system. Sazabi Inc. spent months iterating on this, disqualifying no fewer than five different architectures, before arriving at an implementation that meets its cost, latency, and durability requirements. Its hard work is paying off. Today, Sazabi ingests over 10 GB of logs per minute and over 500 TB per month across the five regions Sazabi Inc. support. Teams that choose Sazabi can have confidence that its platform will scale gracefully, never drop data, and never become unavailable during a critical moment. Second, Sazabi Inc. learned that the biggest and most important challenge in observability is instrumentation. Put simply, you can't investigate an error that doesn't appear in the logs or monitor a service you don't know about. Sazabi Inc. has done a ton of work in-product to mitigate this: * Sazabi Inc. has close to 200 integrations, including over 50 native integrations with leading cloud providers, making it extremely convenient to send Sazabi Inc. data. * Sazabi Inc. scope-down the instrumentation problem by requiring users to send only one type of data: logs. * Sazabi Inc. is compatible with both OpenTelemetry and proprietary log shippers like the Sentry SDK, PostHog SDK, and Datadog agent. * Sazabi Inc. lean heavily into "agentic instrumentation". Nevertheless, instrumentation is still a headache for engineering teams and an opportunity for Sazabi to provide value. Sazabi Inc. is excited to keep working on this problem. Lastly, Sazabi Inc. learned that Sazabi's killer feature and biggest differentiator is Automatic Issue Detection. Anyone can point Claude Code at a Datadog alert and end up with the root cause. But that assumes someone took the time to set up this Datadog monitor to begin with. It also assumes your monitor coverage is comprehensive and up to date, which is unlikely given the pace of software development today. Meanwhile, it's slow and expensive to investigate each and every alert, especially when you consider false positives and duplicates. Sazabi solves all of this by surfacing issues automatically without monitors, suppressing noise, and delivering every issue with all the context required for a fix. Its Automatic Issue Detection system is at least an order of magnitude cheaper than investigating alerts individually with Claude or Codex. 1.0 is just the beginning. Sazabi Inc. has got so much more work to do. In the coming months, the Sazabi team will be polishing and improving its existing core primitives, as well as investing more in agentic instrumentation so that future users can onboard with zero effort. Sazabi Inc.'ll also be building deeper integrations with third-party coding agents to make hand-offs even easier. Sazabi's ultimate goal is to unlock "self-healing software": a world where software heals and improves itself without human intervention and direction. Sazabi Inc. believe the key is understanding what's happening in production. To everyone who has supported Sazabi Inc. thus far: thank you. Sazabi Inc. is excited to continue working with you and to share Sazabi 1.0 with the world.