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.
R&D as a service means our team owns the research and the engineering of your system. We write each unknown as a question with an acceptance plan, test it in our own hardware lab or in code, and build on the options that pass. Work runs in two-week sprints with acceptance criteria you sign, and the results, code and documents are yours.
| Fields | Signals · Embedded · Cryptography · Blockchain |
|---|---|
| Start | a feasibility study or a call |
| Process | two-week sprints, acceptance criteria you sign |
| Price | Fixed price per written scope |
| You own | results, code, documents |
Fit
Use it when you
Skip it when
You already know what to build and need engineers on your roadmap: see Dedicated engineers.
Fields
F01
Which radio gives the accuracy your product needs, and how each unit behaves. Wi-Fi FTM/RTT, Wi-Fi CSI, UWB, BLE, LTE and mmWave radar, each tested against a written acceptance plan; pose and activity models trained on mmWave point clouds.
Signals and sensing →F02
Rust firmware for ESP32-C6 with live tuning, per-device calibration and over-the-air updates; GPU image processing for instruments.
Embedded and firmware →F03
Signed multi-party proofs with witness quorums, Ed25519 on every message, zero-knowledge proof systems, and a threat model written before the code.
Zero-knowledge proofs →F04
Chain choice across candidates, private proof-of-stake networks, token design with staking, slashing and reputation, and a deterministic reward engine.
Blockchain engineering →How it runs
Formats
S01
One fixed question, answered in writing: go, change or stop, with the options tested and the risks.
Feasibility study →S02
A working prototype that proves the one thing your product depends on, measured against the acceptance plan.
Proof of concept →S03
Our team runs research and engineering in two-week sprints until the system works end to end.
Proof
FAQ
R&D as a service means our team owns the research and the engineering of your system. We write each unknown as a question with an acceptance plan, test it in our own hardware lab or in code, and build on the options that pass. Work runs in two-week sprints with acceptance criteria you sign, and the results, code and documents are yours.
A written answer to one question: go, change or stop. It lists the options we tested, the result of each against the acceptance plan, and the risks.
Then the study did its job before you paid for a build. You keep the evidence and the options that remain.
You do. Results, code and documents go to your repositories.
No. We publish nothing from client research, and we name a client only where the client agreed.
Yes. We test radios and sensors in our own hardware lab, each against a written acceptance plan.
Dedicated engineers join a roadmap you already have. R&D starts earlier, when it is not yet clear what can be built or how.
Studies and prototypes have a fixed price per written scope. Ongoing R&D is paid on accepted milestones.
Related
One fixed question, answered in writing: go, change or stop.
FormatA working prototype that proves the one thing your product depends on.
FormatEngineers who join a roadmap you already have.
OfferFTM, CSI and IEEE 802.11bf: what they can and cannot do.
Guide802.15.4z, Bluetooth Channel Sounding, RSSI and Wi-Fi RTT compared.
GuideNext step
A 30 minute call with Mykhailo. You leave with a clear view of scope, risks and next step.
Mykhailo Tiutin
CTO, Vareger
