Industrial Grade • SBOM & SLSA • Built with Go 1.25.5

Industrial IoT
Reimagined

Separate definition from execution. Develop in Low-Code, execute in C++20.
From Edge to Cloud, without sacrificing performance.

Start Building View on GitHub
< 10ms
Latency
500KB
Runtime Size
100%
Offline-First

Built for the Edge. Orchestrated from the Cloud.

The platform that combines Web agility with metal performance.

Visual Flow Designer

Design complex industrial logic without writing code. VDL (Veex Definition Language) translates your intent into optimized binaries.

✓ Node-Based Logic
✓ Hot Reloading
✓ Native Simulation
✓ Code Generation
React • Low-Code • YAML

C++20 Runtime

Deterministic execution engine. No interpreters, no overhead. Just raw performance on ESP32/M5Stack.

C++20 • ESP-IDF • RTOS

Secure OTA Updates

Update logic in milliseconds without reboot. Ed25519 signature verification ensures integrity on metal.

> Checking Update...
> Verifying Signature...
> Applying Atomic Swap...
Ed25519 • Atomic Swap

Native Drivers

CAN Bus, Modbus RTU, MQTT. Native stable drivers.

TWAI • Modbus • MQTT

Cloud Registry & Gateway

Artifact hub with Virtual Hosting. Port 80 access for Registry, Studio, and Fleet Orchestration via dedicated subdomains.

Go • Nginx • SQLite

Developer CLI

Simulate, compile, and flash in seconds.

Go 1.25.5

Industrial Compliance

Built-in SBOM and SLSA provenance artifacts.

SBOM • SLSA

End-to-End Architecture

Radical separation between definition and execution.

Cloud Side (The Brain)
VEEX Studio
VEEX Builder
VEEX Registry
.vex artifact (signed)
Edge Side (The Muscle)
VEEX Runtime
Native Drivers
Hardware
Declarative

Describe behavior, not implementation

Deterministic

Same input → same output, always

Offline-First

Edge works without Cloud connection

The New Industrial Paradigm

Bridge the IT/OT divide with a skills-first approach.

From Requirements to Intent

Automation experts no longer write "wish lists" for developers. They use VEEX Studio to design logic directly, shifting focus from C++ syntax to process results.

From Patching to Platforming

Firmware engineers are freed from minor logic tweaks. Instead, they build robust drivers and secure ABIs—high-performance building blocks for the entire company.

From Cables to Campaigns

Maintenance moves from manual serial updates to remote fleet orchestration. Manage hardware lifecycles with the same agility as cloud software.

Fearless Innovation

The isolated runtime sandbox removes the risk of "bricking" machines. Experiment and optimize on the fly, knowing the system core is protected by design.

Eliminating the translation layer between OT and IT. 🍻📟⚙️🦾

From Design to Deploy in Minutes

Create complex industrial flows with the simplicity of YAML. VEEX compiles to optimized binaries and signs with Ed25519.

1
Design Create flows in Studio or write VDL
2
Build & Sign Compile and sign with Ed25519
3
Deploy Flash directly or OTA via Registry
bash terminal 
# Simulate locally
veex sim my-flow.vdl

# Compile and sign
veex build my-flow.vdl
veex-signer sign my-flow.vex

# Flash to hardware
veex flash my-flow.vex.signed

# Or publish to Registry
veex publish my-flow.vex.signed

Artifact published to registry
239: OTA update available for fleet

Frequently Asked Questions

Everything you need to know about the VEEX Ecosystem.

Why C++20 for the Runtime?
Industrial environments demand determinism and zero-latency. By compiling VDL to C++20, we provide the performance of manual coding with the agility of low-code. It allows the Runtime to run on constrained hardware (ESP32) with a footprint under 500KB.
Does it require a constant cloud connection?
No. VEEX is 100% Offline-First. Once the industrial logic (VEX) is flashed or downloaded via OTA, the edge device executes it locally with zero dependency on the platform or internet.
How does VEEX bridge the IT/OT skill shift?
VEEX eliminates the translation layer. OT experts use Studio to define *intent* without worrying about C++ pointers, while IT/Firmware experts build the *capabilities* (drivers/ABI) that the rest of the team uses as building blocks.
How secure are the OTA updates?
Every artifact is signed with Ed25519 digital signatures. The Runtime verifies these signatures on-device before performing an Atomic Binary Swap, ensuring that only authorized, untampered logic is ever executed.
Which hardware is currently supported?
VEEX is optimized for the ESP32 ecosystem, with native support for M5Stack Core2, AWS EduKit, and generic ESP32-S3/C3 modules. We also support Linux-based edge devices (Raspberry Pi) via our portable C++20 Runtime.
Can I integrate VEEX with legacy PLCs?
Yes. VEEX includes stable native drivers for Modbus RTU/TCP and CAN Bus (TWAI). You can bridge logic between legacy sensors and modern cloud protocols (MQTT/gRPC) in minutes.
Is it possible to monitor device health in real-time?
Absolutely. The VEEX Platform includes an Observability Hub that ingests logs, vitals, and custom telemetry from the Runtime heartbeat, providing a live dashboard of your entire industrial fleet.
What is the licensing model?
The core VEEX ecosystem (Runtime, CLI, Build, and Registry) is open-source under the MIT License. We believe in industrial transparency and community-driven reliability.

Ready to Revolutionize Your Industrial Automation?

Open source. Production ready. Built by engineers, for engineers.

Read the Docs Star on GitHub