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.

Qynetic is in early development. This page describes the intended design; capabilities marked as planned are not yet generally available. The connector contract is defined; individual connectors are delivered over time and are not claimed here until available.

Designed protocol coverage

• MTConnect
• OPC UA
• MQTT
• REST
• GraphQL
• Webhooks
• WebSockets
• TCP
• Modbus TCP
• Databases
• File imports (CSV, XML, JSON)
• Industrial gateways

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, CRM
• Scheduling systems

What provenance is kept?

For every imported value Qynetic is designed to retain where it came from, when it was generated, when it was received, which source object produced it, whether it was transformed, and how confident the mapping is. Vendor identifiers are stored separately from Qynetic's internal identifiers.

What is Qynetic Edge?

Qynetic Edge is a planned service installed inside the factory network. It runs connectors close to equipment, buffers data during connectivity loss (store-and-forward), and makes only outbound, secure connections to Qynetic Cloud. Loss of the cloud must not create unsafe machine behaviour.