Access-control abstraction layer

Access control,
centralized.

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

One door. A dozen dialects.

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.

Without Ostrel

A new integration for Axema, another for Acre, another for TECHFASS, another for Came BPT — rebuilt and re-tested for every new customer site, forever.

With Ostrel

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

Connect. Normalize. Build once.

1

Connect

Point Ostrel at a site's access controllers — any supported brand, mixed freely across one estate.

2

Normalize

Ostrel maps each vendor onto one common schema for doors, people, credentials, schedules, and events.

3

Build once

Your platform calls the Ostrel API. Swapping or mixing controller brands never touches your code.

Doors & controllers Card readers Persons & credentials Access groups Time schedules Events & alarms Remote door control

Systems

Systems we centralize

Supported from the start. As we add controller brands, the platforms built on Ostrel pick them up.

Axema
Vaka
Acre
Vanderbilt SPC
TECHFASS
also sold as Malux
Came BPT
 

Early access

Integrate access once.

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 in.

hello@ostrel.se