Celebrating 20 Years of Splunkbase and What Comes Next

In the beginning, the idea was wonderfully simple: help people solve real problems with the Splunk Platform, then make those solutions easier for someone else to find, trust and use. The early SplunkBin experience in the Splunk 2.x era even let users search for an event on Splunkbase from inside the product. A year later, the goal grew into a repository of IT problem-solving knowledge, where users could upload anonymized event types, tag them and share ways to investigate them.

That spirit is still alive. Splunkbase exists because builders like to build, practitioners like to share what works, and customers need more than raw data. They need integrations, dashboards, add-ons, connectors, agents, and domain expertise they can put to work.

Over the years, the Splunkbase experience evolved: go down the memory lane here! SplunkBin became SplunkForge, bundles became apps, Splunkbase moved to a cloud-based infrastructure with improved search, added app analytics for developers, and introduced a responsive experience. Each change reflected the same basic belief: the Splunk ecosystem gets stronger when customers and partners can package their expertise and share it with the community.

That is what we are celebrating now: 20 years of the modern Splunkbase experience and the builders behind it.

From Catalog Scale To Operational Knowledge

Today, Splunkbase brings together apps and add-ons from Splunk, our partners and our community. The site lists more than 2,000 apps and add-ons with curated collections of top apps tied to key business outcomes. Some of those listings are foundational parts of daily Splunk work, from cloud and operating system add-ons to database connectivity, security content and SOAR connectors. The Splunk Add-on for Amazon Web Services has crossed more than one million downloads. Other popular and trending apps include the Splunk MCP Server and Splunk AI Toolkit.

When a team pulls in AWS data, normalizes Windows events, connects database context, investigates a security incident or builds a dashboard that saves someone hours of work, Splunkbase is often part of the path. It helps turn a clever solution into something reusable. It lets a builder say, "This helped us. Maybe it can help you too."

It also gives customers choice. A Splunkbase user can start with Splunk built and supported apps, explore partner solutions, find community-built utilities or build their own. Developers get Splunk development resources and a 10GB license to help them create apps that solve customer use cases around the world. That builder motion matters because the hardest problems in security, observability and IT operations are not solved by one team alone. They are solved by many teams—it takes a village—each person bringing a slightly different view of what "success" looks like.

Getting Ready for the AI Era

You can see that range on Splunkbase today. Popular cloud apps help teams bring data from AWS, Google Cloud Platform and Microsoft services into the Splunk platform. Security and fraud content helps teams move faster from detection to investigation. Developer and utility apps help admins improve the way they manage, extend and operate their environments. And newer AI-oriented listings, including Splunk MCP Server, point to the next chapter: making Splunk data, searches and knowledge objects more accessible to AI assistants, agents and intelligent workflows, with security and access controls in the loop.

As we are all aware, AI changes how people ask questions and how software takes action. But it does not remove the need for trusted operational context. In fact, it makes that need sharper. AI systems need grounding, permission-aware access to data, and tools that know the difference between suggesting an action and taking one. They also need ecosystems where customers can find capabilities they can evaluate, govern and reuse.

That is where Splunkbase can play an even bigger role.

The next era of Splunkbase is not only about finding an app. It is about helping customers and builders discover trusted capabilities across the Splunk platform: deterministic apps, AI-assisted experiences, MCP tools, skills, agentic workflows and the quality signals that tell teams what is ready for their environment. Apps have always packaged expertise. In the AI era, that packaged expertise can become a safer, more governed action layer for people and agents.

Thank You, Builders

To the people who built the first event type, the first parser, the first dashboard, the first add-on, the first custom command, the first SOAR connector, the first visualization, the first "I made this because I needed it" app: thank you. Splunkbase exists because you turned experience into software. You made hard-won knowledge discoverable. You helped customers move faster. You made the Splunk platform more useful in the real, messy, high-stakes environments where security, resilience and uptime matter.

Now the question is bigger: what should be discoverable when humans and agents both build on the Splunk platform? What does trust look like when capabilities are called through APIs, assistants and automated workflows? How do we help a community of builders move from solving one problem at a time to creating reusable, governed building blocks for the agentic enterprise?

Those are the questions we get to answer next.

Happy anniversary, Splunkbase. And to every builder in the ecosystem: keep going. The next great app, add-on, tool or AgenticOps workflow probably starts the same way the best ones always have, with someone close to the problem saying, "There has to be a better way." We look forward to seeing many of you at .conf26 and the Builder Bar, where you can help us build the next 20 years of Splunkbase.