Connect it.
Put it to work.

Connect your devices. See their data.
Control what happens next.

Bring gateways, embedded Linux systems, and microcontrollers into one workspace for telemetry, remote operations, and visual automation.

Request early access Explore the vision

+ DEVICES ↔ DATA ↔ EXECUTION

THE CONNECTIVE CORE SIGNAL / ACTIVE

FLEET OVERVIEWSAMPLE FLEET

128DEVICES

3CLUSTERS

126ONLINE

2PENDING

CLUSTERNODESSTATE

Sensor mesh96● Healthy

Edge compute24↑ OTA rollout

Field gateways8● Healthy

EDGE COMPUTE / AGGREGATE

CPU38%

RAM62%

STORAGE44%

↑ Firmware rollout 22 / 24 complete

Illustrative fleet telemetry

A WORLD OF HARDWAREMicrocontrollersEmbedded LinuxEdge gatewaysMicroPythonONE CONNECTIVE CORE

01 / THE PLATFORM VISION

Your devices.
Working together.

One place to see your fleet, work with its data, and send the next command.

Observe the fleet.

See which devices are online, what they’re using, and where load is changing. Go from fleet health to an individual signal.

TELEMETRY / FLEET INSIGHT

Execute the logic.

Connect events to decisions and actions. Shape a payload, check a threshold, or start a workflow. Follow each step.

VISUAL FLOWS / EXECUTION ENGINE

Control the edge.

Push configuration, send commands, and plan software rollouts. Keep the response attached to the device that produced it.

PROVISIONING / OTA UPDATES

ONE DEVICE. THE WHOLE LOOP.

From a reading
to a result.

Follow the same device through data, logic, a command, and its reported result. Choose a scenario to see where it fits.

Cool an equipment enclosure.GATEWAY-024 / ENCLOSURE-03

01 / DEVICEGateway online14:02:00
02 / DATATemperature 43.2 °C14:02:00
03 / LOGICAbove 40 °C for 30 s14:02:30
04 / COMMANDSet fan to 80%14:02:31
05 / RESULTACK · 38.7 °C14:04:00

Fan speed acknowledged at 14:02:32. A later reading shows temperature below the threshold.

Illustrative sequence · capabilities and timing are examples

START WITH YOUR HARDWARE

Three ways in.
One connected fleet.

Start with one device. Bring its data into view. Add control and automation when you need them.

Embedded Linux

A lightweight agent for gateways and embedded systems. Publish system health and application telemetry; receive configuration and commands.

AGENT CONNECTION / PRODUCT DIRECTION

⌘

Microcontrollers

A small client in your firmware. Send readings, expose supported controls, and bring MicroPython devices into the same workspace.

CLIENT CONNECTION / PRODUCT DIRECTION

⇄

Existing equipment

Use an edge gateway to translate field signals into device data. Keep the equipment you have and add a connected operational view.

GATEWAY CONNECTION / PRODUCT DIRECTION

A READING WITH CONTEXT

Give every value an identity.

A device, a timestamp, a measurement, and a unit. The same identity follows the reading into its history, flow, and command response.

Illustrative message shape—not a published API or install command. Connection tooling and authentication are being defined for early access.

{
  "device_id": "gateway-024",
  "site": "west / enclosure-03",
  "timestamp": "2026-09-19T14:02:00Z",
  "temperature": { "value": 43.2, "unit": "°C" }
}

02 / SIGNALS BECOME BEHAVIOR

Make the connection.
Build the behavior.

Start with a device event. Add your logic. Send an action back. Explore how a flow turns connected hardware into a working system.

A signal becomes a response.

Watch a temperature reading trigger a command, then bring the device acknowledgment back into the flow.

REVO.IO / FLOW CANVAS

⌁✓

MQTT eventtemperature: 43.2 °C

⋔✓

Check thresholdabove 40 °C

↗✓

Set fan speeddesired: 80%

✓✓

Confirm statereported: 80%

X: 0240 / Y: 0160 4 NODES · 3 CONNECTIONS

NODE DETAILS

