Platform · Connect

Connect every system, from the plant floor to the back office.

One manifest-driven connector layer for the business apps and the machines your operation already runs on. Read what matters, write only through governance.

What it is

A connector in Tokoaido is not a brittle point-to-point script. Every source system is described by a typed manifest that declares its objects, how they map into one shared model, its auth, and its compliance envelope. A factory turns that manifest into a working connector, so a new system is a description, not a rewrite.

Capabilities

What you get.

IT and OT in one layer

CRM, ERP, HRIS, ITSM, databases and REST APIs sit beside OPC UA, MQTT Sparkplug, Modbus and MTConnect machines, normalized to one model.

Connector from docs

Point the generator at an API's documentation and it produces a working, governed connector, with the object mapping, auth and write surface inferred.

Anything REST

A live HTTP and OAuth connector turns any web API into a usable source, so the long tail of systems is never a blocker.

Self-healing

When an upstream schema drifts, the connector detects it, proposes a patch, and can roll back, instead of silently breaking a pipeline.

Governed writes

Reads flow freely; every write is a governed action, proposed and approved at the right risk tier. The plant-floor safety boundary is never addressable.

How it works

Three moves.

01
Describe the system

A typed manifest declares objects, auth, mapping and data classes. Business apps are pull-API connectors; machines are streaming or edge connectors with an ISA-95 asset model.

02
The factory builds it

The manifest is instantiated into a working connector with mock data for instant exploration and a live path for production.

03
It stays healthy

Drift detection, versioning and rollback keep the connector working as upstream systems change.

Why ours is different

The part competitors leave out.

  • Manifest plus factory means a new connector is a description, not weeks of engineering.
  • One layer spans IT systems and OT machines, so a plant-floor signal can drive a back-office action.
  • The safety boundary is structural: a direct PLC or Safety Instrumented System write is not expressible.
Questions

Frequently asked.

How many systems are supported?

The catalog ships with dozens of connectors across IT and OT, and connector-from-docs plus the live HTTP connector cover the long tail. It is built to grow.

Do you store our data?

Tokoaido reads what a use case needs and keeps the governed model. Deployment options include self-hosted and air-gapped so data can stay on systems you own.

How are machine connectors kept safe?

OT connectors carry a safety block: reads are permitted, any write is routed through MES or SCADA with approval, and the Safety Instrumented System is never addressable.

See it on your own operations.

Book a working session with our team, or start with a free Operations X-Ray of your systems.