TELAIA Telaia is a systems integrator specializing in applied AI. We embed reasoning agents into the infrastructure you already operate β they read live state from your equipment, decide in plain language, and act through the protocols your systems speak. Not a rules engine. Not a chatbot bolted onto a dashboard.
The models can run inside your network. Camera frames, ID scans, and telemetry never have to leave the building.
Every automation chooses: act autonomously, or queue for sign-off. The agent proposes; you decide who approves what.
We integrate with the panels, controllers, and software you already bought. The AI layer sits on top β it does not compete with your stack.
01 β What we integrate
The runtime is the same everywhere: read live state, reason in natural language, act through an approval gate. What changes per client is the connector β and connectors are the part we're fast at.
HVAC, chillers, pumps, lighting. The agent reads live points over BACnet or Modbus, reasons about comfort vs. load, and writes setpoints β with an audit trail for every decision.
One identity graph across doors, credentials, and events. Held-open gates, out-of-hours patterns, credential misuse β reasoned about, not just logged.
Registration to check-out as a real state machine. ID capture via vision-LLM OCR, host notification, badge issuance β the lobby runs itself, staff handle exceptions.
Vision models on your existing camera streams. Describe a scene in plain language, flag what matters, and cross-reference with door and visitor events.
Load profiles, tariff windows, generator and UPS state. The agent shifts what can move, flags what cannot, and explains the bill in sentences, not spreadsheets.
Documents, tickets, WhatsApp, ERP and CRM records. The same agent runtime pointed at paperwork β extraction, routing, drafting β with the same approval gates.
02 β Platforms
These aren't concepts β they're the same runtime described above, shipped as products. Every custom integration we build inherits their trigger engine, approval queue, and audit trail on day one.
Building management
Building management, operated by an LLM agent instead of static rule tables.
Visitor management
Visitor management for buildings β registration through check-out, with a real state machine.
Access control
as Aspha β by Apera Indonesia
One identity graph across visitor, tenant, and device events β door and credential activity reasoned about, not just allow/deny lists.
03 β Architecture
Read it bottom-up: your existing systems keep running exactly as they are. We layer intelligence above them β data flows up, decisions flow down, and your team stays in command at the top.
Your team
In command
What you get
Plain language
Telaia
Agent runtime
Telaia
MCP engine
Yours, unchanged
Existing systems
Every action the agents take goes through the same path your technicians use today β the native protocols your equipment already speaks. Anything sensitive waits in the approval queue until someone on your team says go.
04 β Integrations
Modbus TCP Β· RTU
ONVIF Β· RTSP OSDP Β· Wiegand
TANlock Protocol not on the list? That's a connector, not a rewrite β bring it to the walkthrough.
05 β Partnership
One of our integrations β with Apera Indonesia, the physical-security specialists behind access control, CCTV, and visitor management deployments for names like BCA, XL Axiata, and NTT.
Most sites run their security as silos β one console per hardware brand, one login per vendor, no shared picture. Aspha ends that: a canonical model with a driver per brand, the same architecture the world-class physical-security platforms use. Unified live transactions, floorplans, device topology, and cross-brand enrollment β brand becomes a column, not a system.
TANlock by FATH One question spans every brand at once β doors, readers, racks, turnstiles β because the agent reasons over the unified model, not eight separate consoles.
A forced-door alarm becomes a narrative: who badged nearby, what the cameras flagged, which credential was used β correlated across vendors in seconds.
Shift summaries, incident timelines, and compliance exports drafted from live transaction data, in plain language, on request.
"Enroll this contractor for the north wing until Friday" β the agent drives cross-brand provisioning, with every action gated by approval.
This is the partnership in one line: Apera unified the hardware, Telaia makes it reason. Apera owns the product, the integrations, and the customer relationship β we build the intelligence inside it. When eight brands already speak one language, one agent can command all of them.
06 β Working with us
A pilot is scoped in weeks, not quarters β one system, one site, real data.
You show us the system. We map its read points, its write points, and the decisions your people make around it today.
We speak to your equipment in its own protocol. Nothing gets replaced, nothing gets ripped out β the agent plugs into what exists.
The agent reasons over live data and recommends actions β every one goes to an approval queue. You watch it think before you let it act.
Automations you trust go autonomous, one at a time. The rest keep a human in the loop, permanently if you like. Autonomy is a dial, not a switch.
Tell us what you run. We'll tell you what the agent would do with it β and scope a pilot on one system to prove it.