Skip to content
REVYR LABS

Product

Early Access · Beta

FerqonSelf-hosted hardware testing

A self-hosted lab for your dev boards. Flash, test, debug, and run CI against real hardware from any browser. Free for 1 user and 1 active server. No cloud required.

No third-party cloudNo vendor lock-inNo recurring fees
ferqon@lab-gateway — bash
ferqon@lab-gateway:~$ ferqon device scan
✓ Device scan completed
Found 3 devices
PORTBOARDSTATUS
/dev/ttyUSB0ESP32-DevKitCready
/dev/ttyACM0Arduino Zeroready
/dev/ttyACM1RPi Pico Wbusy
ferqon@lab-gateway:~$ ferqon flash build/firmware.bin --device /dev/ttyUSB0 --family esp32 --board ESP32-DevKitC
Uploading firmware: build/firmware.bin
✓ Firmware uploaded: fw_a1b2c3d4
✓ Flash job started: job_7e8f9a0b
✓ Flash completed successfully!
ferqon@lab-gateway:~$ ferqon test run
[build] OK 2.1s
[flash] OK 4.3s
[test] PASS 6 of 6 0 skipped 0 failed
ferqon@lab-gateway:~$

The problem

Your boards are everywhere but your tools are nowhere

Most embedded workflows live on whichever laptop has the right USB cable. As boards and projects multiply, that breaks down.

Boards scattered across drawers and shelves

You own half a dozen dev boards and can't remember which port each one is on, let alone which firmware is loaded.

Manual, repetitive flows

Flashing a board, running a test, and capturing results is done by hand each time, with no reproducible pipeline.

Fragmented tooling

Device detection, flashing, test execution, and logging live in unrelated tools that don't share state.

No shared source of truth

Command definitions and test expectations drift between the host and the device under test.

Your lab is stuck in one room

When you leave the house, the hardware stays behind. Testing something overnight means a laptop is tethered to a desk.

Ferqon turns your boards into a self-hosted lab with a shared command set, a visual test builder, and an API — so the same job runs the same way from your desk, your couch, or your CI runner.

Why Ferqon

Built for teams that work with real hardware

Three reasons teams move from manual rigs and cloud tools to a self-hosted Ferqon pipeline.

Test on real hardware, not a simulator

Ferqon runs against the actual board with the actual firmware. You are not relying on synthetic signals or mocked peripherals.

One pipeline for every board

A single YAML file defines build, flash, and test stages. The same file drives every device in the lab.

Own the product, not a subscription

Pay once and run it where you want. Air-gapped deployments and offline activation keep your data on your network.

Who it's for

Who it's for

Developers and small teams that want control over their own hardware.

Firmware & embedded developers

Engineers running real-hardware tests before a release, or just tired of walking to the lab.

Small labs & startups

Teams that need board testing capability without standing up a cloud-managed platform.

Homelabbers & makers

People with a shelf of dev boards who want a dashboard, a history, and remote access without a cloud account.

Remote device management

Anyone who needs to inspect and drive hardware over the network from a browser.

MCP — AI assistant access (coming soon)

Teams that want a Model Context Protocol endpoint so AI agents can inspect serial logs and triage failures. Read-only by default with explicit write grants.

How it works

From code to hardware in five deterministic steps

A Ferqon pipeline moves through five reproducible stages.

01

Define your pipeline

Build, flash, and test stages are declared in a single version-controlled file, so the pipeline is reproducible and reviewable like any other code.

02

Connect hardware

Plug in a board; Ferqon auto-detects the device, port, and firmware target using its board-profile catalog.

03

Run and test

Execute the pipeline with a single command. Tests run automatically after each flash, against the real device.

04

Review results

Inspect structured logs, test reports, and artifacts in the terminal or the web dashboard.

05

Ship with confidence

Promote only validated firmware builds to production, with deterministic, auditable deployments behind them.

Key features

What you get out of the box

Detect, flash, test, and debug your boards — self-hosted.

Your board shelf, organized

Device auto-detection & port scanning

Firmware flashing (35+ board profiles)

Visual test builder

Device testing & live test console

Serial monitor

Team mode, when you need it

Self-hosted deployment

Security & reliability model

Defense in depth, degraded modes, grace windows, and audit trails.

Supported platforms

Runs where you run

Linux and Windows, browser-driven, and air-gapped capable.

Backend

  • Linux (Docker Compose — recommended)
  • Windows native binaries
  • Bare-metal / systemd or Windows service
  • Raspberry Pi as lab gateway
  • Air-gapped / offline activation

Frontend

  • Any modern web browser
  • SvelteKit single-page app

Supported devices

  • ESP32 / ESP8266
  • STM32
  • Arduino
  • RP2040 / Raspberry Pi Pico / Pico W
  • nRF52
  • Teensy
  • Adafruit Feather
  • 35+ profiles total + open-source firmware SDK for custom boards

One-time purchase, own the product

No subscriptions. 1 user and 1 active server are free, with paid tiers from $290.00 (beta pricing — was $399.00).

Roadmap

Beta roadmap

High-level themes under active development. Join the early access program to influence prioritization.

MCP server integration

Q3 2026

Built-in Model Context Protocol server so AI agents can inspect logs, run diagnostics, and triage test failures on your Ferqon lab. Read-only by design — no destructive operations exposed.

Expanded device connectivity

Q3 2026

CAN bus, SPI, and UART protocol support alongside the existing I2C implementation. New board profiles for Nordic nRF54 and Espressif ESP32-C6.

Advanced monitoring & insights

Q4 2026

Real-time test metrics dashboard with historical trends, failure-rate heatmaps per board, and alerts on regression thresholds.

Share: