Yedem
INTEGRATIONS OVERVIEW · MAY 2026
● Investor Data Room · Product

The orchestration layer
for building mobility.

Yedem doesn't replace the systems already in the building — it sits on top of access control, parking hardware, and workplace apps, and adds the logic that's missing: capacity, fairness, statistics, CO₂.

A mobility orchestration layer — not another silo.

Traditional building systems answer a binary question. Yedem answers an operational one. That's the difference between infrastructure and intelligence.

Traditional ACS / PMS

"Is this car allowed in?"

Yes / No.

Gates lift or stay shut. Each system manages its own list. No awareness of company priorities, daily capacity, or who actually needs the spot.

Yedem

"Should this car come in right now?"

Intelligent orchestration.

Decides based on today's capacity, fairness, VIP rules, EV needs, and historical patterns. Becomes the source of truth for mobility — across every system.

4 layers of a building's tech stack — Yedem on top.

Every commercial property has the same architectural layers. Yedem integrates with the lower layers and adds the orchestration logic above them.

Layer
What it does
Example vendors
Yedem's relation
ACS
Access control
Who enters the building (people, doors, turnstiles)
C4 / Gamanet · Honeywell WinPak · Pro-Watch · Genetec · LenelS2
No integration today. User sync via SCIM from IdP.
PMS
Parking management
Physical barriers, LPR cameras, tickets
Green Center · SKIDATA · Cross · AS Parking · AnthonyApp
Core integration target — production today
Workplace App
Employee-facing
The app in the employee's hand
Sharry · Spaceflow · Spaceti
Integrated — module or standalone
IWMS
Lease management
Long-term real-estate / lease mgmt
Archibus · Spacewell
Out of scope
● Yedem
Mobility logic, reservations, data, fairness
Source of truth for mobility

Two integration patterns. One preferred.

Most deployments use reservation-based access — pushing time-bound entry rights to the PMS instead of evaluating at the gate in real time. Lower latency, fewer dependencies.

Pattern A

Realtime lookup

License plate read at the barrier → sent to Yedem in real time → Yedem evaluates → response back to PMS → barrier lifts. Synchronous, network-dependent.

Pattern B · Preferred

Reservation-based access list

Yedem pushes entry rights (LP, RFID, or other identifier) to the PMS with time-bounded validity. PMS notifies Yedem on entry/exit.

  • Push entry rights via API · time-bound
  • Revoke on cancellation
  • onEnter / onExit events close the reservation loop

Production today. Pipeline tomorrow.

Live integrations with four major PMS vendors cover the bulk of the CEE market. API-open vendors enter the pipeline through customer-driven priority.

● Production

Live integrations

Green Center
AnthonyApp
Parknito
Cross
In Progress

In talks · API open

Autoguard
Custom special builds
Known

Not yet integrated

AS Parking
Capcom
CallSys
Ateas (image only)

Five fallback options when LPR fails.

Bad weather, dirty plates, missing front plates — LPR isn't always reliable. Yedem supports every common backup method, picked based on what hardware the building already has.

R
RFID Card
Tap existing building card at the reader. Most common today.
P
PIN Code
Enter code at keypad on the terminal.
Q
QR Code
Generated in app, scanned by terminal.
A
In-App Button
Open barrier directly from Yedem app.
● Live
C
Reception
Staff enters LP manually or opens remotely.

No ACS dependency. Standards-based identity.

Yedem doesn't require an ACS integration to provision users. Two paths cover every customer profile — enterprise IdP for scale, email/password for simple deployments.

Preferred · In Production

SCIM with customer IdP

Standards-based provisioning from Entra, Okta, or any SCIM-compatible IdP. Automated, keeps users and priorities continuously in sync. Already deployed in enterprise production environments.

Entra · Okta · SCIM 2.0
Fallback · Simple Setup

Email + password

Users sign in directly — no SSO, no IdP wiring. Good fit for smaller customers, mixed-tenant buildings, or projects where touching customer IT is a blocker. Admin invites or pre-creates accounts.

Zero IT dependency

The integration moat compounds with every deployment.

Each PMS we ship in production becomes a repeatable wedge for the next building that runs the same hardware. The customer doesn't choose between Yedem and their existing stack — Yedem makes the existing stack smarter. That's why land & expand works at 100% pilot conversion.