Threshold condition

INPUTtemperature: 43.2 °CEXPRESSIONtemperature > 40OUTPUTtrue → fan.set_speed(80%)Inspect the data at each step.

EXECUTIONReady to run the example.LOCAL PREVIEW

Raw readings. Useful information.

Normalize a measurement, calculate a rolling average, and store a signal your dashboards and flows can use.

REVO.IO / FLOW CANVAS

⌁✓

Device sampletemperature: 298.15 K

ƒ✓

Normalize unitsKelvin → Celsius

∿✓

Window average60-second window

▥✓

Record metrictemperature: 24.8 °C

X: 0240 / Y: 0160 4 NODES · 3 CONNECTIONS

NODE DETAILS

Normalize units

INPUTtemperature: 298.15 KEXPRESSIONcelsius = kelvin − 273.15OUTPUTtemperature: 25.0 °CInspect the data at each step.

EXECUTIONReady to run the example.LOCAL PREVIEW

Roll out in steps. Check the result.

Select a device group, start with a small batch, and use its reported health to decide whether the rollout continues.

REVO.IO / FLOW CANVAS

▦✓

Select clusteredge-compute / 24

↑✓

Deploy canary2 devices / v0.9.4

♡✓

Check health2 / 2 reporting

↗✓

Continue rolloutremaining 22 devices

X: 0240 / Y: 0160 4 NODES · 3 CONNECTIONS

NODE DETAILS

Canary health gate

INPUT2 devices · version 0.9.4EXPRESSIONboth healthy AND version matchesOUTPUTcontinue → remaining 22Inspect the data at each step.

EXECUTIONReady to run the example.LOCAL PREVIEW

See the path.

Triggers, branches, and actions in one readable flow.

Inspect the data.

Keep inputs, expressions, and results close to the logic.

Follow the outcome.

Connect the command to its acknowledgment and reported state.

LIGHTWEIGHT AT THE EDGE.

A small payload connects embedded Linux systems and edge gateways. Lightweight clients extend the same model to microcontrollers, with MicroPython script deployment and remote updates in the vision.

THE PRODUCT DIRECTION

From first connection
to the next update.

The daily work of running connected hardware, brought into one workspace.

DEVICE IDENTITY

01Connect→02Identify→03Group

fleet / west / gateway-024

Give every device a place.

A lightweight client, a persistent identity, and a group to belong to. Bring microcontrollers, Linux systems, and gateways into the same fleet.

ENROLLMENT / INVENTORY

DESIRED → REPORTED

sample_interval30 s ✓

telemetry_enabledtrue ✓

revision 12 / synchronized

Set intent. Track reality.

Change configuration for a device or a group. Keep the desired value, the reported value, and the acknowledgment in view.

CONFIGURATION / DIGITAL TWIN

MICROPYTHON / RELEASE

main.pyv0.9.4

STAGED ROLLOUT

package → deploy → verify

Keep the edge current.

Plan software and MicroPython updates across your fleet. Stage delivery, inspect version reports, and follow device health.

SOFTWARE / OTA UPDATES

Interface concepts show the intended workflow. Request early access to explore your use case.

03 / A DIGITAL TWIN THAT STAYS WITH YOU

Connection lost.
State retained.

Keep reported state, desired configuration, and pending commands attached to the device. Its digital twin persists beyond a network session.

For intermittent links, the vision includes queued commands with explicit delivery and acknowledgment. Reconnection should resume the conversation, not erase its context.

Desired is not delivered. Delivered is not acknowledged. The state should tell you which.

DIGITAL TWIN / FIELD-03TRY THE CONCEPT

Field gateway

Remote monitoring station

● Offline

LAST REPORTED INTERVAL60 seconds

DESIRED INTERVAL60 seconds

A connection can wait. Your intent stays.

Try queuing a new reporting interval for this example device.

Illustrative workflow. No real device is connected.

KNOW WHAT NEEDS ATTENTION

Find the problem.
Know the next move.

A fleet view should help you act. Keep missing data, resource pressure, and rollout health attached to the right device.

