
The product layer of an access-control ecosystem
Every door speaks to every system.
What changed
An access-control channel that used to sell hardware locked to one maker now sells one platform that runs over sixty device models. Operators manage thousands of doors from a single app. Integrators and partners build on Z9 instead of around it. Firmware became a product a facility manager opens every morning.
Z9/Flex is the interoperability firmware: it lets panels, readers, and controllers from different makers behave as one system. AccessFlex is the management software that runs on top. Our work is the product layer over both: the mobile apps, the platform APIs, and the partner-facing surfaces the channel sells.
Visit Partner Site
The problem worth taking on
Interoperable underneath, invisible on top
The Approach
We built the first Z9 management app for iOS and Android on one shared core, with ninety-five percent of the code common to both, so a feature ships to every operator at once. Then we kept going: the platform layer, the APIs partners integrate against, and the surfaces the channel sells. Every release is shaped with Z9's leadership, on real panels, in real buildings.
The Challenge
Z9 had solved the hard part: making controllers from different manufacturers speak one language. But a facility manager does not buy firmware. They buy the thing they open on a phone, enrol a badge with, and trust to tell them when a door on the fourth floor did not close. Z9 needed a product on top of the engine, on both mobile platforms, without doubling the team or the code.

From one app to the platform partners build on
The first release was an operator app on top of Z9/Flex. It was the proof that firmware could feel like a product. What followed was the platform: partner integrations, event streams, cloud services, and the management surfaces that let forty-nine ecosystem partners ship their own products on Z9.
We have worked with SpiceFactory for years. They keep coming with innovative solutions all the time. Super fast product delivery cycles.
— Ken, President of Z9 Security
Outcomes across the ecosystem
What the product layer changed for the people who buy, install, and run access control.
Operators
- Thousands of doors managed from one app, on either phone
- Hardware from fourteen makers behaving as one system
- Enrolment, schedules, and alerts on the device in the pocket, not the panel in the closet
- Deployed in Fortune 500 facilities
Z9
- One shared mobile core: a feature ships to every operator at once
- A product on top of the engine, so Z9 sells a platform rather than firmware
- Release cycles measured in weeks, with leadership in the room
- One product team since the first app, no rewrite, no handover
Partners and the channel
- Forty-nine ecosystem partners building on Z9 APIs and events
- Over sixty device models supported through one integration
- Integrators sell a platform instead of a maker's lock-in
- New hardware joins the ecosystem without a new app

What runs today
The product layer over Z9/Flex and AccessFlex.
- Operator apps for iOS and Android on one shared core
- Platform APIs and event streams partners integrate against
- Cloud services behind the management surfaces
- Partner-facing surfaces the channel sells under its own brand
- Embedded integration with Z9/Flex firmware across sixty-plus device models
- Release pipeline shipping to every operator at once
The standard, experienced
Z9 made access control interoperable. The product we build is how that interoperability is felt: by the facility manager who opens one app, the integrator who ships one platform, and the partner who builds on it. The engine is Z9's. The product on top is what we build.

Building something like this?
Tell us what the business needs to win and who owns it on your side. If it is a fit, a First Build starts within weeks. If it is not, we will tell you why.


