“AI-native from day one — talk to the controller / server API via AI.
“No worse than Kisi. Beat Kisi, Salto, HID.
“Aliro-ready. Mobile apps. Modern standards.
“Fewest hires, maximum automation — the only-key-hire team.
The deeper thing underneath
You don't need a Kisi clone. You need the layer none of them own.
Beautiful at the door. Open at every standard. AI-native to the API. Local to the region — and you own the credential + policy brain none of the incumbents own.
Three things I want you to leave today believing
01
I understand what you're building.
02
You can trust me — because I'll show you, not tell you.
03
I can actually build this — solo, with AI, fast.
Beat 2 — Aliro first
Aliro is Matter — for door keys.
Open across Apple, Google, and Samsung wallets
NFC + BLE + UWB
A CSA standard — 1.0 published Feb 2026
But here's what almost everyone misses
Aliro standardizes the door protocol. It does not govern the credential.
So lock-in doesn't disappear. It moves — to whoever issues the credential, manages its lifecycle, and writes policy over it. That layer is the customer relationship. That layer is ours.
Why it's specifically winnable for SD
Founding Aliro member
NXP
+
SD's NFCKEY chip supplier
NXP
Your silicon path to Aliro is already friendly. The standard, the chip, and the credential layer line up for you specifically.
What the user actually feels
Tap your phone or watch — in any wallet — at the door.
Walk up hands-free over UWB — the door knows it's you.
One credential works at every reader.
An operator issues — or kills — a wallet key in seconds.
The platform, one map
Credentials
Aliro · Wallet · NFC · BLE · UWB · Card · PIN
issuance + lifecycle
Access
People · Groups · Levels · Schedules
Doors & Devices
Sites · Zones · Readers · Health
Live Monitoring
Event feed · Alerts
Audit & Reports
Immutable log · Compliance
Visitors
Temp access · Invites
AI Console
Run by talking
Admin
Multi-tenant · Installer · MSP
StoneID
End-user mobile app
Three tiers, so you can see the shape of the bet
Spine
Table-stakes — the floor we clear
Full management surface
OSDP v2.2.2 + PKOC
Mobile-first apps
SCIM / SSO
SOC 2 Type II
Differentiators
Where we win
AI-native MCP layer
Offline-first (beats midnight sync)
Open standards on every layer
Installer / MSP portal
SEA data residency
Frontier
The lead
Event-stream intelligence
Agentic ops
Predictive maintenance
Open API / SDK
Forward-thesis agent
Direction, not a decree
This is where I'd start.
You're bringing an architecture sketch —
where does this collide with how you'd build it?
Co-creation hook
Live demo
Running on mock data. Click it yourself after.
What launches
The WaveOC prototype app
[ PROTOTYPE URL ]— replace before the meeting
Demo order
Surface→Aliro credential flow→AI console→Cut the cloud
That was real. Here's what you saw.
Real surface
Aliro credential issue → revoke
AI runs the building (NL policy, NL audit, MCP, governed)
Beats Kisi's midnight sync
Mock data — no real hardware, no deployed backend. The architecture is real; the build timeline is ours to set.
Beat 4 — How we win
The differentiation map
AI-native
AI-add-on
Proprietary / closed
Open standards
HID
Verkada
Kisi
WaveOCSD's whitespace
AI-native × open standards: no incumbent shares our quadrant. Add design-led and SEA-residency — the whitespace is ours alone.
The four axes, fast
Beautiful at the door
Corian; the one axis no software competitor copies.
The MCP layer you just saw — not a chatbot bolted on a 2000s platform.
Local to the region
SG/MY data residency + tenant data-region selection.
The proof points a partner will respect
Verified
Offline: we propagate a new credential in seconds — Kisi waits until midnight.
vs Kisi's midnight-sync specifically — errata-safe
Verified
AI-native: as of now, no access vendor ships an MCP server — your literal ask is an MCP server.
Re-verify week-of; phrased as "as of now," not eternal "first"
Table-stakes
Compliance: we match SOC 2 Type II; the real edge is SEA data residency the US clouds under-serve.
Kisi already has SOC 2 Type II — we match, we don't leapfrog
The channel truth
The installer decides whether ACaaS gets deployed.
A beautiful reader is the easiest upsell an integrator ever made.
Installer / MSP portal — white-label, RMR, commissioning.
The Corian story isn't just an end-user feature; it's a channel weapon.
Governance + the leaver-flow
SCIM leaver-flow
Not a convenience — the fix for the #1 access failure: the fired employee who still badges in.
Governed AI
Human-in-the-loop on any door action; full AI-action audit log (agent / model / tool / approval / result).
One more thing
“Research the competitors, keep an eye on the market.”
You asked me to do this.
Following
Summarize what competitors did.
Everyone can do this. It's reactive.
Leading
Synthesize where the niche is going, and move first to exceed what users expect.
I don't want to build you a competitor-news summarizer. I want to build you a product strategist that tells you where to go next — and why.
The forward-thesis agent.
Synthesizes competitor moves + user / market signals + standards & tech trajectory
→ forms a POV on the future of the niche
→ proposes leapfrog moves that exceed expectations.
How it works
Research
→
Triage
only meaningful, forward-leading theses
→
Emit
each with its reasoning shown
It shows its work. A strategist, not a fortune-teller — the reasoning is what you trust, not the prediction.
It runs as a skill on a loop in a separate Claude session — not a server farm. Small mechanism, big output.
Living proof
This session already produced exactly these theses — I used it to build this meeting.
What launches
The forward-thesis agent thread
[ AGENT THREAD ]— replace before the meeting
Four real theses already produced:
Own the credential seam Aliro leaves open
Ship an MCP server — as of now no vendor has one
SEA-residency moat
Beat Kisi on its midnight-sync gap
Everything you just saw —
The competitor teardowns — HID, Kisi, Salto, Verkada, the standards.
The platform concept + this deck.
The running prototype — Aliro flow, AI console, MCP, offline.
The forward-thesis agent.
Me + AI. Solo.
~48 hours.
This is the only-key-hire company you described — already running.
That's the 10% bet.
Beautiful at the door. Open at every standard. AI-native to the API. Local to the region. Built by a team of one, amplified.