Interoperability
Built to connect, not to replace. iViRTH is designed to work alongside the systems you already run.
What it can connect to
Integrations are documented by actual availability for each project; nothing below is a blanket claim.
IoT and sensors
Devices, gateways and edge devices.
APIs
Systems that expose interfaces.
GIS
Maps and geospatial data.
Enterprise systems
Facilities, asset and operations software.
Identity systems
Institutional and enterprise identity.
Databases
Existing data stores.
Cloud platforms
Public and private cloud.
Applications
Campus, tourism and domain apps that use the platform.
Where it can run
Chosen per project against data, latency and governance needs.
Cloud
Managed infrastructure.
On-premise
Inside your facilities.
Edge
Close to the device, where installed and validated.
Hybrid
A defined boundary between site and cloud.
Private infrastructure
Customer-controlled environments.
Data residency, private deployment and customer-controlled environments are scoped options, not claims that every deployment already provides them.
Design principles
Open APIs
Documented interfaces where they are available.
Modular architecture
Add capabilities without redesigning the base.
Data portability
Your data can leave as well as enter.
Identity separation
Identity (Helix) kept apart from measurement (ViSE).
Role-based access
Least-privilege, role-aware access.
Permissioned data sharing
Share only with consent and purpose.
Standards position
iViRTH's architecture is designed with reference to emerging international digital-twin and interoperability standards, rather than as a closed proprietary island. We do not claim certification or compliance with any standard unless it is independently substantiated and stated with its scope.
For developers
Reference integration flow and API areas.
- Create twin
- Register asset
- Connect telemetry
- Synchronise state
- Query twin
- Trigger experience
- Record event
| API area | Purpose | Availability |
|---|---|---|
| Twin | Create, read and relate twins | To be confirmed |
| Identity | Identities and verification | To be confirmed |
| Asset | Register and manage assets | To be confirmed |
| Telemetry | Ingest and query readings | To be confirmed |
| Geospatial | Place and map context | To be confirmed |
| Experience | Trails, challenges and events | To be confirmed |
| Credential | Issue and verify credentials | To be confirmed |
The flow above is the reference design. API documentation and access are provided per project once availability is confirmed. Ask for an integration brief: hello@ivirth.in.
Planning an integration?
Tell us the systems involved. We will say which connections exist, which are in design and what a pilot would cover.