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.
Sound familiar?
The work nobody signed up for.
If you have said one of these this month, the rest of this page is for you.
The same customer exists three times, in the CRM, the ERP and the ticketing tool, with three spellings.
Every new integration is a project with a budget and a six-month wait.
The vendor renamed one field and our nightly sync failed quietly for a week.
Connecting the plant means a separate team, a separate budget and a separate vendor.
I want to try a use case on real data before I fund an integration project.
Use cases
What you would use it for, first.
Each one starts from a problem you can name, and ends with something a person can see has changed. Live means it runs in the product today; pilot means we build it with you.
- 01
A business system, live in an afternoon
Live todayTodayTrying a use case on real CRM or ERP data normally waits for an integration project.
With the platformPick one of the 41 business systems in the catalog and connect it with your own credentials. It switches from sample data to live, pages through every record, and the credential is sealed in the vault, never shown again.
What changesYou test the use case on your own records first, and fund the project second. Budget days, not minutes, for the first connector on a new system.
- 02
Drift caught before it breaks a sync
Live todayTodayAn upstream schema changes and a pipeline fails without telling anyone.
With the platformThe connector compares what the system returns with its manifest, proposes a patch when resources appear or disappear, and keeps the previous version so a bad patch rolls back.
What changesA schema change becomes a reviewed patch, not a week of missing data.
- 03
Machines in the same model as the business
Live todayTodayPlant data and business data live in different worlds with different teams.
With the platformMachines come in live over OPC UA and MQTT Sparkplug B through the edge, and land in the same model as your business systems, so a machine signal can drive a business action.
What changesOne governed layer instead of two integration programs.
- 04
MES, CMMS, historian and the rest of the plant
Built in a pilotTodayYour MES, CMMS, historian and controllers speak protocols the catalog only has on sample data.
With the platformIn a pilot we take the catalog entries your stack needs, Modbus, MTConnect, vendor controllers or a historian API, from sample data to live on the same manifest and governance.
What changesThe systems you run join the model without changing the system of record.
Business value
Where the return comes from.
The levers, and the range other organizations have published for each. Ranges are typical of the category, not a promise and not our customers' results.
Systems left unconnected
only 29% connectedThe average enterprise runs hundreds of applications and connects under a third of them. Vendor-sponsored survey.
MuleSoft (Salesforce), with Vanson Bourne & Deloitte Digital, 2025 Connectivity Benchmark Report (2025)Data silos that hurt the business
90% say soNine in ten IT leaders say silos create business problems. Vendor-sponsored survey.
MuleSoft (Salesforce), with Vanson Bourne & Deloitte Digital, 2025 Connectivity Benchmark Report (2025)Cost of poor data
$12.9M a yearWhat organizations believe poor data quality costs them. Fewer copies, typed by fewer people, means fewer errors to pay for.
Gartner, Data Quality: Why It Matters and How to Achieve It (2020)Time to try a use case
Days to the first live connector instead of a project to scope one. Measure it on your first system.
Run your numbers
Hours your people spend moving work between systems.
Every input is yours to change, and the arithmetic is shown in full. Nothing is hidden in a multiplier.
12 × 6 × €55 × 40% × 46 working weeks = €72,864
An estimate on the numbers above, not a measurement and not a customer result. In an Operations X-Ray we replace the assumptions with figures measured on your own systems.
Before and after
The same week, run differently.
A use case waits for an integration project.
A use case runs on your own records within days.
A schema change breaks a sync quietly.
A schema change arrives as a patch you approve, with rollback.
Credentials live in scripts and wiki pages.
Credentials are sealed in the vault and never shown again.
Plant and business data have separate integration programs.
Both land in one governed model.
Capabilities
What you get.
CRM, ERP, HRIS, ITSM, data systems and REST APIs sit beside machines read live over OPC UA and MQTT Sparkplug B, normalized to one model. Modbus, MTConnect and vendor controllers are in the catalog on sample data and are built for your stack in a pilot.
Give the generator an API's OpenAPI spec and it produces a governed connector, with the object mapping, auth and write surface inferred.
A live HTTP and OAuth connector turns a web API into a usable source. Expect days, not minutes, for the first connector on a new system.
When an upstream schema drifts, the connector detects it, proposes a patch, and can roll back, instead of silently breaking a pipeline.
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.
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.
The manifest is instantiated into a working connector with mock data for instant exploration and a live path for production.
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 starts from a description, not a rewrite.
- 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.
The catalog has 68 connectors: 41 business systems with a live REST/OAuth path and 27 machine protocols and vendors on sample data. Machines are live today over OPC UA and MQTT Sparkplug B. Connectors generated from an OpenAPI spec and the live HTTP connector cover more of the long tail.
Tokoaido reads what a use case needs and keeps a working model of it. You can self-host with Docker or Kubernetes so data stays on systems you own.
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.
More platform capabilities
Operations X-Ray
Connect one system of yours.
Pick the system a first use case needs. We connect it with you, live, and show the use case running on your records.