Installation

Get Muxit running on your machine in under a minute.

Quick Install (Recommended)

Open PowerShell and run:

irm https://raw.githubusercontent.com/muxit-io/muxit/main/install.ps1 | iex

This downloads the latest release, extracts it to %LOCALAPPDATA%\muxit, and adds it to your PATH. No prerequisites required — the binary is fully self-contained.

Manual Download

If you prefer to install manually:

1. Go to the GitHub Releases page
2. Download muxit-win-x64-v<version>.zip (the file name includes the release version)
3. Extract the zip to a folder of your choice (e.g. C:\muxit)
4. Run muxit.exe from the extracted folder

System Requirements

Requirement	Details
OS	Windows 10 or later (x64)
Runtime	None — self-contained binary, no .NET or Node.js needed
Disk space	~150 MB
Network	Required for AI features and license activation; optional otherwise

First Run

After installing, start Muxit:

muxit

This starts the server and opens your default browser to http://localhost:8765.

On first run, you'll see the Workspace Setup screen. Create a new workspace or open an existing one to get started. See Workspaces for details.

Other start modes:

muxit                       # Start without opening browser
muxit --no-tray             # Start without system tray icon
muxit --port=9000           # Use a custom port

Verify It Works

Once the server is running and the browser opens:

1. Check the Hardware panel — Click the plug icon in the left Activity Bar. You should see test-device listed with live properties (temperature, label, count, etc.)
2. Open a demo dashboard — In the Explorer sidebar, expand dashboards/ and click demo.dashboard.json. You should see live gauges and widgets
3. Run a script — In the Explorer sidebar, expand scripts/ and click hello.js. Click the Run button in the editor toolbar. Check the Output panel at the bottom for log messages

If you see the test device with updating values, Muxit is working correctly.

---

What's Included

Muxit ships as a single self-contained package — no hardware needed to get started:

Category	What's Included
MuxitServer	Self-contained .NET 9.0 binary (no runtime install needed)
Built-in drivers	TestDevice, Webcam, ONVIF (IP camera), FileAccess, MqttBridge
Example connectors	test-device, webcam, gui, store, and more in workspace/connectors/
Example scripts	hello.js, examples/sinewave.js, examples/psu-voltage-ramp.js, the tutorials/ series, and more
Example dashboards	demo, test-device, gcode, psu, and more
Example agents	temperature-monitor, pick-and-place
Documentation	Built-in at /docs/ in the web UI

The TestDevice is a simulated device that exercises every data type (strings, numbers, booleans, arrays, objects). It's always available and doesn't count against your connector limit — making it the perfect learning tool.

---

Updating

The easiest way is straight from the app: Help → Check for Updates…. When a newer release is available, Muxit downloads it, installs it in place, and restarts onto the new version automatically — the page reconnects on its own when the server is back. Your workspace files (connectors, scripts, dashboards, agents, config) are preserved; only the binary and bundled driver packages are replaced.

In-app self-install works on Windows x64, Linux x64, and Linux arm64. On other platforms (or builds that can't self-install) the menu offers a download link instead.

You can also update from the command line:

muxit update

Or re-run the platform installer, which detects the existing installation and updates in place:

irm https://raw.githubusercontent.com/muxit-io/muxit/main/install.ps1 | iex

Muxit also checks for updates automatically on startup and surfaces them in the Help menu.

---

Troubleshooting

Installer fails to download — Check your internet connection. The installer fetches from GitHub Releases. Corporate firewalls may block raw.githubusercontent.com.

Port 8765 already in use — Another instance of Muxit (or another program) is using the port. Stop the other process or use --port=9000 to pick a different port.

muxit command not found after install — Close and reopen your terminal. The installer adds the install directory to your user PATH, but existing terminal sessions need to be restarted.

Windows SmartScreen warning — On first run, Windows may show a SmartScreen warning because the binary isn't code-signed yet. Click "More info" then "Run anyway".

For more help, see the Troubleshooting Guide.