OEE & downtime intelligence
Capture every stop with its real reason, not the one someone remembered at end of shift.
Discrete manufacturingThe unified industrial data platform
Every signal on your plant floor, in one live namespace
QUBIQ connects OPC UA, MQTT, Modbus and your databases into a single real-time tree — then gives you pipelines, operator screens, alarming and a historian on top of it. An AI assistant reads that same tree, so questions get answered from live data rather than from a document. Unlimited tags. Unlimited clients. One licence.
- Installs in under 3 minutes
- No per-tag licensing
- AI and 3D twin reading the same live data
qubiq · namespaceLIVE
- Northwind
- Site-Chelmsford
- Packaging
- Line3
- FillerRUNNING
- Torque18.4 N·m
- FillWeight502.1 g
- RejectRate0.42 %
- CapperRUNNING
Torque · 60 s
- Quality
- GOOD
- Rate
- 250 ms
- Source
- OPC UA
Reads and writes the systems you already run
- PostgreSQL
- MySQL / MariaDB
- Microsoft SQL Server
- SQLite
- MongoDB
- QuestDB
- 7
- Industrial protocols
- 57
- Built-in widgets
- 0
- Runtime dependencies
- 0
- Per-tag fees
OPC UA, MQTT, Sparkplug B, Modbus, SNMP, TCP/UDP and REST — all in the base install.
Charts, tables, forms, maps, HMI and P&ID symbols, 3D and vector drawing.
One binary. No JVM, no runtime to install, no per-driver licence.
Licensed per server. Adding a signal never changes the price.
How it works
From raw signal to decision, in four moves
The same four steps whether you are instrumenting one line or forty plants. Each one is a place you can stop and still have something useful.
- 01
Connect
Point QUBIQ at a PLC, a broker, a meter or a database. Drivers are pooled, reconnect on their own and report their own health.
- 02
Model
Define an asset type once, instantiate it everywhere. Raw addresses become Site/Line3/Filler/Torque — readable by anyone.
- 03
Build
Compose pipelines and operator screens against the model. Live values render on every wire while you are still building.
- 04
Operate
Alarm it, historise it, secure it, and roll it out to a fleet — with staged deploys and automatic rollback.
Watch
See it running before you install it
The same four moves, done live — from a raw OPC UA tag to a dashboard someone on the floor actually reads.
Platform
One install, not a stack of integrations
Every capability below ships in the same binary and shares the same namespace. There is nothing to bolt together, and nothing that stops working when one vendor changes their API.
Unified namespace
Stop translating between tag names and reality
DB1.DBW24 means something to exactly one person, and they are on holiday. A typed namespace means the pump on Line 3 is addressed the same way at every site — so screens, scripts, reports and your data team all agree without a meeting.
- Typed asset templates with inheritance
- One change propagates to every instance
- Quality codes travel with every value
- Addressable from screens, scripts and the API
AI assistant
Ask in plain language. Decide on live data.
Most industrial AI is a search box over a PDF. Ours is connected to the running system: it reads your namespace, inspects pipelines and queries history through real tools. Engineers get the answer without writing the query — and the people who sign off get it without waiting for the engineer.
- “Which pipeline writes to Line3/Filler/Torque?” — answered from the live graph
- “Why did Line 3 lose four hours last week?” — answered from history, not from a slide
- Every answer names the tags and time range behind it, so it can be checked rather than trusted
- Runs under your role, and every action it takes is logged
3D digital twin
The twin is driven by the plant, not by a diagram
Import a glTF model of the line and bind its parts to live tags. Visibility, transforms, materials and animations all follow namespace values — the same values feeding your trends and alarms, so the model cannot quietly fall out of date.
- glTF / GLB import with part-level selection
- Bind visibility, transform, material and animation to tags
- Saved camera views for operator screens
- One model shared with screens and pipelines, not a second copy
Connectivity
Speaks the plant floor natively
Certified implementations, not thin wrappers. Every driver is pooled, buffered and observable — and reports its own health as a tag you can alarm on.
- OPC UAIndustrial
Client with subscription batching and pooled sessions.
- MQTTIndustrial
MQTT client, pooled and buffered, with automatic reconnect.
- Sparkplug BIndustrial
Primary host: birth/death certificates, sequence and state.
- Modbus TCP/RTUIndustrial
Master with scan grouping and explicit byte-order control.
- SNMPNetworked
v1/v2c/v3 polling and traps, with a built-in MIB compiler.
- TCP / UDPNetworked
Raw sockets for the devices that speak nothing standard.
- REST / HTTPIT
Inbound routes and outbound calls, both scope-controlled.
Solutions
What your team can build
These are the six projects that pay for the platform. Most sites start with one and expand once the namespace exists.
Energy & utilities monitoring
Meter every asset, allocate every kilowatt-hour, and see cost per unit produced in real time.
Cross-industryCondition & predictive maintenance
Trend vibration, temperature and current draw against the asset model — and alert before the failure.
Process & discreteBatch records & quality
Electronic batch records assembled from the process data you already collect.
Pharma & food3D digital twin
A model of the line driven by the line — bind a glTF model to live tags.
Cross-industryInfrastructure monitoring
Bring switches, UPSs and PDUs into the same namespace as the process.
Cross-industry
Design partners
We would rather have ten plants that work than a logo wall
We would rather build against real plants than collect logos. Design partners get a named engineer, direct influence on the roadmap, and licence terms fixed for the life of the deployment.
- A named engineer on a shared channel, not a ticket queue
- Your protocols and edge cases prioritised on the roadmap
- Licence terms fixed for the life of the deployment
- No obligation to reference us publicly — ever
More from the engineering team
Protocol walkthroughs, deep dives and recorded sessions.
From the blog
Field notes from people who commission plants
Architecture, protocols and post-mortems — written by our engineers, not by a content agency.
Architecture3 min readDesigning a unified namespace that survives contact with the plant
Most UNS designs fail in month three, when the second site does not fit the model. Here is the hierarchy discipline that prevents it.
Administrator · 27 Jul 2026
Protocols3 min readSparkplug B state management, explained without the spec
Birth certificates, death certificates and the primary host. What each one actually does, and the three mistakes that cause phantom stale data.
Administrator · 20 Jul 2026
Protocols3 min readYour OPC UA connection is slow because of monitored items, not bandwidth
Adding 40,000 tags one at a time takes eleven minutes. Batched, it takes nine seconds. Here is what the server is actually doing.
Administrator · 12 Jul 2026
Questions
The things people ask before downloading
What exactly is QUBIQ?
An industrial data platform. It connects to your PLCs, meters, network gear and databases, organises everything into one live namespace, and gives you a pipeline designer, operator screens, a 3D digital twin, alarms and a historian on top of that namespace — in one install, with one licence.
How mature is this? Who is already running it?
QUBIQ 1.0 is released and generally available. We are a young company and will not pretend to an install base we have not earned — you will not find invented customer logos on this page. What we can show you is the software: download it, connect it to your own equipment, and judge it directly.
Which protocols are actually supported today?
OPC UA (client), MQTT with a Sparkplug B primary host, Modbus TCP/RTU (master), SNMP v1/v2c/v3 including a MIB compiler, raw TCP/UDP, REST, and SQL/MongoDB/QuestDB databases. Siemens S7 and EtherNet/IP are not supported yet — if you need one of those, tell us and it will inform what we build next.
What is the 3D digital twin actually doing?
Importing a glTF or GLB model and binding its parts to live tags: visibility, transforms, materials and animations all driven by namespace values. It is a widget on the same canvas as your trends and alarms, reading the same data, so it cannot drift out of step with production the way an exported model does.
How long does it take to get running?
The installer is a single binary with no runtime to install. Most engineers have a live tag on screen within fifteen minutes, using either their own OPC UA or MQTT endpoint or the built-in simulator.
Do I have to replace my existing SCADA?
No. QUBIQ is designed to sit alongside an incumbent system — reading from it over OPC UA or MQTT, adding the namespace, historian, 3D and analytics layer — so you can evaluate it without touching anything that is running production today.
Is there really no per-tag licensing?
Correct. Licensing is per server. Tags, clients, screens and pipelines are unlimited on every edition — what you pay for is the server and the modules you switch on, never the number of signals.
Install it in three minutes and see your own data
The download is the whole platform — every feature is enabled and there is no card to enter. Connect it to your own equipment and see for yourself.