The contextual core of your operations
A namespace-aware broker and contextual historian in one.
Synapse takes in your metrics and events and files each one against the equipment it came from: a specific pump, line, or site, never an anonymous tag. So every reading shows up with its context already attached. And the same system that moves your live data stores its full history and answers questions about it. One source of truth. One place to query.
[ one platform ]
Broker, historian and query engine on one model
Synapse routes your live data, keeps the history, and answers questions about both, all on one shared model. That's usually three separate systems with three copies of your plant layout to keep in sync.
Here it's one, with nothing to reconcile between them.
01 // QUERY
A query language for your plant's graph.
HQL reaches live values, history, events, and the relationships between equipment in one syntax. You pick a set of things, say 'all pumps under the EU site supplied by Siemens,' then ask for the shape you want back: the current value, a time range, an hourly average. The language stays small because the graph carries the context. It can also describe its own model, which is how query builders and dropdowns populate themselves.
02 // STREAM
One call. History, then live.
A single subscription hands back the current state, then streams every change after it, with no gap at the handover. The live phase stays computed: a 5-minute average keeps recalculating, a total-by-vendor rollup re-folds as equipment moves between groups, a live top-10 re-ranks itself. If the connection drops, your app resumes exactly where it stopped. Nothing missed, nothing doubled.
03 // MODEL
Your model, your hierarchies.
Synapse represents your infrastructure as equipment and the relationships between them. Bring the modeling standard your industry uses, such as ISA-95, ISA-88, or CIM, install it as a template, or define your own from scratch. The engine assumes none of them. Run several at once and a single asset sits in more than one hierarchy at the same time, so an operations view and a maintenance view describe the same equipment without copying it.
04 // STABILITY
Safe renames, guaranteed.
Every piece of equipment keeps a permanent internal identity, separate from its name and its place in the hierarchy. Rename a pump or move it to another line, and the dashboards and integrations watching it follow along on their own. Subscriptions tied to an entity survive every rename, and old paths keep resolving. Reorganizing the plant is a modeling decision with no fallout downstream.
One binary, one database
Time travel
Works with your existing gear
Grafana-ready, no code
Priced per environment. Not per data point.
One Synapse environment is one flat annual fee. We don't meter tags, signals, messages, throughput, VMs, pods, or nodes. Capacity scales with the hardware you provision, and the price stays the same whether you run a hundred signals or a hundred thousand.
Two ways to run it
Self-hosted
from
€18,000
per year per environment
Run Synapse on your own infrastructure, on-prem, at the edge, or in your cloud. The flat fee is the whole cost.
Resilience pack
plus
€4,500
per year per environment
One pack covers an unlimited HA, standby, DR, and read-replica topology. Run as many replicas as your architecture needs. Replica count is a design decision, not a licensing one.
Managed SaaS
from
€19,500
per year per managed instance
We host and operate it. HA, backups, and DR are already in the price, and each production instance includes 100 GB of retained history. Size up or add instances as you grow.
3-day proof of value sprint
In just three days, our team joins you on-site to connect your first machines, visualize live data, and reveal tangible opportunities for improvement.
No long contracts, no empty promises, just proof that Helixer OS delivers real value where it matters most: on your shop floor.
next step
Let our team reach out to discuss your challenges and explore how Helixer OS can help optimize your operations.