For professionals

Lab automation that doesn't fight you back.

Scripted instrument control, live dashboards, and AI that helps without taking over. One server for every device on your bench.

What you actually get

One server. Every instrument. One API.

A single server running on your test PC, talking to every instrument over its native protocol. A clean JavaScript API for everything — read a value, set a value, run a sequence. Live dashboards bound to real-time state. AI integration with safety gates. Scripts that keep running while the browser is closed.

No NI license. No LabVIEW dialect. No Python environment that broke last week.

Your instruments

We work with the instruments you already have.

Muxit ships with a generic SCPI driver and an AI that drafts a device-specific connector from a programming manual. Any SCPI-compliant instrument over TCP, serial, or USB-TMC works out of the box.

Vendors our users plug in: Keysight, Tektronix, Rohde & Schwarz, Keithley, Fluke, Yokogawa, Siglent, Rigol, BK Precision, Chroma, Kikusui, GW Instek, Aim-TTi, Anritsu, National Instruments, Owon.

Categories: oscilloscopes, multimeters, power supplies, power analyzers, electronic loads, source/measure units, signal generators, spectrum and network analyzers, frequency counters, data acquisition.

For instruments with native vendor SDKs — closed-source C/C++ or .NET — we ship compiled plugins built and signed by the Muxit team. One-time purchase, lifetime access.

What it changes about your day

Concrete things that work today.

Test sequences that run while you sleep

Scripted automation for the work you used to do by hand. Define the run once, log everything, halt on anomaly. Comes back in the morning with the data.

burn-in.js
// burn-in.js
const lamp = connector("lamp-psu");
const cam  = connector("webcam");
const file = connector("file-access");

let anomalies = 0;

while (script.running) {
  const current = lamp.measured_current;
  const lit = ai("Is the lamp still on?", cam.snapshot) === "yes";

  file.appendLine({
    path: "burn-in.csv",
    text: `${timestamp()},${current},${lit}`,
  });

  if (current < 0.05 || !lit) {
    anomalies++;
    if (anomalies > 3) {
      lamp.output = false;
      log.error("Test halted — too many anomalies.");
      break;
    }
  }

  delay(60_000);
}

Multi-instrument coordination in one script

PSU, DMM, temperature logger, and a camera, all in the same script, all in the same dashboard. No four different apps — just one place to rule them all.

Voice control while your hands are full

Two probes in your hands, both eyes on the scope, and you still need the PSU at 5.2 volts. Just say it.

  • "Set channel A to 5.2 volts."
  • "Start logging temperature to bench.csv."
  • "Run the LED sweep."

Voice in, hardware responds. Tool calls are visible and gated.

Camera-aware automation

Point a webcam at your setup. Ask whether the LED is still lit, whether a non-programmable display has changed, whether the solder joint looks right — and turn the answer into action. Vision turns any camera into a sensor, and any instrument with a display into something readable.

vision.js
const cam = connector("webcam");
if (ai("Is the LED still on?", cam.snapshot) === "no") {
  psu.output = false;
  log.warn("LED failed — PSU disabled.");
}

Safety interlocks across instruments that don't normally talk

Over-temp shutdown, over-current cutoff, dead-man checks. The kind of thing you'd hard-wire if you could, written in ten lines instead.

interlock.js
const sensor = connector("thermocouple");
const psu    = connector("psu");

while (script.running) {
  if (sensor.temperature > 60) {
    psu.voltage = 0;
    log.warn("Over-temp! PSU disabled.");
  }
  delay(500);
}

AI integration

AI that helps without taking over.

Muxit's AI integration is a working tool, not a chat gimmick.

Natural language, real hardware.

"Set the voltage to 12V", "Run the calibration sequence", "Move the robot up 5 millimeters." Plain English, real instruments responding.

Tool calls are visible and gated.

Every action the AI takes is logged. Write operations require explicit approval by default; you choose what the AI is allowed to do unsupervised.

Local LLM support.

Point Muxit at Ollama or LM Studio for fully offline, air-gapped operation. Your prompts and your data never leave the network.

MCP integration is free, on every tier.

Bring your own AI client — Claude Desktop, Claude Code, ChatGPT, any MCP-aware tool — and connect it directly to your bench. No Muxit AI credits required if you'd rather use your own provider.

The AI drafts drivers, too.

Plug in a new instrument, point the AI at its programming manual, and Muxit generates a working connector in minutes. Plain JavaScript, no black box, hot-reloadable, write-gated.

Built to be defensible

The kind of facts you want when someone asks why.

Plain JavaScript end to end.

Connectors and scripts are readable JavaScript files in a folder you can put under version control. Diff them, review them, commit them. Nothing is hidden.

Sandboxed execution.

Scripts run in a locked-down V8 engine with no filesystem, network, or shell access. They can only talk to the hardware you've explicitly connected.

No vendor lock-in.

Drivers are open code. Connectors are open code. Your scripts are open code. The data is your data, in formats you choose.

Local-first by design.

The server runs on your machine. AI features are optional and can be routed to a local LLM. You can run Muxit fully air-gapped.

Signed plugins.

Compiled drivers are RSA-signed and verified at load time. You can see who built every component.

When you need to prove it: Lab

Engineering work that has to defend itself.

Pro is for engineering work. Lab is for engineering work that has to defend itself — to a QA manager, an auditor, a customer, a regulator.

Audit log.

Full history of every device interaction on the installation, exportable to CSV or JSON. Who or what did what, when, with which value.

Safety policy engine.

Per-connector write limits, confirm gates, AI agent restrictions. Define the rules once, enforce them across every script and AI call.

Procurement-friendly invoicing.

Annual billing, VAT-ready invoices, the things that make finance departments stop emailing you.

For organisations deploying across multiple labs, Enterprise covers site licensing, custom driver development, and on-site integration support.

See full pricing →

Where we are

A note on where we are.

Muxit is in active development, approaching alpha — built and maintained by a small, technical team with deep hands-on experience in industrial measurement and control.

That's a deliberate choice you should know about. It means rough edges in places. It also means the roadmap is shaped by a small number of early users with real problems, not by committee or by what's easy to ship. If you adopt Muxit now, you have a direct line to the people building it — and you'll see your feedback in the next release, not the one after the next funding round.

If lab automation is something you've quietly wished worked better for years, this is the rare moment to influence what it becomes.

Talk to the team →

Pricing

Three tiers for professional work.

  • Pro — €29/month or €279/year. Everything you need for daily engineering work.
  • Lab — €99/month or €949/year per installation. Pro plus audit log, policy engine, and procurement-friendly billing.
  • Enterprise — Custom. Site licensing, dedicated support, on-site integration.

50% academic discount for verified students, educators, and researchers.

See full pricing →

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.

Get early access →