Splunk Developer Day Recap: Building, Publishing, and Growing on the Splunk Platform

[vvalverde]

Splunk Developer Day brought the Splunk developer community together for a practical look at what it means to build on the Splunk platform today. 

Hosted by Splunk Community HQ on May 13, 2026, the event focused on the real work behind great developer experiences: extending the platform, building reliable technology add-ons, improving app quality, publishing on Splunkbase, and helping developers turn useful apps into sustainable solutions. 

This recap focuses on the community and ecosystem side of the day. For more product announcements, see the companion announcements post. 

Platform extensibility as the foundation 

The platform extensibility talk stepped back and explained how apps for the Splunk platform deliver value in the first place. 

The session framed an app as a packaged business outcome: configurations, content, and platform extensions bundled together so a customer can solve a specific problem. The talk focused on the extension side, where code connects to the Splunk platform through structured extension points that Splunk software can recognize, interpret, and run. 

That context made the rest of Developer Day easier to understand. MCP tools, embedded agents, custom visualizations, technology add-ons, and App Inspect improvements all build on the same idea: developers need clear, reliable ways to extend the platform without turning every project into a one-off integration puzzle. 

Modern technology add-on tooling gets a stronger quality path 

Technology add-ons were another practical focus of the day. The modern tooling session framed TAs as the backbone of how data gets into Splunk software, then walked through a more structured approach for building high-quality, reliable add-ons. 

The session covered a new gold standard framework and a self-assessment checklist for TA builders. The checklist helps developers evaluate whether their add-ons use UCC, store credentials correctly, include automated tests, validate Common Information Model mappings, support current platform standards, and provide documentation users can follow. 

The session also reinforced UCC as the primary framework for modern TA development. UCC uses a single global configuration file to generate the configuration UI, REST handlers, modular input scaffolding, monitoring dashboards, alert action files, OpenAPI documentation, and package structure around a developer's data collection logic. 

For developers maintaining TAs, the message was useful and concrete: start with the framework, run the self-assessment, and use the toolchain to catch quality issues earlier. 

AI for App Inspect and Splunkbase app analysis are available today 

The kickoff included two Splunkbase and app quality updates that are especially relevant for developers publishing apps. 

First, AI for App Inspect was described as a recently launched enhancement that embeds AI into App Inspect reports. Instead of only showing failed checks, the AI-enhanced report can explain why a check failed, identify root causes, and point developers toward the lines of code they may need to change. The session also described connecting App Inspect through CLI, API, or MCP so agentic coding tools can check work continuously against App Inspect guidance. 

Second, the Splunkbase app analyzer was presented as an AI-assisted way to improve app listing documentation. The tool looks at an uploaded app package and helps generate metadata - including summary, details, installation and troubleshooting for the Splunkbase listing, while leaving the developer in control to review and edit the output. This capability is available today. 

Both announcements support the same developer goal: make it easier to ship apps that are easier to review, understand, and maintain. 

A new guide for monetizing apps on Splunkbase 

The closing session focused on monetizing apps for the Splunk platform and introduced a new guide on the Splunk developer portal. 

The guide is the first version of documentation for developers who want to understand how to monetize an app, set up transactions, publish on Splunkbase, and build a more complete go-to-market path around a paid app. Newly launched, this guide is intended to become a living document shaped by developer feedback. 

That made a strong close to the day. Developer Day was not only about building apps; it was also about helping developers package, validate, publish, and grow them. 

Community announcements for builders 

The kickoff also included two community updates: 

The Agentic Ops Hackathon is live, with submissions open through June 15, 2026. Developers and practitioners are invited to build solutions across platform developer experience, observability, and security use cases, with $20,000 in cash and .conf26 passes to win as prizes. 

The Community Dashboard Contest is also open, giving developers another way to showcase dashboard-building skills and compete for .conf26 passes. 

What to watch next 

If you build on the Splunk platform, this content is for you. Developer Day showed how much investment is going into the full builder journey: how you extend the platform, how you create dependable add-ons, how you improve app quality, how you publish on Splunkbase, and how you grow from app package to real customer value. 

Watch the recordings to go deeper into the demos, examples, and implementation details from each session. 

Keep the good stuff coming. Here’s how to subscribe to this blog — and stay in the loop on the topics that matter to you.