The JBAC story

For us, that obsession has always been about making things work. JBAC started as two friends on opposite sides of a 7-hour time difference, trading late-night calls and stubborn promises: if something was broken, we would fix it; if something didn’t exist, we would build it. There were versioning disasters at 3 a.m., free-tier limits that killed deploys mid-demo, and cryptic logs that made us question our logic. We messed things up, rolled them back, and tried again. What never left was the rush - the obsession - with solving problems and shipping something real.

Every project began the same way: a gap we felt in our own lives, a quick “can we build this?” on a call, and then days of reading docs, tracing stack traces, and rewriting parts that didn’t scale. The terminal-only AI-Interviewer became a voice-to-voice service. The Hackathon Scraper grew from a local script to a clean, hosted tool. The YouTube LLM Questionnaire Generator went from a 45-minute pipeline to a 5–7 minute sprint through careful GPU - CPU optimization. We did it the unglamorous way - RTFM, unit tests, logging, refactors, and a lot of coffee.

We learned deployment the hard way. Free tiers meant budgets and trade-offs; cold starts forced us to rethink architecture; rate limits taught us to cache, queue, and backoff. We broke things minutes before demos and fixed them minutes after. We fought merge conflicts, dependency hell, and “works on my machine” until it worked on everyone’s. The point was never perfection - it was persistence. Keep moving. Keep shipping.

When the web didn't quite spin our way, we learnt about developing Python SDKs/Libraries. We were so fascinated by the possibility of providing features that run totally locally on the user's machine that we ended up publishing not one but two libraries/SDKs on PyPI. One of them is already 750+ downloads strong!

JBAC isn’t a pitch deck. It’s a rhythm: build → break → learn → ship. Our ideas came from the simple feeling that something should exist, and if it didn’t, we’d make it - and open-source it so others could use it too. We tried to keep everything free-tier friendly, documented the sharp edges, and made the UX fast so people actually saved time. What started as phone calls turned into products, and those products turned into a habit: take small, useful ideas and push them into the world.

That’s the story we believe in. Not luck. Not shortcuts. Just two friends who got stubborn enough that no amount of errors, logs, or rate limits could break us. JBAC is our obsession with building - one commit, one fix, one shipped tool at a time.