Stop tinkering. Start deploying. Pair up, pick a real Dapta bottleneck, and build an agent from scratch for a real internal workflow. Demos at 10 PM. Winners at 11.
Dapta ships infrastructure that moves data for hundreds of other teams. Yet internally, we still do a lot of manual, repetitive work, the kind an agent could eat for breakfast.
Thursday night, we change that. We pair up, pick a real Dapta bottleneck, and ship an agent, a skill, or an automation in a single sitting.
Built from scratch. Demoed live. Deployed tomorrow. It doesn't have to be perfect. It just has to work.
From half-baked idea to working internal tool, on a Thursday night. Here's exactly how it goes down.
Pairs. Grab a partner at kickoff. One domain expert plus one AI-savvy builder is the dream combo, but any pairing works.
Everyone presents at 10:00 PM. Broken is fine. Half-broken is fine. Nothing is not.
Judges: Nicolás & Felipe pick the jury winner. The room picks the crowd favorite by live vote.
Build something that actually works. An agent, a skill, an automation, a wild experiment. Full creative freedom.
The goal isn't a pitch deck. The goal is a functioning tool we plug into a real Dapta workflow starting tomorrow.
Share your build in #hackathon on Slack.
Build an agent or workflow that a real Dapta team can use next Monday. That's the only brief.
Pick a single, painful task a real Dapta team does today. Not hypothetical. Not cross-functional. One chore, one team, one outcome.
By 10 PM it must run on real inputs and produce a real output. Working > pretty. No mocks, no "imagine if". If it can't run live, it doesn't count.
No pre-written scaffolds, no prior work. Everything is built the night of. Reusing public libraries and APIs is fair game. Reusing your own old code is not.
Solo or pair. 6-7 hours of build time. Narrow scope beats grand vision every time. If it doesn't fit in a single demo, cut it.
Whatever gets you to a working demo by 10 PM. These are the tools the rest of the team is likely to recognize, and the ones we've tested.
$700 in real prize money, plus pizza and Red Bulls. And bragging rights through the next all-hands.
Five rules, mostly common sense. Read them, sign them in spirit, then forget them and build.
No pre-existing projects. No "I had this lying around." Open your editor at 6:00 PM with a blank file. That's the whole point.
Every pair presents at 10:00 PM. Working or half-working, both count. A broken demo beats no demo. "It worked 5 minutes ago" is an accepted format.
Team size is one or two. Don't have a partner? Kickoff at 5:30 PM is matchmaking night. Come solo, leave paired, or just fly solo and ship.
Pizza, coffee, Red Bulls and transportation back are all on the house for folks joining in person in Colombia. We'd rather you ship than safely catch the last bus.
Participation is optional. The only real rule: build something you'll be proud to show your team on Friday. Everything else is vibes.
Grab a partner. Find a problem. Ship a solution.
The hackathon kicks off at 5:30 PM COT sharp.