Will Muxit work with your device?

The honest premise

One small file per device. After that, it's permanent.

Muxit ships with a handful of built-in drivers (webcam, ONVIF, MQTT, files, G-code), three declarative protocols (Scpi, LineText, BinaryStream) that cover most benchtop, serial, and binary devices, and transports for serial, TCP, and USB-TMC. For your specific device, you (or the built-in AI) write one small connector config: a readable JavaScript file that lives in your workspace, gets version-controlled like any other code, and is yours to keep, edit, or share.

That's the trade. We don't pretend to have shipped a driver for every instrument that exists; we ship the tools that make the one-time connect step take minutes instead of weeks. The more your device speaks a standard (SCPI, MQTT, ONVIF, plain serial), the less work there is — often zero.

What the AI actually does

End-to-end for declarative protocols. A capable helper for the rest.

The "AI drafts your config" claim isn't aspirational: for the declarative protocols (Scpi, LineText, BinaryStream) it's a working flow on Maker tier and up. Here it is for a SCPI instrument, in four steps you can watch happen:

For Tier C (custom drivers), the serial-probe connector gives the AI an interactive view of the wire so you can reverse-engineer together. Fully automated drafting for arbitrary custom protocols is on the roadmap.

Your step-by-step

What to do when you sit down with a new device.

From the bench

Three real connectors.

Same workspace, same API. The first two are declarative protocol configs with no driver code at all; only the last needed a custom driver.

// rigol-dp832.js — declarative SCPI connector
export default {
  protocol: "Scpi",
  connection: { type: "tcp", host: "192.168.1.100" },
  config: {
    schema: {
      properties: {
        voltage: { cmd: "VOLT", type: "float", unit: "V" },
        current: { cmd: "CURR", type: "float", unit: "A" },
        output:  { cmd: "OUTP", type: "bool" },
      }
    }
  }
};

// arduino-logger.js: LineText protocol, no driver code
export default {
  protocol: "LineText",
  connection: { type: "serial", port: "COM3", baudRate: 115200 },
  config: {
    schema: {
      properties: {
        temperature: { prefix: "TEMP: ", type: "float", unit: "C" },
        humidity:    { prefix: "RH: ",   type: "float", unit: "%" },
      }
    }
  }
};

# bench-rig.py — wrap your lab's own Python code as a Muxit device
from rig_io import connect_serial, read_voltage, read_temperature, set_pump_rate

def connect():
    connect_serial("/dev/ttyUSB0")

def voltage():
    return read_voltage()

def temperature():
    return read_temperature()

def pump_rate(rate_ml_min):
    set_pump_rate(rate_ml_min)

Honest limits

What doesn't have a clean path yet.

We'd rather you find this out here than after a purchase. These categories don't have a documented Muxit path today. Some are on the roadmap; others depend on community demand.

Missing your category? Tell us what device — it's how the roadmap gets prioritised.

What you end up owning

One small file. Yours forever.

At the end of the setup — five minutes, fifteen minutes, or a few hours — you have a single readable JavaScript or Python file in your workspace. Not a binary, not a vendor account, not a subscription per device.

• No vendor lock-in. The connector is plain code in a folder you own.
• No black-box driver. You can read every line, change anything, audit what it does.
• No per-device licence. One Muxit licence covers every device you connect.
• Version-controllable. Diff it, review it, commit it like any other source file.
• Shareable. Hand it to a colleague, drop it in a repo, contribute it back.

Try it with your device → How the architecture works →