Because legacy “wired” architectures cost upwards of €2,000 per door. They are built solely for the few “battleship” entrances, leaving the remaining 97% of your asset as analog dead weight. Bitwards uses the smartphone as the infrastructure layer to make digitizing every single door, cabinet, and utility economically inevitable.

When a legacy vendor tells you a door “doesn’t need” digital access, what they actually mean is that their system is too expensive and rigid to justify putting it there.

Through logical separation. The owner defines the boundary, but the tenant manages the identity. It is a peace treaty built into the architecture that respects the privacy line between building safety and individual privacy.

Most “keyless” systems are designed for total surveillance; we are designed for sovereign access.

Universities don’t have static populations—they have semester turnover, visiting researchers, temporary contractors, and event guests, often numbering in the tens of thousands.

• Legacy systems handle this by creating, distributing, and eventually collecting physical fobs for every person. 
• Bitwards replaces that entire logistics chain with software-defined delegation. Departments issue time-bound, role-based access rights directly through the Tenant Access Manager. 
• When a student graduates or a visitor’s event ends, the credential expires automatically. No fobs to chase. No manual database purge.

If your facilities team is still spending the first two weeks of every semester handing out plastic cards and the last two weeks trying to collect them, that’s not an operations problem—it’s an architecture problem.

Yes. Because the phone is the infrastructure, each building doesn’t need its own network connection to participate in the access system. The phone carries certified, time-bound tokens that the lock validates locally. Audit data is carried back to the cloud by the next connected phone. You manage the entire estate from a single platform—whether the building has gigabit ethernet or no network at all.

Legacy vendors will tell you each building needs its own controller and site network. What they really mean is: each building needs another €50,000 in hardware before a single door goes digital.

Through logical separation – configured in a few stroked by the administrator on the Bitwards Platform.

• The university defines the building boundary and the overarching policy. 
• The departments—engineering, medicine, administration—manages their own users, its own schedules, and their own internal spaces. The university never needs to see who the department lets in. They only need to know that the policy rules are being followed.

Legacy “master” systems force a choice: either the central office controls everything (and departments resent the bottleneck), or departments run their own silos (and central loses oversight). We eliminate that choice.

No. Bitwards is an architectural bridge. Bitwards Unwired Access coexists with your existing infrastructure—extending modern delegation, remote management, and software-defined permissions to your current card readers and digital locks at virtually no additional cost. 

For new buildings or expansions, you deploy Bitwards Unwired Access with zero legacy hardware. Over time, the old infrastructure phases out naturally. No rip-and-replace. No capital shock.

The vendors who sold you the original hardware want you to believe that the only upgrade path is buying more of their hardware. We exist to prove that’s not true.

Emergency protocols are handled at the policy layer, not the device layer. Lockdown or evacuation commands propagate through the Bitwards Unwired Access to every enrolled user. 

• Doors stay locked.
• Doors can be commanded to lock, unlock, or fail-safe based on pre-defined emergency profiles—just as they would in any compliant access system. Critically, because the system works offline, emergency behavior is pre-loaded at the door level. It does not depend on an active network connection at the moment of crisis.

A wired system’s emergency response is only as reliable as the network that connects it. If the emergency is the reason the network went down, you have a problem. Our emergency logic lives at the edge—where it matters.