EXAMPLE INVESTIGATION

Check the last known state.

Last contact was 12 minutes ago. The last reported battery level was 18%; newer readings are unknown.

Evidence: Last seen 14:18 · expected every 60 s
Next step: Inspect battery and gateway connectivity before sending a command.

Select an issue to preview its context and next step.

04 / FROM TELEMETRY TO CONTEXT

Find the pattern.
Act on it.

Spot a growing load before it becomes a problem. Compare clusters, trace a change, and see whether your devices return to target. Turn fleet telemetry into decisions.

CLUSTER PERFORMANCE30 MIN / EXAMPLE DATA

MEAN CPU42%

SPREAD±2pts

RX + TX8.0Mb/s

CPU LOAD THREE COMPUTE GROUPS / %

NETWORK TRAFFIC VOLUME + MOVING AVERAGE

↘ Load converges after configuration. Traffic stays within range.

CLOUD CONTEXT. EDGE RESPONSIBILITY.

Know where
the work happens.

Remote supervision and local machine behavior have different jobs. The architecture must make that boundary clear.

01 / EQUIPMENT

Devices & controllers

Sense, actuate, and report. Local controllers retain machine interlocks and time-critical control.

⇄FIELD DATA

02 / EDGE

Gateway / client

Connect equipment, translate signals, and return device responses. Buffering and offline execution need explicit policies.

⇄TELEMETRY / COMMANDS

03 / PLATFORM

REVO.IO

The intended home for fleet context, telemetry history, desired state, visual workflows, and command tracking.

When the connection drops

Keep last-known state visible with its timestamp. Eligible commands need expiry and acknowledgment rules. Gateway buffering and local flow execution are design decisions—not current guarantees.

Connect to existing systems

MQTT is part of the planned connection model. Modbus, OPC UA, and BACnet are integration candidates to discuss with early-access users; adapters are not yet available.

Connection and deployment status

Area	Current direction
Linux agent / microcontroller client	Planned; no public SDK or quickstart yet
MQTT / device authentication	Protocol model and credential lifecycle to be finalized
Modbus / OPC UA / BACnet	Integration candidates; support not committed
Cloud / edge execution	Placement, offline behavior, and hosting options to be decided
Historical data / exports / API	Planned product areas; retention and interfaces to be defined

FROM FIRST CONNECTION TO WHAT’S NEXT

One place for the life of your device.

01Provision
02Observe
03Interact
04Update
05Evolve

REQUEST EARLY ACCESS

Bring a device.
Bring a use case.

Help shape the connection. Tell us what you run, what you want to measure, and what you need to control.

Describe your project.
Copy your brief into the Revotics contact form.
Send it to start an early-access conversation.

This prepares a brief locally. Nothing is sent until you submit the contact form. Access timing, compatibility, and pricing will be discussed for your use case.

Connect it.Put it to work.

Your devices.Working together.

Observe the fleet.

Execute the logic.

Control the edge.

From a readingto a result.

Three ways in.One connected fleet.

Embedded Linux

Microcontrollers

Existing equipment

Give every value an identity.

Make the connection.Build the behavior.

A signal becomes a response.

Raw readings. Useful information.

Roll out in steps. Check the result.

See the path.

Inspect the data.

Follow the outcome.

From first connectionto the next update.

Give every device a place.

Set intent. Track reality.

Keep the edge current.

Connection lost.State retained.

Field gateway

Find the problem.Know the next move.

Check the last known state.

Find the pattern.Act on it.

Know wherethe work happens.

Devices & controllers

Gateway / client

REVO.IO

When the connection drops

Connect to existing systems

One place for the life of your device.

Bring a device.Bring a use case.

Connect it.
Put it to work.

Your devices.
Working together.

From a reading
to a result.

Three ways in.
One connected fleet.

Make the connection.
Build the behavior.

From first connection
to the next update.

Connection lost.
State retained.

Find the problem.
Know the next move.

Find the pattern.
Act on it.

Know where
the work happens.

Bring a device.
Bring a use case.