Open Observability

Your data. Your cloud. Your AI. Our observability.

Open standards were supposed to fix observability. OpenTelemetry arrived, vendor lock-in was supposed to end, and engineering teams were finally going to own their instrumentation. The only problem is that open instrumentation feeding into a closed platform is still lock-in. It is just one layer deeper than before.

Your telemetry is collected openly. Then it is ingested into a proprietary store, indexed in a proprietary format, queried through a proprietary interface, and priced in a way that grows faster than your infrastructure. The data left your environment the moment it arrived.

Open should mean open all the way down

Tsuga is built on open object storage and open file formats. That means your data is readable and portable independent of any vendor relationship. It means you are not betting your operational intelligence on a single company's continued existence, pricing decisions, or rate limit policies.

It also means no query caps. No tiered access to your own data. No penalty for querying more because your agents are doing what you built them to do. Your engineers, your AI agents, and your tools query everything, all the time, without asking permission.

And because the underlying storage is open, you can connect it to everything else in your environment. Your business data. Your source code. Your BI tools. Observability stops being a silo and starts being part of how your whole organisation understands what is happening.

What genuinely open observability makes possible

When the data layer is truly open, the economics change completely. Teams start monitoring environments they currently cannot justify the cost of monitoring. Staging environments get instrumented. Development gets real production context fed back into it. AI agents investigate incidents using data that never left your perimeter.

The question most teams have quietly accepted as unanswerable turns out to have a straightforward answer. You cannot see enough because the platform you are using makes seeing everything too expensive. Change the platform, and the constraint disappears.

Three things we believe

Open formats. Your data is yours in a format you can read, move, and build on. No proprietary schema, no vendor dependency.

Open access. No rate limits. No query caps. No tiered pricing that penalises you for actually using what you are paying for.

Open ecosystem. MCPs, CLIs, and APIs built for how engineering teams work today, with any LLM, any agent framework, any coding tool. We meet your stack where it is.

Who this is for

Teams who took open standards seriously and are tired of watching open instrumentation disappear into a closed system. Organisations preparing for AI-scale data volumes who need economics that do not collapse when usage grows. Developers who want to build on their observability data, not around it.