The flagship tool

The workbench
that reads the link.

Emrysia isn't just the studio name — it's a real, offline-first RF workbench I built and run on live work. When you hire the studio, this is the engine your deliverable comes out of. It's the proof of competence and the reason the report is more than an opinion.

Have me run it on your problem Why I built it

4M/s

Link calcs — stress-verified

100% offline

No cloud, no bundled key

2 regions

FCC & ETSI legality built in

1 export

PDF · code · diff · BOM

See it work

Real captures — not mockups.

The same workbench your deliverable comes out of. Watch it take a failing 2.4 GHz link and, in one move, foretell the rig that fixes it.

Animated walkthrough: Emrysia takes a failing 2.4 GHz link (red, NO LINK, −15 dB), then after Corvus optimizes the rig the field turns green with +7 dB margin and ~84 m reach. — **Live capture, looping.** A dead link becomes a working one — the field goes red → green as Corvus foretells the fix (antenna, PHY, power).

Emrysia showing a failing link: margin −15.4 dB, NO LINK, the RF field glowing red around the node. — **−15.4 dB · NO LINK.** The field turns red where the budget dies. The problem finally has a picture.

Emrysia after optimizing: Corvus recommends antenna → dipole, LoRa SF12, TX 8 dBm for +7 dB margin and ~84 m reach; the field goes green. — **+7 dB · ~84 m.** Corvus: antenna → dipole, LoRa SF12, TX 8 dBm — the cheapest legal path to a working link.

Under the hood

Physics, not vibes.

Every capability exists to put a number where there used to be a shrug.

Link budgets

Corrected multi-band Friis + log-distance path loss — no negative-path-loss unit bugs. Coverage rings and per-link margin in plain dB.

Terrain-aware

ITU-R P.526 single knife-edge diffraction along the real profile, plus a 3D view and a link cross-section. Hills break links here like they do in the field.

Regulation-aware

FCC / ETSI band legality, EIRP caps and duty-cycle limits, checked live — so the fix is legal where you actually deploy it.

Whole-mesh view

Multi-node networks with comms-drop tracing. Faulted nodes glow red; click one and Corvus gives the verdict — cause first, then fix.

Firmware in, fixed out

Paste Arduino / ESP-IDF / RPi / STM code. Wrong lines flagged red, corrections green, download the working firmware with a diff.

Corvus, the familiar

A blunt, dry assistant that reads the omens aloud. Runs on-device by default — no cloud dependency, no API key ever bundled in the app.

The workbench

A single field, and everything floats over it.

The sim canvas is the whole screen; every control is a draggable panel you summon and dismiss — Radio, Link, Device, Node, Network, Terrain, Spectrum, Corvus, Code. Minimal chrome, maximum field. Built for a phone in your hand at the base of a tower.

✓Field-first UX. Draggable, collapsible panels + a summon FAB. It works on a laptop and on an Android phone in the field.
✓Device library by brand. Nordic, Espressif, Raspberry Pi, Arduino, STMicro, Semtech, TI — brand → model in two taps.
✓Scenarios & projects. Save a deployment, compare rigs, and re-open a client's network later.

Emrysia running on a phone in the field: band and PHY pickers (433/868/915 MHz, 2.4/5.8 GHz, BLE, Wi-Fi, LoRa), device orbit view, and the RF field — floating panels stacked for a narrow screen.

Real capture — the same workbench on a phone, offline, at the base of a tower.

The deliverable

Every run can become a client package.

The differentiator isn't the model on my screen — it's what you can hand to a client or a manufacturer at the end.

.pdf

Report

The reveal in plain language + the numbers behind it. Written to be read by a client, not just an RF engineer.

.diff

Corrected code

Your firmware, rewritten toward the fix, with a clean diff so every change is visible and reviewable.

.csv

BOM

Real, sourced parts — MCU, radio, antenna, matching — ready to drop into a quote or a fab order.

.json

Config

Per-node settings that make the model reproducible: bands, power, timing, placement.

The instrument behind the work

You don't buy the tool — you get what it sees.

Emrysia is the workbench I build on and run on live jobs. Hire the studio and you get its output on your deployment: the reveal, the fix, and the package to build from.

Have me run it on your problem See it on real problems

The workbenchthat reads the link.