About
Revyr Labs
We build clean systems for embedded engineers who care about determinism, speed, and clarity.
Mission
Revyr Labs exists to remove complexity from embedded software delivery. We believe engineers should spend time building reliable systems, not fighting repetitive workflow overhead, brittle test rigs, or vendor-imposed constraints.
Our work is grounded in production reality. Every product we ship is designed for teams that need stability under pressure—deterministic behavior, predictable performance, and tooling that stays out of the way.
We measure success by how little friction our users feel between an idea and a verified result on real hardware.
Vision
A world where embedded board workflows are as accessible and reproducible as software CI—self-hosted, scriptable, and free from vendor lock-in.
We see embedded engineering converging with modern DevOps practices: versioned test definitions, observable runs, signed artifacts, and audit-ready workflows. Revyr Labs is building the substrate for that convergence without forcing engineers off the tools they already trust.
Long term, we want self-hosted, deterministic board workflows to be the default—not the exception—for labs, indie hardware makers, and enterprise teams alike.
What we build
We build focused, self-hosted tooling for embedded hardware workflows. Our products are native to Linux and Windows, offline-capable, and designed to run on infrastructure you control.
Ferqon
A self-hosted hardware testing platform pairing an orchestration server, a web IDE, a hardware bridge, and a shared command set—so build, flash, test, and diagnostics happen from one place.
Shared command definitions
A single source of truth for device commands and board profiles, reused across the server, firmware, and UI so behavior stays consistent end to end.
Signed update channel
Ed25519-signed server and firmware update manifests, verified fail-closed before install, with a version store for rollback.
Observability surface
Prometheus metrics, system status endpoints, and audit logging built in—drop-in Grafana dashboards without external agents.
Why Ferqon exists
Embedded hardware workflows have historically meant expensive bench setups, proprietary tooling, and workflows that don't translate between teams or labs. The result is fragmented test rigs, manual handoffs, and results that are hard to reproduce or audit.
Ferqon exists to collapse that complexity into a single self-hosted platform. One orchestration server, one web UI, one shared command set, one hardware bridge—so the same job runs the same way on a developer laptop, a CI runner, or an air-gapped lab bench.
We built it because we lived the problem: shipping embedded systems at scale and needing cleaner operational tooling than what existed. Ferqon is the tool we wanted, made available to everyone who works with real hardware.
Commitment to security and reliability
Security and reliability are not features we add later—they are constraints we design against from the first commit. Ferqon runs on your infrastructure, and we treat that trust as a contract.
Self-hosted by default
Your data, devices, and test artifacts never leave your infrastructure. No phone-home telemetry, no mandatory cloud accounts.
Defense in depth
JWT auth, MFA with TOTP and recovery codes, CSRF protection, rate limiting, CSP headers, and role-based access control layered together.
Encrypted at rest
AES-256-GCM encryption for sensitive data at rest, with tamper-evident audit logging for every privileged action.
Sandboxed execution
AppArmor and seccomp profiles (default, plugin, strict) constrain what backend processes can do at the syscall level.
Signed artifacts
License tokens and update manifests are Ed25519-signed and verified fail-closed. Unsigned or tampered artifacts are rejected.
Resilient operations
Degraded and grace modes keep the server usable when upstream services are unavailable, with maintenance middleware that surfaces status to clients.
Offline-first
After activation, Ferqon runs without an internet connection. Air-gapped deployments ship via the enterprise runtime for restricted environments.
Observable by design
Prometheus metrics, system status endpoints, and diagnostics bundles give visibility into throughput, latency, and health without external agents.
Brand philosophy
Geometric minimalism with strong visual signal.
Sky blue accents used intentionally, not excessively.
Native to Linux and Windows, with offline-first product thinking.