// led-iv.js const psu = connector("psu"); const dmm = connector("multimeter"); const file = connector("file-access"); psu.output = true; for (let v = 0; v <= 3.5; v += 0.05) { psu.voltage = v; delay(100); file.appendLine({ path: "iv.csv", text: `${v},${dmm.measured_current}`, }); } psu.output = false;
For makers
Lab-grade automation, on your bench.
The same platform R&D engineers use — at home-lab prices. Connect your scope, your PSU, your multimeter, your ESP32, and the tangle of stuff you wired yourself, and run it all from one place.
Not your bench? See Muxit for professionals →
What you actually get
One server. Every device on your bench.
A single server running on your machine, talking to every device on your bench. A clean JavaScript API for everything. Live dashboards. Voice and vision when you want them. Scripts that keep running while you sleep.
If your devices support USB, Serial data or SCPI, you can communicate with it. Whether it is the scope and PSU you've got, the ESP32 you flashed last weekend or the cheap multimeter from AliExpress and the second-hand Rigol you found on Ebay.
Your gear
Yes, your gear is supported.
Muxit ships with a generic SCPI driver and an AI that drafts a connector for almost any instrument from its programming manual. If your scope or PSU speaks SCPI over USB, serial, or LAN, it works.
Brands you'll recognise from the home-lab world: Rigol, Siglent, Owon, Aim-TTi, GW Instek, Hantek, Riden, BK Precision. Higher-end gear too — Keysight, Tektronix, Keithley, Fluke — same driver, same connector, same scripts. Your second-hand HP from a decade ago and your friend's new Keysight scope use exactly the same code.
If your instrument doesn't speak SCPI, the AI can usually draft a JavaScript driver from whatever programming reference the vendor put in the manual. And for anything you wired yourself — ESP32, Arduino, Pi — Muxit speaks MQTT and serial out of the box. Your homemade hardware fits.
What it's actually for
Real things you'll actually run.
Characterisation runs
IV curves, frequency response, temperature coefficients. The kind of measurement you'd do by hand, then realise you should have automated, then do by hand again next week. Write the script once, run it whenever.
Long-running tests that watch themselves
Burn-in a salvaged power supply for a week. Track the drift on your oven controller overnight. Stress-test a battery pack. Define what "still healthy" means once — current in range, temperature stable, indicator still lit — and Muxit tells you the moment something's off.
Voice control while you're soldering
Hands full, iron hot, and you still need the bench supply at 5 volts. Just say it.
- "Set the supply to 5 volts."
- "What's the current draw?"
- "Save the scope screenshot to today's folder."
Camera-aware automation
Point a webcam at whatever you're working on. Ask whether the LED is still lit, whether the print is finished, whether the indicator on your old non-programmable bench supply has moved. Vision turns any camera into a sensor. It's the only way to read instruments that don't have a port.
const cam = connector("webcam"); if (ai("Is the LED still on?", cam.snapshot) === "no") { psu.output = false; log.warn("LED failed."); }
Reactive setups that aren't quite a "lab"
Sensors driving lights, motors, and sound. A homemade environmental monitor that pings you when the basement floods. A grow-light controller that watches the plant. Muxit doesn't care whether you call it a lab, an installation, or just the thing on the desk.
Multi-device orchestration
The point of Muxit isn't any one of these jobs — it's that they're all the same script. PSU, scope, sensor, ESP32, webcam, all in one place, all in one language, all in one dashboard.
Homemade hardware
Your homemade hardware fits.
ESP32, Arduino, Pi-zero — anything you wired yourself, anything running custom firmware. There's no Muxit-specific protocol to flash. If your microcontroller publishes data on MQTT, Muxit can read it. If it speaks a few lines of serial, Muxit can read that too. Bring the hardware as it is; Muxit meets it where it lives.
// esp32-temp.js — your microcontroller publishes on MQTT const esp = connector("esp32-bench"); log.info(`Bench temperature: ${esp.temperature}°C`);
A connector is a small JavaScript file that says here's how to talk to this thing. Twenty lines, sometimes less. You write one once and the rest of Muxit treats your homemade hardware exactly like a commercial instrument — same scripts, same dashboards, same AI access.
AI
AI you actually use.
Not a chat gimmick stapled to the side. The AI in Muxit drives real hardware, with real safety gates.
Voice and natural language.
Talk to your bench while your hands are full. Tool calls are visible — you see what the AI is about to do before it does it.
MCP integration is free, on every tier.
If you've got a Claude Desktop or Claude Code setup already, point it at Muxit and your AI client gets direct access to your hardware. Use your own provider, no Muxit credits required.
The AI drafts drivers.
New instrument arrives, you point the AI at the programming manual, and it writes a working connector. Plain JavaScript, you read it and approve it before it runs. Drivers are the single biggest reason hobbyist lab automation has historically been a pain. Muxit turns that on its head.
Local LLM if you want it.
Point Muxit at Ollama or LM Studio and run AI features fully offline. Useful when you don't want your prompts touching anyone's cloud.
The small things
Plus the small things that make it nice.
One window for everything.
Hardware on the left, scripts and dashboards in the middle, AI on the right. Drag a property from the hardware panel into a script and Muxit writes the right code for you.
Dashboards that update themselves.
Drag widgets onto a grid, bind them to live values, watch them tick. Scripts can be started and stopped from buttons. Everything is JSON, so you can put your dashboards in git.
Headless if you want it.
Run Muxit on a Pi or an old laptop in the corner of the room and connect to it from your real computer. Your tests keep running when you close the lid.
Remote access that isn't terrifying.
HTTPS with password auth on your LAN, plus mDNS so any device on the network finds the server by name. Drop it behind a VPN of your choice when you need to reach it from elsewhere.
Pricing for one-person labs
Pay nothing, pay nine, or pay once.
- Free — €0, forever. Generous limits for trying everything out and running small projects. Includes MCP integration, so if you bring your own AI client you can do a lot before paying anything.
- Maker — €9/month or €89/year. Unlocks the SCPI driver and
AI-assisted connector authoring (the thing that makes any lab instrument
work). Adds Muxit's built-in AI chat and voice with a monthly credit
allowance, plus the
ai()function in your scripts. Adds remote access and email support. - Founding Member — €399 one-time. Lifetime Pro features. 500 AI credits per month for three years. Limited to the first 250 waitlist signups. If you're going to be using this for years anyway, the math is straightforward.
Where we are
A note on where we are.
Muxit is in active development, approaching alpha. It's built by makers who got frustrated with the gap between "five separate vendor apps that don't talk to each other" and "the €10,000 LabVIEW license your day job has." The gap is wider than it should be, and Muxit is the bridge.
If you adopt it now, you'll see your feedback in the next release. The roadmap is shaped by a small number of real users with real benches — and there's room for yours.
Be at the bench when it opens
Join the waitlist.
Early access, launch pricing locked in for your first year, and a heads-up when founding-member spots open.