Built by People Who Actually Fix Apps
We started streamonlighta because we were tired of watching businesses struggle with app updates that broke more things than they fixed. It's 2025, and apps shouldn't crash every time someone updates their phone.
Started in a Canberra Coffee Shop
Back in 2019, Thorsten and I were working contract jobs—him doing backend work for a logistics company, me fixing broken app deployments for retail clients. We'd meet up at the same café on Northbourne Avenue every Thursday morning.
One day Thorsten showed me this deployment pipeline he'd built that actually tested updates against real device configurations before pushing them live. Sounds basic now, but back then? Most companies were just crossing their fingers and hoping iOS updates wouldn't break everything.
We figured other businesses probably had the same problems our clients did. Apps that worked fine until Apple or Google changed something. Updates that took weeks because nobody wanted to be the one to break production. Support teams drowning in bug reports they couldn't reproduce.
So we put together a basic monitoring system and offered it to three local businesses for free. Two of them are still clients today. The third one got acquired, but their new parent company uses our services too.
How We Actually Work
Most IT companies will tell you about their "proven methodologies" or "cutting-edge frameworks." We just try to prevent your app from breaking when things change—which they do constantly.
Real Device Testing
We maintain a rack of actual phones and tablets running different OS versions. Not emulators. Real devices. Because an app that works perfectly in a simulator can still crash on a three-year-old Samsung.
Gradual Rollouts
Updates go to 5% of users first, then 20%, then everyone. If something breaks, we catch it before your entire customer base starts leaving one-star reviews. Learned this one the hard way in 2021.
Boring Reliability
We don't rebuild your entire app every six months. We make small, tested changes that keep things working when OS updates drop. Your customers probably won't notice anything—which is exactly the point.
The Person Who'll Probably Answer Your Email
We're a small team. You'll work directly with the people who actually manage your deployments, not an account manager who has to ask someone else for technical answers.
Thorsten Lundquist
Lead Technical Architect
Thorsten's been writing deployment scripts since 2014, back when continuous integration meant "we deploy on Fridays and hope nothing breaks over the weekend." He built our core monitoring system and still maintains most of it.
He's the one who'll notice your app's crash rate went from 0.2% to 0.8% before you do. Usually emails clients at odd hours because he checks monitoring dashboards before bed. His wife thinks it's excessive. His clients appreciate it when we catch issues at 11pm instead of 9am Monday morning.
Outside of work he restores old motorcycles, which probably says something about his patience for fixing things that break in weird ways.
Want to Talk About Your App?
We're based in Mitchell but work with businesses across Australia. If your app keeps breaking after updates or you're worried about the next iOS release, let's have a conversation about what we can do.