TechnologyEmbedded and firmware

    Embedded and firmware: Rust on the device, signed data to the back end

    Short answer

    We write firmware and the software around hardware: Rust firmware for ESP32-C6 with radio ranging and live tuning, research in our own hardware lab across Wi-Fi RTT, UWB, BLE, LTE, mmWave radar and Wi-Fi CSI, signed device messages and over-the-air updates, field apps that control machines over their own Wi-Fi, and GPU image processing for super-resolution microscopes.

    At a glance
    FirmwareRust 2024 · ESP32-C6 · no unsafe in shared crates
    RadiosWi-Fi FTM/RTT · UWB · BLE · LTE · mmWave · CSI
    SecurityEd25519 · threat model first · SBOM
    InstrumentsC++ · CUDA · camera and stage control

    How a project runs

    Embedded and firmware: from question to running system

    Your pathEach step ends in a written result
    1. 01Acceptance planwhat the device must prove · how it is measured
    2. 02Lab testsradios and sensors · against the plan
    3. 03FirmwareRust · OTA and calibration
    4. 04Securitythreat model · signing and SBOM
    5. 05Field and back endapps and telemetry · ledger or server

    What we build

    Rust firmwareFirmware in Rust for ESP32-C6 with a seven-step Wi-Fi FTM accuracy pipeline, live tuning over MQTT, per-device calibration and over-the-air updates.
    Radio and sensing researchOur own hardware lab tests Wi-Fi RTT, UWB, BLE, LTE, mmWave radar and Wi-Fi CSI, each against a written acceptance plan; pose and activity models trained on mmWave point clouds.
    Device securityEd25519 on every message, signed multi-party proofs with witness quorums, a threat model before code (relay, Sybil, replay, clock skew), cargo-audit, cargo-deny and SBOMs, ready for the Cyber Resilience Act.
    Hardware assembly and control appsWe assembled a liquid fertiliser sprayer around the client's controller and built the Android app that runs it in the field over the machine's own Wi-Fi: live telemetry, automatic, test and manual modes, and console commands to the controller.
    Instrument softwareContinuous scanning with the camera shooting on the move, multithreaded GPU image processing in C++ and CUDA, and support for a new light source, focusing system, stage controller and confocal imager.
    Device to ledgerSigned evidence from devices through verifiers and a witness quorum to a blockchain record, so nobody can fake where a device was.

    Stack

    Technologies we use

    Firmware
    Rust 2024 on ESP32-C6, MQTT, over-the-air updates, per-device calibration
    Radios and sensors
    Wi-Fi FTM/RTT, Wi-Fi CSI, UWB, BLE, LTE, mmWave radar, phone signal harvesting
    Security
    Ed25519 signing, threat modelling, cargo-audit, cargo-deny, SBOMs
    Instruments and vision
    C++, CUDA on GPU, ML defect analysis, camera, stage and autoloader control
    Apps around hardware
    Android and Ionic over local Wi-Fi and TCP/IP, native iOS and Android

    Proof

    Delivered work

    All work
    Case · Devices · Europe

    Devices that prove where they are

    Problem
    Signed proof of physical presence that nobody can fake.
    Built
    Rust firmware on ESP32-C6, radio lab research, signed proofs.
    RustESP32-C6Embedded firmwareWi-Fi FTM
    Firmware to chain, signed off sprint by sprint.
    Case · AgTech · Europe

    Fertiliser sprayer, from hardware to field app

    Problem
    Operators had to run a sprayer from a tablet, offline.
    Built
    We assembled the sprayer and built its Android control app.
    Hardware assemblySprayerAndroidIonic
    A working sprayer, run from a tablet next to the machine.
    Case · Instruments · Europe

    Faster imaging for a microscope maker

    Problem
    Faster cameras outpaced the scanning and image pipeline.
    Built
    Scanning on the move, multithreaded processing, CUDA.
    C++CUDAGPUMachine learning
    Faster super-resolution imaging at the same optical quality.
    Case · Location proof · Global

    Proof of location, built on sensor fusion

    Problem
    Prove where a device is without trusting the device.
    Built
    Signal-harvesting mobile apps, token contracts, Java back end.
    Proof of locationSensor fusionEthereumEOS
    MVP and token contracts that reward confirming nodes.

    FAQ

    Questions buyers ask

    Q01Why Rust for firmware?

    Memory safety without a garbage collector, a strong type system for protocol code, and tooling (cargo-audit, cargo-deny, SBOM generation) that makes security reviews and Cyber Resilience Act evidence easier.

    Q02Do you have hardware in-house?

    Yes. We test radios and sensors in our own hardware lab, each against a written acceptance plan, before the design goes into firmware.

    Q03Can you work with our existing controller or board?

    Yes. We have built apps and services against existing controllers, for example a fertiliser sprayer we assembled and the field app that drives it over the machine's own Wi-Fi.

    Q04What about the back end?

    We build the whole line: firmware, the services that verify and store device data, and where needed a ledger that keeps the record.

    Next step

    Working on embedded and firmware?

    A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.

    Mykhailo Tiutin

    CTO, Vareger

    Mykhailo Tiutin, CTO, Vareger