Hello! 👋 I'm Anthony

I started Udora Safety in 2016 as a security integrator, installing cameras, access control systems, and structured cabling for clients across the Greater Toronto Area.

Planning and documenting those projects meant bouncing between floor plan printouts, spreadsheets, and presentation slides that never quite stayed in sync from site visit through to final handoff. The job always moved faster than the paperwork.

Udora Systems Designer grew out of that problem. Not a startup's theoretical product, but a practitioner's answer to a workflow that had been broken for too long. The goal was simple: one connected workspace where planning, review, and documentation stay tied to the same project, from start to finish.

Udora is in early access. I'm the developer, the designer, the support contact, and one of the primary users. There's no funding, no team, and no roadmap shaped by investor pressure.

That means decisions get made carefully, features get built because they solve real workflow problems, and feedback reaches someone who can actually act on it. If you get access and something isn't working the way it should, you're hearing from the person who wrote it.

Before Udora Safety, I spent over a decade as a flight dispatcher, managing flight planning, weather analysis, and operational control across multi-aircraft operations.

That background shapes how I think about systems design: field-ready, methodical, and honest about what actually matters under real operating conditions versus what just looks good on paper. Security projects aren't so different from flight operations, the details matter, the handoffs matter, and things going wrong in the field is expensive.