vøiddo on devpost · updated 2026-05-16
eleven active builds across cash-prize hackathons running on devpost, lablab.ai, kaggle, and a handful of vendor-run sponsor pages. each one carries a public app or a public repo, real screenshots taken from the working build, a recorded demo when the platform requires it, and an honest scope section that says what was finished, what was cut, and why — instead of the usual hackathon submission padding where “production-ready” means “runs once on the demo laptop if you do not click anything weird.” judging happens on the work that is actually shipped, not on the slide deck wrapped around it.
01 active builds
each card links to the local proof page (screenshots, recorded demo, audit notes, deferred scope) hosted on voiddo.com under /devpost/<project>/ and to the original hackathon overview on devpost.com or the equivalent sponsor page. sorted by deadline, closest first — the “building” tag is honest and means we have not yet pushed the final submission, not that we will get to it later.
a reddit-native duplicate-review mod tool. posters precheck before submitting; mods get a last-7d duplicates queue with similarity scores and one-click lock/remove. zero llm, zero external network. already live on reddit developer platform — only the submission needs to go in.
a no-code message coach built end-to-end inside medo. paste a thread, get a calmer rewrite, see the rule. tells lite carries the public app, support page, and demo reel.
a defensive incident agent that refuses unsupported claims. reads case events, forms findings, runs a correction pass, and ties every conclusion to exact evidence. precision and recall stay visible.
a launch-readiness agent for the hour before shipping. inspects release evidence, calls tools, ranks blockers, and returns owner-safe next actions instead of a vague green light. if a required mcp is blocked, the report says blocked.
an evidence-first incident triage room for Splunk teams. takes an alert bundle, forms evidence-backed findings, marks every unverified conclusion, and generates explicit next SPL queries — tied to the Security track and Best Use of Splunk MCP Server.
a resilience console for autonomous operators. shows an agent choosing a safe failure mode instead of pretending success. live TrueFoundry AI Gateway integration — gemini-2.5-flash-lite primary, gemma-3-27b-it free fallback — with 2× authenticated HTTP 200 gateway calls as proof.
an AI-powered english activity generator for low-resource classrooms. teachers choose an age group and topic; gemma 4 returns a structured, print-ready lesson plan. no internet in class — activities are cached for fully offline use.
a live-web research desk for outbound and partner scouting. deterministic by design: fixture mode is fully explorable today; live mode stays blocked until a real authenticated bright data capture is attached. every claim in the brief points back to a retrieval step.
ai-augmented bpmn process orchestration: claude classifies contracts, detects exceptions at each uipath maestro stage, and decides retry / escalate / reroute at runtime. no hand-coded catch blocks — the ai is the exception handler.
a deterministic ops triage agent for the special ops track. reads live vøiddo state and returns a clean run-now / repair / defer / owner-only split — no guessing, no silent failures. copilot studio integration is fixture-safe now; live microsoft path is gated behind one authenticated capture.
an enterprise AI resilience console built on IBM watsonx. shows how granite-powered agents handle IAM token failures, model brownouts, rate-limit storms, and response validation failures — safely, without silent data loss. fixture mode is fully explorable; IBM watsonx mode unlocks with a real IBM Cloud request ID proof.
02 how this surface works
each linked project carries a runnable slice or a public proof page before the devpost submission goes in. no rendered mocks pretending to be live ui, no demo videos cut to hide the parts that crash, no invented metrics pulled from a slide template. the boring rules below are why this page is a useful index instead of a vanity gallery.
scope rule
every entry above maps to an active hackathon with a confirmed deadline and a confirmed prize, both verified on the sponsor’s page on the day the card was published. when a hackathon closes we move that entry to a results page, mark the outcome (won, placed, no placement, withdrawn) honestly, and link to the judges’ public statement when they publish one. we do not retroactively claim wins, we do not delete losing entries, we do not re-tag a missed deadline as “deferred”.
media
screenshots and demo videos are produced from real runs on the actual build that will be submitted, not from photoshopped mockups or pre-rendered concept art. when a clip is a scripted browser capture (typing automated, mouse path scripted, narration absent) rather than a real narrated demo, the proof page says so on the same surface so judges can read the disclosure without having to ask. when a project relies on a sponsor api we cannot access on our own developer credentials, the proof page shows the fixture-mode run side by side with a screenshot of the blocked sponsor call.
cross-link
this hub lives one click from /reddit/ (our devvit apps surface, including dupe-detector and queue sentinel’s public reddit reach), the root portal, the studio engine room for context on how we ship in general, and the per-project proof pages linked above. every page is statically generated from the same project metadata, so a card update propagates to all surfaces in a single rebuild.
future builds
our internal hackathon scout (a small daemon) tracks new active hackathons across devpost, lablab.ai, mlh, kaggle, and a handful of vendor pages, seeds the candidates into a local board, and a human on the team decides which to take on based on whether we already have working code that fits the brief. eazo (a queued data-cleaning agent) and a couple of others sit in that backlog and will not appear on this page until a working slice exists in a public repo — promising a build before it has been started is exactly the kind of pitch theatre this page is set up to avoid.