About us
The Vision
Engineering tools that share one model of the product — so code, board, and enclosure stop meeting at a file export.
Florian Römer
Founder · Dipl.-Ing. (FH)
Founded by an engineer, for engineers.
RMR Dynamics was founded by Florian Römer, an electrical engineer from Dresden with a background spanning embedded systems, PCB design, and mechanical prototyping. The tools here exist because the workflow they replace was the one being lived every day: a board in one application, an enclosure in another, firmware in a text editor, and a spreadsheet holding the three together.
That is not a hypothetical problem. It is the reason this company exists.
A small team, working across everything
We are deliberately small, and we cover an unusually wide range. There are no separate departments for software, electronics, and mechanical design here — the same team works across all three, which is precisely why the tools can share a model instead of merely sharing a file format.
RMR Dynamics is built AI-native. The work of building, testing, and iterating is carried out by our own agent team, working directly against our codebase and our designs. Every decision that matters is reviewed and directed by an engineer — the judgement stays with a person, the throughput does not.
This is the same bet the products make. If an engineering workflow can be driven by conversation, then the company building that workflow should be run that way too. We would rather prove it on ourselves first.
What we build
Three disciplines, each with its own tool, all built around one shared model of the product.
Software Development
Four tools over one session — a terminal agent, a desktop app, an editor, and a phone client that follows you out of the office.
Electronic Design
Schematic, layout, routing, and a 3D view of the board, driven by conversation as much as by mouse.
Mechanical Design
The enclosure around the board, modelled against the real components rather than a dimension copied across by hand.
Where we are going
One model, not three files
Finish the shared product model so a change in one discipline is visible in the others immediately, instead of at an export.
Every tool AI-operable
Each tool is designed to be driven by conversation as well as by hand, and the same way across all three disciplines.
Brief to buildable design
The long-term goal: a product taken from an idea to a design you can build from, with an engineer reviewing decisions rather than performing every step.
Build it with us
We are early, and we are building in the open. Create an account to follow progress, or get in touch about what you would use it for.