Table of contents
I am excited to announce the release of Parseable 2.0. This release (rather series of releases) is truly a labour of love.
In this post, I’ll go over some of the most important updates in this new release. I’ll also explain the what and the why of the product, how we look at the observability ecosystem and what is next on our roadmap.
Before we get started, here is the TL;DR of Parseable 2.0
Unified observability platform for all telemetry signals.
Brand new UI.
OpenTelemetry native.
Incredibly fast.
Text search capabilities.
Feature-rich OSS and enterprise-grade features for production use cases.
Background
Over the last 6 months, we spoke to 100s of stakeholders - customers, users, community members, SRE practitioners. RoI on the observability investment was a major concern across the board. But, it was very clear that people want to centralise their observability platform, reduce the tool sprawl and the complexity that comes with it.
We also saw significant interest in OpenTelemetry. OTel's interest in our experience comes from the fact OTel allows vendor independent instrumentation and formats. This makes stakeholder’s lives much easier, should they want to change vendors.
Finally, a large chunk of the stakeholders are looking to keep their O11Y data within their firewalls. This helps them manage the cost efficiently, allows unparalleled security and privacy, and lets them leverage their investments in cloud and security infrastructure.
We went back to the drawing board, armed with these insights, and Parseable 2.0 is the outcome. Technically, we’re already at v2.2.0, but after months of testing and stabilising, this feels like the right time to officially announce the product.
Unified observability
According to a recent Gartner webinar, observability spending is rapidly rising, with 36% of enterprises now investing over $1 million annually, a figure growing by as much as 40% year-over-year. Over half of these costs are dedicated solely to log management, and complexity continues to mount as many organizations juggle 10-20 or more observability tools simultaneously.
Fragmented tools create:
Operational delays: Engineers waste 2–4 hours per incident correlating data across interfaces
Security gaps: Many organisations struggle to detect multi-stage attacks due to siloed telemetry
Scalability limitations: Tool-specific data ingestion caps hinder cloud-native expansion
Unified observability has emerged as a critical paradigm shift in IT operations. This is driven by the convergence of cost considerations, platform engineering practices, advancements in telemetry standardisation (read OTel), and growing enterprise demand for holistic system visibility.
Consolidating metrics, events, logs, and traces (MELT data) allows real-time insights into complex, distributed environments across the signal spectrum. Users can correlate different signals as needed. A single platform also allows freedom to plug this data into other systems.
We wrote extensively about how
With 2.0, we are one step closer to achieving Unified Observability.
There are several improvements in ParseableDB to allow native compatibility with all OTel signals, Prism is at the core of our unified observability proposition.
Prism: Built for unified observability
Prism is the developer-first UI built for the ParseableDB. Combined, ParseableDB and Prism are the unified observability platform, purposefully designed to tackle the fragmentation plaguing modern observability stacks.
With a tightly integrated experience and lightning-fast interface, Prism allows extracting value out of MELT data in a single interface. Read more for a deep dive on Prism.
Why Now?
Unified observability has transitioned from a technical initiative to a strategic imperative. According to Grafana’s Observability Survey, 83% of organizations that have centralized observability report saving time or money, with many also seeing improvements in incident response and developer productivity.
As platform engineering matures and OpenTelemetry becomes ubiquitous, enterprises must prioritize:
AI-driven automation to handle exponential telemetry data growth
Vendor consolidation to eliminate ~$1.2M/year wasted on redundant tools
Business-outcome alignment to prove observability’s ROI beyond IT metrics
The 2025 landscape demands a paradigm shift, from monitoring systems to enabling innovation through observability-driven insights. Organisations that fail to unify their MELT data pipelines risk operational paralysis in an increasingly complex, AI-augmented IT ecosystem.
OpenTelemetry native
OpenTelemetry (OTel) has rapidly evolved into the foundational standard for collecting, processing, and exporting telemetry data in modern IT environments. As an open-source project under the Cloud Native Computing Foundation (CNCF), OTel now stands as the second-largest CNCF project behind Kubernetes, reflecting its critical role in observability strategies worldwide.
Parseable 2.0 takes this commitment to OpenTelemetry a step further. We’re proud to be among the few platforms that are OpenTelemetry-native by design, not as an afterthought. Our goal is to build a unified observability platform that speaks the language of open standards, without requiring proprietary agents or vendor-specific formats.
No Proprietary Agents: Parseable promotes the use of standard open-source agents; we don't believe in locking you into a closed-source agent to ingest data.
Traces & Metrics in OTel Format: Today, traces and metrics are supported only in OpenTelemetry format. We’ve made a conscious decision to adopt OTel first, and we’re building support for logs and profiling with the same philosophy.
Built for Compatibility: Whether you’re using OTel SDKs, the OTel Collector, or third-party instrumentation, Parseable integrates natively with your telemetry pipeline.
Future-Ready Architecture: As OTel expands into GenAI and continuous profiling, Parseable is positioned to ingest and analyse all forms of OTel native data.
Data Volume Management: As organisations adopt OTel, telemetry data volumes can increase 4–5x, creating challenges for cost management and storage, something Parseable addresses head-on with S3-native storage and efficient columnar data formats.
Implementation Complexity: Deploying OTel at scale still requires thoughtful pipeline design. Parseable simplifies this with native compatibility and flexible ingestion paths.
Integration with Existing Systems: While traditional platforms require custom glue code, Parseable is designed to slot seamlessly into existing OTel-based setups.
The OTel ecosystem is maturing rapidly, with detailed specifications and robust implementations. According to a 2025 EMA Research Report, nearly half (48.5%) of organisations already use OTel, and another 25.3% plan to adopt it soon. Over 46% report a greater than 20% ROI from OTel adoption, and 84% of organisations that reduced costs with OTel saw at least a 10% decrease in observability expenses.
OpenTelemetry is no longer just a trend, it’s the backbone of modern observability. Standardising telemetry collection and processing drives operational efficiency, reduces cost, and accelerates innovation.
Performance
With Parseable 2.0, we’ve pushed the limits of query speed and ingestion scale while staying true to our architecture-first approach. Below are the key technical elements driving performance improvements:
Distributed Query Engine
Parseable 2.0 introduces a fully distributed query execution model. Query nodes are stateless and horizontally scalable, meaning any node can independently serve requests without requiring coordination or state syncing. This reduces bottlenecks and simplifies scaling under heavy workloads.
Vectorised Execution
We now use SIMD-powered vectorised query processing, allowing our engine to process data in chunks and use CPU cache more effectively. This leads to faster execution with significantly lower CPU cycles, especially for analytical queries that scan large volumes of observability data.
Lightweight Compute with Rust
The entire system is written in Rust, resulting in a minimal compute and memory footprint, up to 50% less than comparable systems. Combined with object storage-backed durability, Parseable avoids heavyweight replicas on local disks and expensive SSDs.
On-Demand Indexing
Instead of bloating ingestion with full upfront indexing, Parseable lets users define indexes as needed. This reduces write amplification and storage overhead, while still enabling sub-second lookups when required. It’s a smart tradeoff for high-ingest, low-query data like logs.
Object Storage Native
Data is stored in cloud-native object stores (like S3 or GCS) with no compromise on query performance. Local staging is used just for caching, keeping the core engine stateless and making Parseable ideal for cloud-native and hybrid setups.
Enterprise offerings
Core infrastructure projects, especially those that deal with data and need to guarantee data protection and reliability of the highest order, take time to build. Over the last 3 years while building ParseableDB, we’ve seen a wide range of edge cases, bug reports, weird behaviour, and more.
Parseable 2.0 is backed by several hundred production deployments and months of rigorous testing for stability, data reliability, and performance.
The time is right to create an enterprise-grade offering, built on the solid foundation of AGPLv3 ParseableDB. With a dedicated, well-defined Enterprise offering, we’ll be able to serve serious, mission-critical users much better, while improving the sustainability of the OSS product. It helps us derive some value from our work without pulling the rug from under the community.
Sustainable open source. No drama. No bait-and-switch. Just fast, efficient, observability.
Parseable OSS vs. Enterprise Edition
Parseable OSS
High performance.
Single binary with built-in Prism.
RBAC and OIDC integrations.
Regular updates and feature releases based on community feedback.
Perfect for individuals, smaller teams, and non-mission-critical deployments.
Enterprise Edition
Everything in OSS, plus
Hardened, stable builds.
Searching on demand.
Distributed query support.
Built-in schema detection for log formats.
AI Native summarisation, alerts, and correlation (coming soon, talk to us for a preview).
High touch onboarding, O11Y data modeling,g and 24/7 support.
Predictable pricing model.
How to access Parseable Enterprise
Drop us a note at sales@parseable.com to set up a quick discovery call and discuss your needs.
Want to try before you buy? You can check out the enterprise features at demo.parseable.com.
Whether you’re an indie developer building the next big thing or an enterprise scaling observability across a global infrastructure, we’ve got you covered. Let’s build something awesome together!
Closing notes
We're thrilled to announce the arrival of Parseable 2.0. Say goodbye to tool sprawl and hello to centralized insights with our next-generation solution!
Parseable 2.0 tackles the growing challenge of managing disparate observability tools. By consolidating metrics, events, logs, and traces (MELT data), you gain a holistic view of your systems, enabling faster troubleshooting and deeper insights through signal correlation.
We've engineered Parseable 2.0 from the ground up with performance in mind. Our architecture leverages on-demand indexing and object storage for optimal efficiency and scalability.
Open Source (OSS): Get started with our powerful open-source version and experience the benefits of unified observability.
Enterprise Edition: Unlock advanced features like hardened builds, search on demand, distributed query support, AI-driven insights, and dedicated support.
Ready to experience the future of observability? Drop us a note at sales@parseable.com to learn more and get started with Parseable 2.0 today!