R&D & Tooling
Custom SDR tools, test benches and secure-development advice, built on the same stack as RF Swift so your team can keep using them after the project.
- You want the capability in-house, not a one-off report
- A repeatable test setup would pay for itself
- Your engineers will run it after the project
- You want the source code, not a black box
How it runs
We share progress at each milestone, and your engineers can use the tools before the handover.
Scoping
What your team needs to be able to do, and how they will run it after the project.
Build
Tools and test benches on the RF Swift stack, so the environment is reproducible and yours.
Handover
Hands-on sessions with your engineers, with the source code and documentation.
Support
A support period while your team takes over, agreed in advance.
Deliverables
Tools and a test bench your team can run and change, with the documentation and training to do it.
- Tools
- With source code and documentation, yours to run and change
- Test bench
- Built, documented and reproducible on the RF Swift stack
- Architecture guidance
- In writing, for decisions that outlast the project
- Handover sessions
- Hands-on, so the knowledge stays with your team
| Target | What that involves |
|---|---|
| 5G device test bench | Automated NR, NSA and SA security testing |
| Automotive RF test bench | V2X, TPMS and keyless entry validation |
| IoT protocol test bench | LoRa, BLE and Zigbee regression testing |
| Baseband fuzzing rig | Continuous security testing of modems |
| RFID and NFC test bench | Access-control validation |
| SDR tooling | Tools built for your protocols and workflow |
Frequently asked questions
Do we own the tools?
You get everything needed to run them on your own: the source code, the documentation and the build instructions, with the right to use, change and maintain them for your own needs, no licence fee and no lock-in. Your engineers can run it, change it and maintain it after we leave. We would rather leave you a capability you control than a black box that depends on us. If you need full ownership of what we develop specifically for you, for example to commercialise it, a transfer of rights can be agreed and priced in the proposal; Penthertz's own building blocks and generic techniques stay ours and are licensed to you on the same terms, and open-source components such as RF Swift keep their own licence. If you later want us to extend or support the tooling we can, but that is your choice, not a condition of using what we delivered.
Is it built on RF Swift?
Where it fits, yes. RF Swift is Penthertz's open-source framework for reproducible software-defined-radio environments, written by one of our own engineers, so building on it means your team gets a documented, repeatable setup instead of a fragile one-off that only works on one machine. It is not mandatory: if your project needs a different base, or must stay self-contained, we build it that way. The aim is tooling your engineers can rebuild from scratch and trust, long after the engagement ends.
Talk to us about your project
We scope the work in a first call, then send a fixed-price proposal. We can put a mutual NDA in place before discussing details.