10 Years of Imply: From Apache Druid to What’s Next in Real-Time Analytics

A large “10” made of candles, with the Imply arrow mark as the zero, on a purple background of dots.
Animated Imply 10th birthday graphic: a large “10” made of lit candles, with the Imply arrow mark as the zero.

We’ve officially hit double digits!

Ten years ago, a few Druid-obsessed engineers asked a radical question:

What if analytics didn’t have to be slow, stale, or stuck in dashboards?

Back then, we were just a small team solving our own problem—creating Apache Druid to get real-time answers from massive streams of data. Today, Imply powers some of the fastest, most interactive data experiences on the planet.

  • Real-time dashboards? Check.
  • Subsecond search at scale? Absolutely.
  • Wild use cases no one saw coming? Every day.

Druid now fuels critical analytics at organizations around the world—and Imply has grown into a full platform that’s changing how people interact with data.

This year, we’re celebrating a decade of progress, partnership, and pushing boundaries. And we’re just getting started.

It Started With a Problem—and an Idea

Before Imply, there was Druid.

“We were trying to answer a simple question: How do you get instant answers from massive streams of data without breaking the bank? Druid was the result—and it turned out we weren’t the only ones who needed it.”
— Fangjin Yang, Co-founder & CEO

That idea—interactive queries on event data at scale—sparked a new kind of database. Apache Druid broke the mold, offering subsecond performance across real-time and historical data, all while keeping infrastructure costs in check.

It was open source from day one. And the community took it further than we could’ve imagined.

From a Database to a Movement

In 2015, we founded Imply—not just to commercialize Druid, but to reimagine what analytics could be.

“We didn’t just want to package Druid—we wanted to rethink the entire analytics experience. That meant staying open, staying developer-first, and solving real, hard problems.”
— Gian Merlino, Co-founder & CTO

Over the past decade, we’ve:

Contributed hundreds of Druid features and improvements
From Multi-Stage Query (MSQ) and schema-on-persist to async queries on S3, we’ve helped Druid mature into a true event database—built for flexible ingestion, long-term historical analysis, and real-time performance at scale—without breaking the bank.

Launched Polaris, the easiest way to run Druid in the cloud
Built from the ground up as a fully managed, cloud-native service, Polaris makes Druid accessible to any team—without the operational overhead.

Raised over $215 million from leading investors
Backed by Andreessen Horowitz, Bessemer Venture Partners, and others, we’ve scaled our team, product, and global reach—while staying true to our open-source roots.

Enabled real-time analytics at the world’s most innovative companies
From fraud detection at Ibotta to operational visibility at Reddit, our customers span finance, tech, retail, media, and beyond—powering analytics where milliseconds matter.

Grown a global community of engineers, architects, and builders
What started as a few engineers in an apartment is now a worldwide movement—20,000+ GitHub stars, 100M+ Docker pulls, and 600+ contributors later—spanning thousands of Druid users, community meetups, and Imply customers pushing the limits of what’s possible. In 2024, we brought that energy together at our first in-person Druid Summit.

And through it all, we’ve stayed true to the values that sparked this journey: performance, simplicity, and scale.

What’s next: A New Layer Is Taking Shape

As data systems grow more complex, real-time analytics and observability can’t afford to be disconnected—or slow.

We’re building a smarter foundation—one that brings speed, efficiency, and openness to the tools teams already use.

“We’re building for a world where real-time is table stakes—and observability needs a smarter foundation. That means rethinking the data layer itself.”
— Vadim Ogievetsky, Co-founder & Chief Experience Officer

We think the next 10 years will look very different from the last—and we’re excited to help shape that future.

To our Customers and the Community: Thank You

Whether you contributed to Druid, built on Imply, joined our team, or simply cheered us on—thank you. Open source only works because of the people behind it.

“It’s been amazing to see how far this community has come. Druid started with a handful of us in a tiny apartment. Now it’s powering apps we could never have imagined.”
— Fangjin Yang

This milestone is yours, too.

Here’s to the Next 10

We started with a distributed database. Now, we’re building something bigger—a new foundation for analytics when real-time truly matters.

“We built Druid on the belief that infrastructure should solve real-world technical problems. Ten years in, we’ve learned that’s just the starting point—true impact comes from solving market-defining challenges. We have the hubris to believe we’ve identified the core problem facing observability and security data teams—and we’re building the product to change the game.”
— Eric Tschetter, Chief Officer of Emerging Solutions

Thanks for riding the event stream with us. The next decade? Even wilder.

And the best part? We’re just getting warmed up.

Stay tuned.

A birthday cake decorated with the Imply arrow logo on a photo card reading “Happy 10th birthday, Imply!!!”

Related articles

More from Imply on the same topic.

Lipsum logo description
October 14, 2026

Search your Splunk DDSS archive without restoring it

Security teams often keep logs long after they have aged out of their SIEM platform’s searchable window. The data is there for investigations or audits, but accessing the data for insights can be complicated.

October 14, 2026
Security teams often keep logs long after they have aged out of their SIEM platform’s searchable window. The data is there for investigations or audits, but accessing the data for insights can be complicated.
Lipsum logo description
October 9, 2026

Claude makes dashboards now, Lumi is ready for them

