01Placement
Browse the current placement
Use the namespace to understand current operational context without making the path the object's permanent identity.
novasteelhot-rollingline-01coil-1042
UNS OpenHub platform
A shared context
that survives change.
UNS OpenHub gives operational data stable identity, an understandable place in a Unified Namespace (UNS), and relationships that remain useful as the surrounding systems change. The core is domain-neutral, not limited to a single industry.
Namespace + relationship graph
Separate what an object is
from where it is now.
Paths make the present easy to browse. Stable identity and time-aware relationships preserve lifecycle and lineage through moves, renames, and source-system changes.
02Identity
Keep the same object through change
A stable entity ID remains constant while namespace placements and external identifiers evolve with the real system.
Stable entity
ent · 7f3a…1042 hot-rolling / coil-1042 warehouse / coil-1042
03Relationships
Query lifecycle and lineage
Typed, time-aware relationships connect processes, batches, and material. When a process produces a new object, record its lineage rather than treating it as a renamed input.
ProcessproducesBatch 42containsCoil 1042
One generic core
Add the vocabulary your domain needs.
The core keeps identity, placement, relationships, provenance, and lifecycle domain-neutral. Domain packs add specific vocabulary without changing the platform.
Deliberate layers
Keep meaning separate
from deployment.
Each layer has one job. This keeps the generic platform reusable while domain models, integrations, and deployment choices evolve independently.
Governed context
Identity, Schema, relationships, packages, authorization, audit, and service lifecycle.
Shared vocabulary
Declarative object types, attributes, units, and relationship rules for a particular domain.
Executable integrations
Connect external systems and normalize their data without placing protocol drivers in the core.
Repeatable adoption
Choose a tested set of domain packages and optional capabilities for a particular solution or deployment.
Built for operations
Run services with
explicit controls.
Inspect health and data flow, coordinate service handover, validate compatible add-ons, and resolve secrets where workloads run.
01Continuity
Coordinate updates and recovery
Start a replacement beside the active service, drain queued work, and acknowledge handover before cutover. Opt-in guards can restart unhealthy services after defined limits.
- Drain + resume
- Health thresholds
- Observable recovery
02Visibility
See process, data, and controller health
Inspect service versions, MQTT state, memory, message counters, routes, logs, and dependencies in one control plane.
- Process + MQTT
- Logs + dependencies
- Controller health
03Deployment
Deploy compatible services
Discover official add-ons through the signed public catalog and connect operator-configured private sources. Validate compatibility and placement before deployment.
- Verified sources
- Schema + snapshots
- Placement preflight
04Secrets
Resolve secrets at runtime
Use typed references to environment variables or optional Infisical paths without placing resolved credentials in source files.
- Environment + Infisical
- Typed references
- Token refresh
Product boundary
Own the shared context.
Integrate the rest.
OpenHub does not need to replace every tool around operational data. Its role is to make identity, meaning, governance, and lifecycle consistent between them.
The governed context
- Stable identity and namespace placement
- Schema, relationships, history, and provenance
- Policy, audit, provider lifecycle, and basic data access
Specialist systems
- Device drivers, brokers, SCADA, and HMI
- Complex transformation and edge operations
- Domain analytics, visualization, and enterprise orchestration
Put it to work