Back to all updates

4 days ago

Before you submit: the most common reasons projects don't make the cut 🔍

The Splunk Agentic Ops Hackathon closes on June 15th at 9:00 AM PT. We want every project to get a fair review, so here's exactly what we check — and the most common reasons submissions get disqualified. Take a few minutes to confirm none of these apply to you before the deadline.

  1. Splunk AI capabilities aren't actually used. This is the single biggest reason. Your project must use Splunk's AI capabilities at runtime — projects built only on other tools (e.g., Gemini or Firebase alone), mock prototypes with simulated Splunk output, or projects that only describe a planned Splunk integration don't qualify. Fix: open your code and confirm Splunk AI capabilities are actually integrated and called when your project runs.
  2. No architecture diagram. A written description of your architecture may not cut it — judges need an actual diagram showing how your solution interacts with Splunk and integrates AI. Fix: refer to the specific architecture diagram instructions in the rules and make sure your submission follows them.
  3. The project isn't new or substantially updated. Existing projects are welcome, but only if they've been substantially updated during the hackathon period (on or after May 18, 2026). Fix: if you're building on existing work, make sure your submission clearly explains what's new and that your commit history backs it up.
  4. No open source license. Your repo needs a real OSI-approved license that's detectable — visible in the repo's About section. Fix: add a LICENSE file at the root of your repo. A copyright line in the README does not count.
  5. The code repository isn't accessible. A private repo, a removed repo, or a broken link means judges can't review your work. Fix: open your repo link in an incognito window to confirm it's public and reachable.

You can update your submission as many times as you want before the deadline — so if any of these apply to you, there's still time to fix it. ⚡

Need a hand?
  1. Click here to go to the Splunk Community Slack sign in page
  2. Click on “Sign in with your Splunk ID. If a new Splunk user, create your Splunk account. Existing users can sign in with their Splunk login details.
  3. Head to the to the #splunk-ai-hackathon Slack channel for support