For IT, architecture, and procurement teams
Platform and security
Open standards. Your data model. Your infrastructure.
Bridge OT and IT ecosystems with a security-engineered, vendor-agnostic architecture built to ingest multi-protocol data seamlessly across vast physical environments.
Written for the review your team will run before anything is signed.
Any vendor, any protocol, at the edge or in the cloud
Building, plant, and utility protocols run through one connectivity layer. Where nothing off the shelf fits, a configurable driver handles the source.
BACnet/IP
DNP3
REST
IEC 60870
Allen-Bradley
Yokogawa
Modbus
SNMP
SOAP
IEC 61850
Mitsubishi
GE
OPC
MQTT
HL7
Siemens
Omron
Honeywell
Your model stays yours
TwinWorX builds a knowledge graph of your assets and how they relate, on the open ontology your domain uses: RealEstateCore, ASHRAE 223P, BRICK, Project Haystack, ECIM, SSO, and others. Where you already have a model, it maps to it.
The model belongs to you, not to an e-Magic schema. If you replace us in ten years, you keep the asset you paid to build.
Your tenant, our tenant, or your own servers.
All three are supported configurations, not special cases. Healthcare, government, and industrial clients have each chosen on premise.
Your Azure tenant
Runs in your subscription
Under your identity provider and data residency, bought through your existing Microsoft agreement.
e-Magic's Azure tenant
We host and operate it for you
No Azure capability to build, no operational load, and not shared with other clients.
On premise
Runs on your own servers
For regulated or air-gapped environments, with no cloud connection required.
IN YOUR OWN TENANT
Who owns the subscription?
You do.
Who holds the identity provider?
You do.
Where does the data reside?
Your tenant, your region.
What can e-Magic see?
Only what you grant.
A language model never acts on your building
It proposes; a deterministic engine disposes. The language model writes rules your engineers can read before they run, and the rule engine checks each one against safety limits and interlocks. Where they conflict, the limit wins, on the record.
TwinWorX Copilot, our assistant and not Microsoft's, runs on any LLM endpoint, including the model your organization already governs. On your own endpoint:
No AI sub-processor to declare
No training on your data, because it never reaches a third-party model
Your existing approval is the approval
No inference markup; model cost stays in your account
Answers are only as good as the model you supply, so we ask which one early.
Go deeper: bring your own language model →
Security, designed with your team
Topology, segmentation, and identity are decided with your IT team, not handed to them.
Encrypted
TLS in transit, encrypted at rest.
Role-based access
Every user authenticates; permissions follow the role.
Audit logs
Who saw what, and who changed what.
OT kept apart from IT
The edge opens every connection outbound from your OT network, so nothing on the cloud side can open a session into your building systems
Life-safety stays read-only
Code-mandated systems stay in their native systems. TwinWorX supervises; it is never in their control path.
Seven writeback controls
Per-point enablement, elevated authorization, rate limiting, readback confirmation, reversion to local control if communication drops, immutable audit, and manual override.
Buying through Microsoft or Carahsoft
TwinWorX is listed on the Azure Marketplace and Microsoft AppSource and co-sold by Microsoft, so committed Azure spend can be applied to it. U.S. public sector buyers can purchase through Carahsoft.
Bring your security questionnaire.
Thirty minutes with one of our engineers, with your architecture or security lead in the room. We will walk through topology, identity, and segmentation for your environment.
Prefer to read first? The platform technical overview → · ← How it works