Skip to content

Technology

  • IIoT
  • SSE
  • RFC 8628
  • Tenant isolation

Industrial IoT, built to be trusted at the asset.

Hydris is a multi-tenant platform: edge gateways push telemetry over HTTPS, the platform validates and evaluates it, and a realtime stream delivers exactly the right context to the console and to each pair of glasses.
Gateway batch≤ 500 readings
Pairing challenge5 min · single-use
RealtimeSSE + replay

/01Telemetry ingestion pipeline

Equipment to eyes, with every reading checked on the way.

  1. Plant equipment

    01

    Sensors on pumps, blowers, tanks and analyzers

  2. Edge gateway

    02

    Per-site key, HTTPS POST MQTT / OPC UA planned

  3. Ingestion API

    03

    Gateway auth, rate limits Unknown tags rejected per item

  4. Validate & normalise

    04

    Units, timestamps, quality flags Duplicate message IDs ignored

  5. Store & evaluate

    05

    Tenant-scoped time series Deadband + on-delay alarms

  6. Realtime (SSE)

    06

    Per-connection authorisation Last-Event-ID replay

  7. Operator Console

    07

    Live overview, alarms, history & CSV export

  8. Field Glasses

    08

    Asset context in view Freshness on every value

Per-item results

A batch never fails silently: each reading is accepted, flagged as duplicate, or rejected with a reason such as unknown sensor or timestamp in the future.

Idempotent & ordered

Message IDs make retries safe; out-of-order readings are stored by observation time, not arrival time.

Alarm evaluation

High, high-high, low and low-low rules with deadband hysteresis and on-delay, evaluated as readings land.

/02Context awareness

The right context for the right operator.

Who
One operator per device at a time. Reassignment clears the previous operator’s context and is audited.
Where
Only the sites and areas the operator is permitted for; events from other sites are never delivered.
What
The assets on the current round, their latest readings with freshness, open alarms and approved documents.
When
Values age visibly: live, delayed, stale, no data. A frozen number never masquerades as a healthy one.

/03Device pairing & identity

Pairing modelled on the device authorisation grant (RFC 8628).

Glasses have no keyboard, so they never handle a password. The QR code carries no reusable credential; challenges are single-use, expire after five minutes and are rate-limited against guessing.

  1. 01

    Glasses request a challenge

    The device asks for a pairing challenge and receives a short user code plus a separate device secret that is never displayed.

  2. 02

    QR + 8-character code

    The viewport shows XXXX-XXXX and a QR link. The alphabet avoids look-alike characters (no 0/O, 1/I/L).

  3. 03

    An authorised person approves

    Signed in to the console on another device, they confirm the code and assign the glasses to an operator and sites.

  4. 04

    Device claims its credential

    The glasses poll (no faster than every 3 s) and, once approved, exchange their secret for a short-lived device credential.

Lifecycle: unregistered → pending pairing → paired → assigned → connected / disconnected. Any device can be suspended or revoked from the console.

/04Offline-capable sync & realtime

Dead spots are part of the plant.

Degraded mode, stated plainly

When the network drops, the viewport says so and every value shows its age.

Local step queue

Inspection responses queue on the device and sync in order on reconnect.

Server-Sent Events

One long-lived HTTPS stream per client, with the token in a header — never in the URL.

Replay after reconnect

Last-Event-ID replay closes gaps; sessions are re-validated every 30 s so revoked devices are disconnected.

Safety & reliability

Advisory only. Hydris never actuates pumps, valves or dosing.

Advisory only

No write path to SCADA, PLCs or field devices. Hydris shows context and records observations; operators act through your existing controls and permits.

Tenant isolation

Every query runs in the caller’s organisation context, enforced in the database. Realtime events are authorised per connection.

Audit trail

Pairing approvals, device assignments, alarm actions, inspection reviews and permission changes are recorded with who and when.

Least privilege

Role- and site-scoped permissions. Devices get their own short-lived credentials and only see approved documents.

  • Session tokens

    Short-lived access tokens held in memory; refresh tokens are httpOnly, SameSite=Strict cookies and rotate on use.

  • Gateway keys

    Per-site gateway keys are stored as hashes and can be revoked instantly from the console.

  • Synthetic data separation

    Simulator data is only accepted in demo tenants and is labelled synthetic wherever it is shown.

  • Account provisioning

    Accounts are invited by an administrator; there is no self-registration into a customer tenant.

/05Integrations

What connects today, and what is planned.

Integration options and their availability
Edge gateway → HTTPS ingestionJSON batches (≤ 500 readings) with a per-site API key; per-item accept / reject results; idempotent by message ID. Available now
Manual & laboratory entryField and lab results entered in the console with source and timestamp provenance. Available now
Realtime stream (SSE)Server-Sent Events to console and glasses, authorised per connection, Last-Event-ID replay. Available now
History exportPer-sensor history and CSV export for reporting and regulator submissions. Available now
MQTT adapterEdge adapter subscribing to existing broker topics and forwarding to ingestion. Planned
OPC UA adapterEdge adapter reading tags from OPC UA servers. Planned
Native glasses adapterDevice packaging for Meta Ray-Ban Display class glasses; today the viewport runs in a browser. Planned

/06Future: computer vision & more

Computer vision is planned — and labelled that way.

We are exploring gauge reading and visual anomaly prompts from the glasses camera. Any such feature will suggest, never decide: the operator confirms what is recorded. None of it is available today.

Available now

In this release
  • Glasses viewport (web) + browser simulator
  • Live asset context with data freshness
  • Guided inspections, rounds & maintenance checklists
  • Alarm rules with deadband and on-delay
  • Approved SOPs for operators and devices
  • QR + short-code device pairing, fleet management
  • HTTPS edge-gateway ingestion, manual & lab entry
  • Realtime (SSE), audit trail, CSV export

Planned

Not yet available
  • Computer vision
    Gauge reading and visual anomaly prompts from the glasses camera — always confirmed by the operator.
  • Voice
    Hands-free notes and navigation for gloved, wet work.
  • Predictive maintenance
    Early warnings from vibration, motor current and runtime trends.
  • MQTT & OPC UA adapters
    Edge adapters so existing brokers and servers can feed Hydris without custom code.
  • Native device adapter
    Packaging the viewport for Meta Ray-Ban Display class glasses with neural-band input.

Planned items describe direction, not committed delivery dates. We will tell you plainly what exists when you evaluate Hydris.

Talk to an engineer, not a script.

A 30-minute walkthrough: the glasses viewport, the operator console and how your gateway telemetry would reach both. We will be clear about what is available today and what is planned.