SV·00

Your plant floor,
live on one board.

Supervictor puts every machine behind its own certificate and on a dashboard that moves with every reading: who is running, who is idle, who went dark — and what each one is drawing right now.

Fleet status — live preview

Machine	Current	Power	Last uplink	State
press brake	9.1 A	off	1s ago	fresh
extruder	43.2 A	on	3s ago	fresh
cnc mill	30.8 A	on	6s ago	fresh
compressor	17.2 A	on	2s ago	fresh
welder	1.5 A	off	11s ago	fresh
band saw	10.6 A	on	9s ago	fresh
oven	25.8 A	on	17s ago	fresh
conveyor	5.9 A	on	28s ago	fresh
injection molder	—	unknown	46m ago	stale
process pump	—	unknown	3h ago	dark

5 s

uplink period

1 cert

per machine, revocable

machine profiles to rehearse with

1 binary

on your own box, anywhere

SV·01

Deploy. Monitor. Sustain.

Deploy PROVISION & IDENTITY

One-command onboarding — issue the certificate, register the device, flash the firmware, verify the first handshake. One step, repeatable per unit.
Certificate authority built in — device, server, and operator credentials from a single managed root; browser bundles for your team included.
Runs where you run — one static binary on a $5/month VPS, a box on your own network, a Raspberry Pi or an EC2 instance, terminating mTLS itself. No cloud dependency, no lock-in decision on day one.
Rehearse without hardware — ten simulated machines (extruder, press brake, CNC mill, saw, oven, compressor, conveyor, molder, welder, pump) run as containers, each with its own certificate and a realistic working day, so the dashboard is proven before the first board is racked.

Monitor SEE EVERY UNIT

Live fleet dashboard — telemetry streams in as it happens; freshness badges triage the fleet at a glance. Pick a five-minute window and the charts re-render on every reading.
Power state per machine — each unit has its own current threshold, so on means producing for a press whose idle pump draws 9 A and powered for a sensor node. Power-over-time shows the whole plant's day.
Machine-readable health — the same fleet view, summary and history as JSON, for your alerting, your scripts, your ops tooling.
Dark-device watchdog — a device that goes quiet past its threshold is logged, flagged, and ready to page you.

Sustain KEEP IT RUNNING

Firmware accountability — every unit reports what it runs; version drift is visible the moment it exists.
Revoke and reactivate — device misbehaving or decommissioned? One click flips its status; its certificate stops working with it.
Audit trail — every operator action is logged with the operator's certificate identity. Who did what is never a mystery.

Put your fleet on the board.

Talk to us about running Supervictor for your devices.

Talk to us View the source

SV·02

Security spec

Built on standards	Mutual TLS 1.2/1.3 for every connection and X.509 public-key infrastructure for every identity — the same standards that secure banking and the modern web, applied device-to-cloud.
Best practices	No passwords or shared keys anywhere. Least-privilege access, per-device revocation, request throttling, and audit logging of every operator action, following OWASP-aligned web practices.
The short version	Each device and each operator carries its own revocable cryptographic identity, and nothing talks to anything without proving who it is. It just works — and keeps working when a credential is lost.

SV·03

Self-host it, anywhere

MACHINE  (ESP32-POE over PoE Ethernet, ESP32-C3 over WiFi, or a simulated machine)
   │
   └──mTLS──►  one static binary on your hardware ──► SQLite   self-hosted
                        │
                        ├── /ui            dashboard: fleet, device pages, live windows
                        ├── /ui/history    status + power over the day, every metric charted
                        ├── /fleet         health, summary, history as JSON
                        └── watchdog       dark-device alerting

The same product runs both ways: self-host on your own hardware for full control, or push to the cloud for enterprise scale — your budget and your needs decide, and you can change your mind later without changing your devices.

SV·04

Built as one piece

One language	Most connected-machine stacks are C on the board, a scripting language in the cloud, and a web framework on top, held together by contracts nobody checks. Supervictor is Rust from the microcontroller to the database: the message a machine sends is one definition compiled into both ends, so a change that would break the fleet fails to build instead of failing at 2 AM.
Nothing else to run	The service is a single program that handles its own encryption, its own identity checks, its own storage and its own dashboard. No proxy in front, no database server beside it, no runtime underneath. It installs on a plain Linux machine in one command, and upgrading is running that command again.
Boards that stay honest	Each board carries its own certificate, baked in when it is flashed, and reports the firmware it runs on every uplink. Wired PoE boards take power and network from one cable; WiFi boards are supported for places a cable cannot reach.
Rehearse the whole plant	Ten machine models — extruder, press brake, CNC mill, saw, oven, compressor, conveyor, injection molder, welder, pump — each run a realistic working day: heaters soaking, strokes and passes, breaks, shutdowns, the odd jam. Point them at your endpoint and the dashboard is proven before a single board is racked; swap one for a real machine and nothing about the dashboard changes.