Justin Dagen Spent 15 Years Learning Why Doors Fail - Then He Made Them Read the Calendar

Every ordinary door on a college campus is a small negotiation. A lecture begins at nine. A club has the room at seven. A student books a practice space ten minutes before arriving. Somewhere else, a weather delay rewrites the day. The lock knows none of this. The calendar knows all of it. For years, a person had to stand between them, carrying information from one system to the other with reports, spreadsheets, and manually programmed schedules.

Justin Dagen built his career in that gap. It is a narrow place, technically fussy and almost invisible when it works. It is also where the consequences of two perfectly respectable systems refusing to speak become embarrassingly physical. A professor waits in a corridor. A building stays open hours longer than necessary. A campus safety officer gets a call that a computer should have prevented.

Dagen is a Rochester-area software engineer who studied computer science at the University of Rochester, graduating in 2002, and later earned a master's degree in software engineering from Brandeis University. His first professional stop was Netsville, where he worked as a systems engineer. In 2004 he moved to Lenel Systems International and stayed until the end of 2016, working in customer-facing custom development and engineering leadership.

Those years supplied a rather useful education: not merely how access-control software is supposed to behave, but how it behaves after meeting universities, companies, government agencies, and the baroque reality of an installed system. Dagen and his colleague Jason Higley spent roughly 15 years building and supporting integrations in that world. They learned the APIs. More importantly, they learned the exceptions.

A calendar full of facts, a door full of silence

In 2016, Dagen and Higley formed Detrios. Their premise was grounded in work they had already seen: organizations wanted integrated access control, but the last mile was often a custom project. Higher education presented an especially dense version of the problem. Thousands of spaces change purpose throughout a week. Classes, conferences, meetings, housing assignments, study groups, and cancellations all create temporary rules about who should enter where and when.

Campuses were compensating with labor. Administrators ran daily or weekly event reports and translated them into reader schedules. Someone remained on call for late changes. Another compromise was to leave doors open through a generous block of “typical” hours, trading precision for convenience. Everyone involved knew the calendar held better information. There simply was no dependable bridge to the access-control system.

Detrios called its answer DAX. The software sits between event, room, and housing platforms on one side and access-control platforms on the other. It maps spaces to readers, handles pre-event and post-event timing, merges overlapping schedules, and reacts to last-minute bookings or cancellations. Campus rules remain in charge. Lockdowns, manual officer actions, and other configured overrides can take priority.

The product is revealing in one important respect: it does not demand a theatrical rip-and-replace. It uses supported APIs to connect systems already installed. DAX runs on premises, in large part because many access-control platforms live there and do not accept inbound commands from external networks. The design follows the awkward facts of the environment instead of asking the environment to become fashionable.

Sixty rooms and a number worth checking twice

Wake Forest University became the first DAX customer. In 2017, its Deacon OneCard team worked with Detrios on an initial 60-room pilot. The university tracked the time staff spent on activities that included room and reader scheduling. The result reported by the DAX team was 15 hours saved per day. The Wake Forest group ran the calculation twice.

The figure made the invisible cost visible. A human process can seem modest when observed one click at a time. Add the clicks across dozens of rooms, a full day, and an academic year, and the chore becomes a job hiding inside other jobs. Automation did more than accelerate the task. It allowed the door schedule to follow the actual event schedule rather than a simplified imitation of it.

DAX expanded from that pilot to support widely used systems for access control, room scheduling, events, and housing. Detrios says the product now processes more than two million events each year across institutions serving more than one million students, from regional colleges to large state universities. Customers describe the value in similarly practical terms: fewer hours spent programming unlocks, the ability to handle late reservations, and tighter control over when buildings remain open.

Custom work taught the product what to become

There is a tidy founder lesson here, although the work itself was anything but tidy. Dagen and Higley did not begin as outsiders declaring an old industry broken. They had spent years inside its constraints, serving customers whose systems could not pause for a clean-sheet redesign. That experience let them distinguish a recurring problem from a merely loud one.

Detrios continued to offer consulting and custom integration alongside DAX. That pairing makes sense. Custom work keeps an engineering team near the sharp edges of a market; a product captures the patterns that recur. The consultancy listens for new dialects. The product becomes a more fluent translator.

Dagen's own public biography still describes him as someone who writes code. Away from it, he plays pinball, golfs, and travels with his wife. Pinball is an almost suspiciously appropriate hobby: switches, timing, physical mechanisms, and layers of rules producing an outcome that feels immediate at the glass. Good access software aims for a similar vanishing act. A lot happens. The user experiences a click.

The credential met the context

In late 2022, SwiftConnect acquired Detrios. The combination joined two related layers of physical access. SwiftConnect worked on connected access and mobile credentials. Detrios brought deep integration experience and DAX's foothold in higher education. One side helped deliver a credential; the other helped systems decide what that credential ought to do.

Dagen and Higley joined the SwiftConnect management team, while Detrios continued operating from the Rochester area and serving its integration and DAX customers. Dagen is now listed as CEO of Detrios at SwiftConnect. The acquisition did not end the specialist story. It placed that specialty inside a broader connected-access network.

His recent public activity remains grounded in the same community. In 2025, Dagen participated in a Detrios Security Integration Forum at Rochester Institute of Technology. In 2026, he appeared with colleagues at the higher-education Lenel user conference in Rochester to discuss door automation, event scheduling, student housing, and mobile credentials. He joked publicly about enjoying a conference ten minutes from home. The remark is small, cheerful, and useful. This is a founder whose industry network and home ground overlap.

The larger aspiration Dagen and Higley have stated with SwiftConnect is “connected access”: systems, credentials, and places coordinating cleanly enough to create value without exposing all the machinery to the person at the door. It is an ambition built from decidedly unglamorous ingredients. Mapping tables. Vendor APIs. Security policies. An event that moved from Tuesday to Thursday.

Founders are often advised to look for pain. Dagen's story offers a more precise instruction: look for the competent person doing the same translation again. They may not complain. They may have built a respectable spreadsheet. They may even call the process normal. But if one database already knows what another system needs, the space between them is not empty. It is waiting for an engineer patient enough to learn both languages.

A door opening on time is an unremarkable event. That is the achievement. Nobody applauds, nobody files a ticket, and nobody wonders which piece of software made the decision. The room simply becomes available when the calendar says it should. Somewhere behind that quiet click sits the kind of company Justin Dagen knew how to build because he had spent 15 years listening to what happened when the click came late.