Connect the systems industry already depends on
From PLCs on the plant floor to GIS, CMMS/EAM, LIMS, ERP, BI, APIs, MCP, cloud storage, and edge systems. TwinEdge turns disconnected systems into one operating layer.
Integration proof
Connect existing systems once, then use the context everywhere.
TwinEdge is designed to sit across the industrial stack customers already own: OT protocols, historians, GIS, CMMS/EAM, LIMS, ERP, BI, cloud storage, APIs, MCP, edge runtime, alerts, and field systems.
OT + IT
Source coverage
Protocol, enterprise, spatial, lab, file, cloud, and API sources.
One
Asset context
Signals, records, documents, and work align around the same asset model.
Many
Consumers
Operations, EAM, Field, BI, agents, apps, and regulators use the same record.
Integration Ecosystem
Industrial Protocols
OPC UA
Universal industrial protocol, server and client
Modbus TCP/RTU
Legacy device connectivity
MQTT
IoT messaging and edge-to-cloud telemetry
File / CSV
Batch exchange for historian exports, lab files, and no-cloud sites
Identity & Access
Microsoft Entra ID
SSO and OAuth 2.0
SCIM 2.0
Automated user provisioning
Custom OIDC
Any OpenID Connect provider
API Keys
Programmatic access with scoping
Analytics & BI
BI Studio
Built-in dashboards with RLS
Custom Dashboards
Drag-and-drop widget builder
Analytics Library
Custom formulas and KPIs
Parquet Export
Edge data export for data lakes
Cloud & Storage
AWS S3
Model and data storage
Azure Blob Storage
Data import/export
Azure Event Hubs
Streaming telemetry
RDBMS
Time-series analytics
Cloud Historian
Centralized time-series sync
Notification & Alerting
Email (SMTP)
Alert notifications
SMS (GSM modem)
Critical alerts via serial modem
Slack
Channel-based alert routing
Webhooks
Custom HTTP callbacks
MQTT
Machine-to-machine alerting
GPIO/LED
Physical indicators on edge device
DevOps & Monitoring
Prometheus
Metrics collection
Grafana
Visualization dashboards
Loki
Log aggregation
Docker
Containerized deployment
OpenTelemetry
Operational traces and observability signals
API Overview
Comprehensive API for custom integrations and automation.
API Features
Custom Integrations
REST API
Comprehensive REST API with OpenAPI specification for any custom integration.
Webhook Events
Subscribe to 25+ event types for event-driven integrations and automation.
MCP and REST Connectors
Productized connectors that expose governed operational context to agents, apps, and internal systems.
Professional Services
Custom integration development with 4-12 week delivery timeline.
Integration Development Process
Requirements
Define integration scope and data flows
Development
4-8 weeks for custom integrations
Testing
Validation in staging environment
Deployment
Production rollout and monitoring
Quick Start Example
import requests
# Authenticate
response = requests.post(
"https://api.twinedgeai.com/auth/login",
json={"email": "you@company.com", "password": "***"}
)
token = response.json()["access_token"]
# Fetch asset data
headers = {"Authorization": f"Bearer {token}"}
assets = requests.get(
"https://api.twinedgeai.com/api/v1/cmms/assets",
headers=headers
).json()
# Get real-time sensor data
for asset in assets:
data = requests.get(
f"https://api.twinedgeai.com/api/v1/asset-physics/{asset['id']}/current",
headers=headers
).json()
print(f"{asset['name']}: {data}")Need a Custom Integration?
Our engineering team can build custom integrations tailored to your requirements.