Nothing special. Just plug in some spare mice and keyboards. MouseMux will detect the new devices and automatically add them. Generally what people do is buy a USB hub and use that to plug in more mice and keyboards. Theoretically you can add unlimited devices, we tested up to 32 simultaneous users (64 input devices).

Occasionally a virus scanner will flag MouseMux as unsafe - under the hood MouseMux has a lot of complex behaviour and manipulates the input layer of windows, some virus scanners will find that behaviour suspect and give you an alarm. We're in constant contact with various manufacturers of security tools to keep MouseMux whitelisted. Please drop us a line if your virus scanner flags MouseMux as suspect.

MouseMux generates telemetry to help us understand how it behaves on various systems. All data is anonymized, no personal data is sent to our servers. No interaction data is sent, so no keystrokes, on which window you clicked etc. We’re mainly gathering which features are being used, how long some operations take and what warnings are generated during a MouseMux session. We’ve built a list of all specific data that is sent to our servers – find it at https://mousemux.com/pages/telemetry - feel free to contact us if you have any questions or concerns!

All windows versions are supported, from Window XP up to Windows 10, including all the server editions. The program comes in both 32bit and 64bit versions and will automatically select for the appropriate architecture. There is initial support for Windows Apps (UWP) and this will be updated in the coming period. Windows 11 will be tested soon.

Keyboard pairing means linking a keyboard to a mouse – together they represent a (virtual) user. Pairing is simple: move a mouse and hit a key on the keyboard that you want to pair. You will see both the mouse and keyboard light up orange in the row of your user number. Working with paired keyboards may feel unintuitive at first; here’s a use case to explain why. User A and B sit behind the same computer, there are two mice attached and one single keyboard. Both users are interacting with the desktop with their own mouse. User A pairs his mouse to the keyboard. User A clicks on notepad and starts typing. User B takes over and types on the same keyboard. Now user B clicks on some other window and expects to start typing in that window – but since the keyboard is paired with user A, and user A did not click on any other window user B will keep typing in notepad! Practically speaking; user B does not have a keyboard – he/she just follows what the focus window is of user A. This may feel unintuitive because generally you expect to be able to type in a window once you click on it. For this scenario we added an option to synchronize all keyboards (even if it’s just one) to all users – that means mice can operate independently but the keyboard is shared for all users. You can uncheck the Multi Keyboard option in the main UI to disable per-user keyboard pairing – when this option is switched off the keyboard(s) will work just like in normal windows – follow the window with focus to send key data to. Of course, if you have two keyboards and two mice and user A and B are both working on the desktop we suggest to keep the Multi Keyboard option checked and pair each keyboards to an individual mouse so that both A and B can work independently with each a mouse and keyboard.

Yes we have an SDK to allow MouseMux to run in the background (hidden) and create mouse pointers and user via API calls. Please drop us a line for more information.

MouseMux is continually being updated (and will update on your computer automatically). We plan to add networking support so people can remotely join a MouseMux session. We also plan to add screensharing at a later stage. We also have an initial SDK where telemetry for each user is recorded (important in SCADA) and where users can have granular rights. Feel free to drop us a line if you have any cool ideas on how to extend MouseMux!