Articles · Infrastructure & Cities
The depot where every name is known
Transit systems still let vendors and staff cross on shared accounts. DepotCheck replaces them with issued identity, scopes every session to its job, and keeps receipts an agency can stand behind.
By Lucian · Lux Automations
The problem
A transit depot at night holds the city’s moving parts: buses and trains at rest, and the systems that will send them out in the morning — fare collection, real-time tracking, and the operations networks behind them. Vendors and staff cross into those systems to keep them running. Too often, they cross on shared accounts that name no one.
The preparedness picture is thin. A Mineta Transportation Institute study found only 3 in 5 US public transit agencies had a plan to deal with a cyberattack. The named cases keep coming: SEPTA in 2020, New York’s MTA in 2021, and Maryland’s MTA in 2025. Each case is its own story, but the common thread the product page draws is access that crosses into fare, tracking and operations networks without a name and a scope attached to it.
A public agency carries a burden a private firm does not. Its record may be read in public, under public-records rules and grant-compliance audits. A shared account cannot support that record. After an incident, “the vendor account was in that night” is not an account of anything.
The technology
DepotCheck replaces shared accounts with issued identity. Every vendor and every staffer crosses by name and key, with an identity issued to that person or firm. The door knows every name because every name was issued at the door.
Sessions are then mandate-scoped to the job at hand. Access ends where the mandate ends: the firm maintaining the fare system holds a session for the fare system and its task, not a standing pass across tracking and operations. The scope is set before the session begins and checked as it crosses.
Every crossing leaves a receipt sized for public-records and grant-compliance audits — the record a public agency can stand behind. Underneath, it is the house engine: Amos checks who is knocking, SeamGuard checks the joins between systems, and every check leaves a signed receipt. And revocation is immediate: when the contract ends, so does the key, in a moment, without disturbing anyone else’s access.
What it changes
For an agency, the change is a record it can publish, file and defend. Grant compliance and public-records requests are answered from receipts that were written as the work happened, each one naming who crossed, under what scope, and when. The audit stops being an excavation and becomes a reading.
For vendors and staff, named access is fairer as well as stricter. Work done properly under one’s own name and mandate is provable, and no one carries the suspicion that falls on a shared account everyone used. When a contract ends, its key ends with it, cleanly, and the next firm begins under its own name rather than inheriting the last firm’s login.
Transit will remain a public, complicated, many-handed system. DepotCheck does not simplify the city. It gives the city’s systems a door that knows every name, scopes every session, and keeps the receipts a public trust requires.
See it
DepotCheck checks the buses, trains and systems in a transit depot, behind a door that knows every name. DepotCheck — the product page · All the house articles · Lux Automations — ailux.ca