I've spent the best part of twenty years in enterprise IT. Patch management, endpoint governance, Azure infrastructure — the kind of work that happens quietly in the background and only gets noticed when something goes wrong.
For most of that time, monthly patching meant the same thing it means for most engineers. Maintenance windows booked weeks in advance. Last-minute calls from application owners asking for exclusions. Spreadsheets tracking compliance across environments. Tenants managed one at a time, manually, on a schedule that never quite survived contact with reality. You get it done, you move on, and six weeks later you do it all again.
"I kept waiting for something better to exist. It never quite arrived. So I built it."
I'm a developer by passion and an infrastructure engineer by profession, and for the first time those two things pointed at exactly the same problem. OPUS started as a personal project, built in evenings and weekends alongside a full-time role. The result is a platform I'd have genuinely wanted to use for the last decade — and one that's already doing that job in production.
I built OPUS because I understood the frustration from the inside. That's still the best reason I know to build anything.