About us
This is a group for anyone interested in search engineering, open source search technology, and search relevancy in the Pune area. If you’ve used or are interested in OpenSearch, you’re in the right place!
All skill levels are welcome. Even if search is just a small part of your day-to-day duties, come learn and connect with other smart engineers. We cover and welcome talks on topics including: search, logging, log analytics, and data visualization.
Upcoming events
1
![[24-HR Hackathon] Build. Run. Ship. Observe](https://secure.meetupstatic.com/photos/event/a/5/8/f/highres_527802383.jpeg)
[24-HR Hackathon] Build. Run. Ship. Observe
Unnati Development and Training Centre Pvt Ltd Pune, 2nd Floor, Office no 222,223, Business Bay, behind Hotel Tip Top International, WBB, Wakad, Pimpri-Chinchwad, Maharashtra 411057, Pune, INInvite Only · register for approval · 80–100 builders
***
What is this?
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 model is running, but nobody knows if it's running well. They fail when the system ships, but nobody can see inside it.
So let's spend 24 hours on the part people skip. build the thing, run it in a real environment, ship it so it actually works, and observe it so you know when it doesn't.
The theme is production engineering — containers, local AI, cloud native infrastructure, and observability. But it's an anchor, not a fence. Bring whatever backend, AI, or infrastructure problem you're 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 challenges, evaluation criteria, and partner bounties will be revealed 3 days before the event (Wednesday, June 24) or directly on the spot. We won’t be giving out starter codebases—we want to see how you architect and stitch things together from scratch. - The Technical Playground:
The challenges focus on real-world infrastructure problems. You'll be dealing with concepts like container deployment, local GenAI/LLM pipelines, end-to-end observability, and data indexing loops. - What technology should you use?
Your choice. Bring your own stack. We care about 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 local binaries. Use whatever tools let your squad build fast, and stream system telemetry live by Sunday morning. - How do teams register?
One person can register the entire squad. You do not need to fill out individual forms. A single representative can submit names, GitHub/LinkedIn links, and tech stacks for the whole team (max 4 members). Solo builders are completely welcome too - we'll help you team up on Saturday morning!
***
How do the 24 hours run on
Saturday, June 27
10:00 → doors open + caffeine grab a spot, open your IDE, write on the wall what you're trying to ship today.
10:15 – 1:30 → the lightning talk arena, a continuous stream of 5–7 minute open-mic walkthroughs from the room. no slides — Open a terminal, a config file, or grab a whiteboard marker.
— Got a container setup that actually works in prod? show it. — an observability pipeline that catches real failures? walk us through it. — a local AI inference setup, a compose pattern, a deployment trick that saved you? The floor is yours. — fresher with a script, an automation, or a tool breakdown you're proud of? same stage, same respect.
Draft bonus: the team that recruits a morning speaker onto their squad starts Sunday with +10 points on the leaderboard.
1:30 – 2:15 → lunch + team draft grab food. form squads (max 4). You just watched people live-terminal for three hours — you know exactly who you want on your team.
2:15 → hacking begins + bounty board drops build your own project or take one of the open tracks.
6:00 → mid-sprint architecture check whiteboard sessions with mentors. catch what's broken before the night starts.
8:00 – 9:00 → dinner fuel block step away from the keyboard. eat. Map your overnight execution plan with your team.
12:00 AM → midnight fuel + late-night huddle chai, coffee, bun maska, samosas. secret partner bounties drop.Sunday, June 28
7:00 AM → sunrise code freeze, hands off the keyboard. clean up environments, stabilise pipelines, run final diagnostics.
7:30 – 8:30 AM → sunrise breakfast, hot local breakfast before the stage opens.
9:00 AM → the showdown strictly no slides. 5 minutes per team. show us a running system, live logs, active integrations, and a real dashboard. If it doesn't run on localhost, it doesn't exist.
11:30 AM → awards + wrap speaker bonus tallies, prizes, group pictures.Who's this for
1. Builders. engineers who want to break production systems, instrument them properly, and ship something that survives 3 AM.
2. Learners. Freshers and students who want a real peer-learning weekend — hear from engineers running actual production systems, get on a team, and build something that works by Sunday morning.***
Bring
laptop, charged, plus charger your stack of choice, an API key or credentials (BYO, or we'll sort partner credits on the day), a project to build, or an open mind for the bounty board
LET'S BUILDD :)2 attendees- What is the problem statement?
Past events
1
