Make your Windows software multi-user.
Multiple people, one Windows PC, and only one of them can touch the mouse. That is the problem we remove. MouseMux gives everyone their own cursor on the same Windows machine at once, wherever they need it on the desktop, together in one app or side by side in different ones, whether they are sitting at the PC or connected over a remote desktop. We build it into your product, or hand you the engine to do it yourself.
Just want to run MouseMux as-is on your own machines? The Ultra license covers commercial use for a one-time fee, no call needed. This page is for building it into your own product, hardware or a custom app.
What we build
Same engine underneath, three different ways in. Whichever fits, it starts with one conversation and a small, fixed-price pilot on your own setup.
Get real teamwork back.
An in-house collaboration tool, built around your tools, in your brand
Remote work took something with it: the feeling of gathering around one screen and getting things done as a team. This brings that back. Your remote people log into the office and work side by side in whatever you actually use, your own product, somebody else's software, even the Excel sheet that secretly runs the company. We shape it into your own little collaboration product: built for your team, your niche and nobody else's, and it ships under your brand, not ours.
Built for simulators.
For flight, ATC and naval trainers, and every rig with exotic hardware
Simulator builders were among our first enterprise users, and they still push the engine hardest. Instructor and trainee share one running scenario, each driving their own side of it. And the hardware these rigs live on, the yokes, throttle quadrants and control panels, feeds into the same session, so the rig behaves like the real thing instead of a desktop with a pile of USB devices. From tower trainers to submarine sims: if it teaches someone to operate a machine, we can make it multi-user.
A cursor for every operator.
For SCADA stations, factory lines and control-room walls
Picture a control room: one big screen, a row of operators, and a single mouse only one of them can hold at a time. That is a bottleneck exactly where you can least afford one. We give every operator their own cursor on the same screens, on the control-room wall and right on the factory line. And because not everyone is allowed to touch everything, rights are managed per person: who can change a setpoint, who can stop the line, who can only watch. Roles decide it, the system enforces it, and the controls that should never be shared simply can't be. We build it for you, or your team builds it themselves.
Where it's already running
A two- or three-person crew runs an entire broadcast off one PC, the switcher, the audio, the graphics, the chat, each role with its input kept separate. When something goes sideways mid-stream, the right person dives in and fixes their bit without fighting anyone for the mouse.
Staff and customer share one screen, and the customer scans their own items. Each scan lands in the right field instead of grabbing focus and jumping to whatever window was open. That focus-stealing is most of why shared counters never work, and removing it is the whole trick.
An instructor and a room of trainees work the same scan or scenario at once. Who gets to point, measure or take the next step is set per person, so the session stays a lesson instead of a scramble for the mouse.
Manufacturing lines · Flight & ATC simulators · SCADA & process control · Energy & utilities · Command & surveillance centers
The team behind MouseMux
MouseMux comes from a small, senior team that has spent more than two decades on one problem: low-level input routing. Getting devices to the right people, HID, device emulation, input simulation and virtualization, remote collaboration, and all the failure modes that only ever turn up on real hardware in a real deployment. It is a narrow, deeply unglamorous specialty, and it is the one we know cold.
Run a project with us and you deal with the people who actually built the engine. No support tier, no hand-off to someone reading from a script. Just straight answers: what is possible, what is not, and how to get it into your product.
More than two decades of low-level input routing
HID, input injection, multi-device routing and the edge cases most teams never see.
Direct architect access
You talk to the people who built the engine, not a first-line support queue.
Proven where "mostly" isn't enough
Running in industrial, aerospace and simulation settings where "mostly works" doesn't cut it.
Input simulation & virtualization
We simulate and virtualize devices at the Windows input layer, emulating mice, pens, touch, gamepads and specialized controllers, and capturing or injecting input, so unusual hardware, simulators and remote tools behave like the real thing.
Projects start at €900
Every engagement begins the same way: a small, fixed-price pilot on your own software, so you see it working before you commit to anything bigger. Send us a few lines about what you're building. We'll tell you honestly whether MouseMux fits, and exactly what it would take.