[24-HR Hackathon] Build. Run. Ship. Observe.
Details
Most engineering projects don't fail at the idea stage.
They fail when the container crashes at 2 AM and nobody set up tracing. They fail when the pipeline works locally and nowhere else. They fail when the backend is running, but nobody knows if it's running well. They fail when the system ships, but nobody can see inside it.
We are focusing heavily on the parts people usually skip: building the system, running it in a real environment, shipping it so it actually works, and observing it so you know when it breaks.
The theme is pure Production Engineering - containers, local AI inference, cloud-native infrastructure, and telemetry pipelines. Bring whatever backend, systems, or infrastructure problem you are currently wrestling with.
👉 Apply here to register for approval → `https://forms.gle/Dx8WyGUb6U3M7cHw7`
### Theme, Tech Stack, & Problem Statements
- What is the problem statement?
The official tracks, evaluation criteria, and partner bounties will be revealed directly on the spot at 9:30 AM. We won’t be giving out starter codebases - we want to see how you architect, instrument, and stitch systems together from scratch under a tight clock. - The Technical Playground:
Challenges focus on real-world infrastructure problems: container deployment patterns, local LLM integration pipelines, end-to-end observability (metrics/logs/traces), and secure data loops. - What technology should you use?
Your choice. Bring your own stack. We care about the stability and visibility of the problem you solve, not the language you use. Write your logic in Go, Python, or Rust. Deploy it using Kubernetes, Docker Compose, or raw binaries. Just ensure you can stream system telemetry live by the evening.
### The 8-Hour Sprint Schedule (Saturday, July 25)
- 9:00 AM → Doors Open + Caffeine Grab: Claim a spot, open your IDE, and map out what you're trying to ship today.
- 9:30 AM → Hacking Clock Begins + Bounty Board Drops: Form your squads (max 4 members) or lock in your solo build. Select an open infrastructure track or build your own custom project.
- 1:30 PM → Mid-Sprint Fuel & Architecture Check: Grab lunch and run rapid whiteboard sessions with mentors to catch broken configurations before the afternoon crunch.
- 4:30 PM → Hard Code Freeze: Hands off the keyboard. Stabilize your environments and prepare for the live showcase.
- 4:45 PM → The Showdown: Strictly no slides. 5 minutes per team. Show us a running system, live logs, active container integrations, and a real observability dashboard. If it doesn't run, it doesn't exist.
- 5:30 PM → Awards, Wrap-up: Final tallies, community prizes, group pictures, and doors close.
### Who is this for?
- Builders: Engineers who want to break production systems, instrument them properly, and ship code that survives real-world chaos.
- Learners: Freshers and students looking for a high-density peer learning environment—work alongside engineers running production systems and build a verifiable, observable project in a day.
### What to bring:
Your laptop (fully charged + charger), your stack of choice, pre-pulled base images to save time, and a bias for shipping working systems.
LET'S BUILD IT.
