Connect
Point Ostrel at a site's access controllers — any supported brand, mixed freely across one estate.
Access-control abstraction
Ostrel gives your platform one place to handle doors, cards, and alarms across different access systems — so you connect once instead of integrating each one separately.
The problem
Platforms that manage doors, cards, and alarms usually build a separate integration for each brand of controller — each with its own protocol, auth, and data model. Across more sites and vendors, that adds up.
A new integration for Axema, another for Alarm systems, another for TECHFASS, another for Came BPT, another for Hanwha Wisenet — rebuilt and re-tested for every new customer site, forever.
Connect once to Ostrel. When a controller brand is added, the platforms built on it pick it up — without extra integration work on your side.
How it works
Point Ostrel at a site's access controllers — any supported brand, mixed freely across one estate.
Ostrel maps each vendor onto one common schema for doors, people, credentials, schedules, and events.
Your platform calls the Ostrel API. Swapping or mixing controller brands never touches your code.
Ostrel is API first — your platform calls it directly. There is also a simple web interface for everyday door, card, and schedule work, for teams who would rather not build one.
One schema
Doors, cards, and alarms from different controllers, normalized before they reach you.
| Time | Door | Result | Source |
|---|---|---|---|
| 09:14:02 | Entré A | granted | axema |
| 09:14:37 | Garage | granted | alarm system |
| 09:15:11 | Lab 2 | denied | techfass |
| 09:16:48 | Port 3 | granted | came bpt |
Systems
Supported from the start. As we add controller brands, the platforms built on Ostrel pick them up.
Early access
Ostrel is in early access for platform builders and integrators running mixed-vendor estates. Tell us what you're building and we'll get you set up.
Request early access