This week Anthropic launched Claude Dashboards in beta. You connect a data source, ask a question in plain language, and Claude writes the queries and builds the dashboard.

October 9, 2026
This week Anthropic launched Claude Dashboards in beta. You connect a data source, ask a question in plain language, and Claude writes the queries and builds the dashboard.
Lipsum logo description
September 24, 2026

Lumi Lounge Recap: 3 Takeaways from Splunk .conf26

The Imply Lumi Lounge sat directly across the street from Splunk .conf26 and reached venue capacity on both days. Digital signs around the Colorado Convention Center pointed attendees our way with a simple message: “Federated search, done right. Full SPL. Less spend.”

September 24, 2026
The Imply Lumi Lounge sat directly across the street from Splunk .conf26 and reached venue capacity on both days. Digital signs around the Colorado Convention Center pointed attendees our way with a simple message: “Federated search, done right. Full SPL. Less spend.”
Lipsum logo description
September 13, 2026

Lumi Loglake is now generally available in Imply Lumi

Search unstructured logs in place in your data lake

September 13, 2026
Search unstructured logs in place in your data lake
Lipsum logo description
September 3, 2026

Agents don’t query like your detections do

A security team of four has run a major SIEM since February. Nobody on the team writes SPL. Nobody opens the console or looks at the dashboards. Every question goes through an AI agent, which writes the query, runs it, reads the result, and answers in plain language.

September 3, 2026
A security team of four has run a major SIEM since February. Nobody on the team writes SPL. Nobody opens the console or looks at the dashboards. Every question goes through an AI agent, which writes the query, runs it, reads the result, and answers in plain language.
Lipsum logo description
July 24, 2026

Why You Shouldn’t Have to Delete Your VPC Flow Logs

When a security incident happens, investigators almost always start with the same questions: Which systems communicated? Where did the traffic originate? What changed before the incident? Was data exfiltrated? AWS VPC Flow Logs are often the fastest way to answer those questions.

July 24, 2026
When a security incident happens, investigators almost always start with the same questions: Which systems communicated? Where did the traffic originate? What changed before the incident? Was data exfiltrated? AWS VPC Flow Logs are often the fastest way to answer those questions.
Lipsum logo description
June 16, 2026

Splunk Smartstore vs Lumi Loglake: Two Very Different Ways to Search Logs in Object Storage

One copies data back before it can be searched. The other queries it where it lives. Lumi Loglake lets Splunk teams query logs directly in object storage, including AWS S3, Delta Lake, Apache Iceberg, using standard SPL.

June 16, 2026
One copies data back before it can be searched. The other queries it where it lives. Lumi Loglake lets Splunk teams query logs directly in object storage, including AWS S3, Delta Lake, Apache Iceberg, using standard SPL.
Lipsum logo description
June 11, 2026

Supercharging Schema-On-Read: Logs in Object Storage Don’t Need a Data Catalog

Machine data architectures are rapidly changing. As telemetry volumes continue to grow and as costs rise, organizations are increasingly moving logs and other machine data into object stores such as AWS S3.

June 11, 2026
Machine data architectures are rapidly changing. As telemetry volumes continue to grow and as costs rise, organizations are increasingly moving logs and other machine data into object stores such as AWS S3.
Lipsum logo description
June 4, 2026

Imply Lumi Loglake vs Splunk Federated Search for S3

Teams are increasingly moving log data into AWS S3 to reduce costs and extend retention. Both Lumi Loglake and Splunk Federated Search to S3 help you query data in AWS S3 to lower costs, however the two technologies have several notable differences.

June 4, 2026
Teams are increasingly moving log data into AWS S3 to reduce costs and extend retention. Both Lumi Loglake and Splunk Federated Search to S3 help you query data in AWS S3 to lower costs, however the two technologies have several notable differences.
Lipsum logo description
May 21, 2026

A First Look at Lumi Loglake: Query Logs Where They Live

TL;DR: Imply Lumi Loglake is a lakehouse (separated compute/storage) architecture for unstructured logs that reduces costs from 40% up to orders of magnitude on your hardware/AWS/Azure bill used to run your SIEM/observability products.

May 21, 2026
TL;DR: Imply Lumi Loglake is a lakehouse (separated compute/storage) architecture for unstructured logs that reduces costs from 40% up to orders of magnitude on your hardware/AWS/Azure bill used to run your SIEM/observability products.
Lipsum logo description
May 11, 2026

Imply Lumi Major Release Preview: Continuing the Journey Towards Decoupled Observability/SIEM

We are getting ready to introduce the next major expansion of Imply Lumi and the observability warehouse. When we introduced the industry’s first observability warehouse, the goal was clear: decouple the observability stack by separating storage, compute, and access.

May 11, 2026
We are getting ready to introduce the next major expansion of Imply Lumi and the observability warehouse. When we introduced the industry’s first observability warehouse, the goal was clear: decouple the observability stack by separating storage, compute, and access.
Lipsum logo description
May 4, 2026

Query Lumi from Grafana: Now in Private Preview

Observability has a silo problem. Today, we’re removing another one. Imply Lumi’s Grafana Loki integration is now in Private Preview.

May 4, 2026
Observability has a silo problem. Today, we’re removing another one. Imply Lumi’s Grafana Loki integration is now in Private Preview.

Lipsum section heading

Lipsum line of text about this section.