Product area
Access
The physical layer. ARK360 manages doors, access levels and credentials across sites, and reads the access system the building already runs rather than replacing it.
From the running build
The screens.
Captures of the build as it stands. The data in them is a demo dataset, not an operator's.
Access and security
Doors, devices, access levels and the activity trail, integrated with the access system the building already runs. Shown as a diagram here: those screens populate from a live access-control sync, and this build is not connected to one.
Your directory
A person and an agent each authenticate as themselves. No shared service account.
Access level
Authority is granted per role and scoped to a site. It is the narrowest thing that does the job.
The door
The building's own access system stays the record. ARK360 asks it; it decides.
The trail
What acted, under whose authority, at which door, with what result.
Status
What is built in Access, and what is not.
Three states, from the same capability map the platform is governed by. The middle one is the one worth reading.
Shipped
Built, and working in the running build.
- A multi-site door directory, with access levels, schedules and device groups
- BioStar Air cloud integration, kept as the access-control system of record
- A real-time access-event stream into the operator console
- Digital key and BLE unlock in the resident app through Airfob, validated on physical hardware
Partial
Built underneath, and not reachable end to end yet.
- Credential revocation on move-out is best effort, and a failure is currently swallowed rather than raised
Roadmap
Not built. Named here so it cannot be implied elsewhere.
- Named property-management vendor connectors beyond the generic adapter
The rest of the platform