Integrations
How does Qynetic connect to machines and systems?
Qynetic is integration-first. Its core never depends on a specific vendor, protocol or database: connectors read from a source and normalisers translate what they read into canonical events and entities that every module consumes. Connectors can run in the cloud or in Qynetic Edge inside the factory network.
The connector contract is defined. Individual connectors are delivered over time and are not claimed here until they are available.
01 Source
A machine, gauge, CMM, PLC, database, file or enterprise system.
02 Connector
Speaks the source's protocol and produces raw records with their origin.
03 Normaliser
Maps vendor-specific data to canonical events and entities. Unmappable data is reported, never silently dropped.
04 Event log
Consistent event envelopes with source, timestamps, schema version and idempotency.
05 Modules and agents
Quality, OEE, tooling and the rest consume one model regardless of source.
Designed protocol coverage
MTConnect
Read-only machine tool data in a common vocabulary.
OPC UA
Rich, secure industrial communication with information models.
MQTT
Lightweight publish/subscribe messaging for machine and sensor data.
REST and GraphQL
APIs of enterprise and measurement systems.
Webhooks and WebSockets
Event-driven integrations.
Modbus TCP and TCP
Devices that speak simpler industrial protocols.
Databases
Read from existing quality, tooling or ERP databases.
Files
CSV, XML and JSON imports and exports.
Industrial gateways
Data already aggregated by a gateway.
Designed system coverage
- CNC machines
- PLCs
- Robots
- CMM and optical inspection
- Vision systems
- SPC systems
- Tool management and presetters
- Sensors and energy meters
- Maintenance systems
- ERP, MES, QMS, WMS, PLM and CRM
- Scheduling systems
Provenance for every value
For imported data Qynetic is designed to retain the answers to six questions:
- Where did this data come from?
- When was it generated at the source?
- When did Qynetic receive it?
- Which source object produced it?
- Has it been transformed?
- How confident are we in its meaning?
Qynetic Edge
Qynetic Edge is a planned service installed inside the factory network. It handles:
- Local machine connectivity and protocol adapters
- Buffering and store-and-forward during outages
- Normalisation close to the source
- Secure, outbound-only communication to Qynetic Cloud
- Command validation and deterministic execution where appropriate
- Connection health reporting
Integration principles
Read first
Read-only monitoring is the simplest and safest first step. Any path that can write to a machine is treated as safety-relevant.
No vendor lock-in
Vendor names are examples of what a connector can talk to, never hard-coded assumptions in the core.
Credentials stay out of config
Connector configuration holds a reference to a secret store, never the credential itself.
Be among the first to know
Qynetic is being built now. Join the waitlist and we will tell you when it is available.