Stop walking to the bench to flash and reset.

Your boards stay on the bench. You don't have to.

VBUS-04 is a 4-port USB 2.0 hub on your network. Each port attaches to your machine as a local USB device, wherever you work. Every port's power is independently switchable, with reset and boot GPIO per port. Your workflow stays the same - erase, flash, monitor as you've always done.

Early access $129 · Retail $249 · Ships Feb 2027

Reserve yours now for $10

Compare.

OptionsVBUS-04DIY
Unified controls-
Per-port power switchingmaybe*
Network attach
Reset + boot GPIOplumb*
Price$129~$150 + your weekends

*compatible hub · plumbing

Early-access price, first 100 units.

How it works.

Install

$ curl -LsSf https://vbus.dev/install.sh | sh

Discover

Power the box on.

$ vbus search SERIAL HOSTNAME ab12cd vbus-ab12cd.local $ vbus setup ab12cd default box set to ab12cd

Plug in

Plug a board into any port. The box powers the port (all ports on by default, configurable), then enumerates it.

$ vbus ls PORT NAME STATE POWER 1 esp ready on 2 - empty off 3 jlink ready on 4 - empty off $ vbus attach esp port 1 attached -> /dev/ttyUSB0 (esp)

The target attaches as a normal USB device. Your toolchain doesn't know the difference.

Flash

$ idf.py erase-flash -p /dev/ttyUSB0 $ idf.py flash -p /dev/ttyUSB0 $ idf.py monitor -p /dev/ttyUSB0

Bootloader

$ vbus bootmode esp # holds boot, pulses reset - then flash as usual $ idf.py flash -p /dev/ttyUSB0

Power

Cycle a target's power from anywhere - no walking to the bench.

$ vbus power cycle esp esp power cycled

Config

$ vbus config $ vbus config apply board.json

Spec.

VBUS-04 - USB-over-IP hub
Downstream ports4× USB 2.0, power switched per port
Per-port GPIO2× GPIO (reset + boot)
Data isolationD+/D− cut when a port is off
Per-port current1 A max
Ethernet1 Gbps
Remote attachUSB/IP over Tailscale (included)
Power in5 V DC, 4 A total
StatusPer-port LEDs

Why reserve now?

$129 early access, $249 retail. Pay $10 now, $119 when it ships. Ships by Feb 2027 with biweekly build updates starting when you reserve.

Reserve now for $10

Fully refundable until it ships. One email, no questions.

FAQ

Why $10 instead of a full preorder?

Because we're not asking you to fund the project. We're asking who is actually in. Ten dollars filters out the maybe, and it's refundable, so the risk sits with us. That's where it belongs.

Do I need to ssh in to flash? Or to cycle power?

No to both. The target attaches as a local USB device, so you flash with the tools you already use. Power is one command: vbus power cycle esp. The CLI runs on your machine and talks to the box over your LAN or tailnet.

What does the WebUI do? When do I use the CLI, and when ssh?

The WebUI handles setup: see what's attached on each port, join your tailnet, name ports, update firmware. Runtime control is the CLI, run anywhere on your tailnet. ssh is for admin.

My target board draws more than 1 A. Will it work?

Most debug probes, JTAG adapters, and serial bridges draw 200-500 mA, well within the 1 A per-port limit. A target that spikes above that (some RF SoCs under transmit load, anything with an active display) should be powered from a bench supply; VBUS handles the data side.

Does it work with Windows?

Yes, via WSL2. USB-IP attach is native there, and your tools have Linux versions that run unchanged inside WSL. The device appears inside WSL, so you flash with those Linux tools, not the Windows GUI. WSL2 is the supported route today.

Can I cancel and get my money back?

Yes. 100%, no questions asked, any time before your unit ships. One email. After it ships: 30 days to return it, and dead on arrival means a replacement.

Does it do USB 3?

No. USB 2.0 control channel: serial, HID, DFU, debug probes. If you need 5 Gbps throughput, this isn't the box for it.

Why not a DIY rig: Pi, a smart hub, and uhubctl?

That stack works, but you have to find a hub that actually implements per-port power switching. uhubctl's own support list notes most hubs don't, and many that do are out of production. Then wire it, flash it, and debug it when it breaks. VBUS is that rig. If you enjoy building it, keep building. If you want tests to run, take the box.

Can an AI agent use it?

Yes, deliberately. The control surface is a single binary with a small command set, so anything that can run a shell one-liner can drive it: a cron job, a pipeline, a tool-using agent. vbus ls --json speaks to them in plain structured data.

Does it phone home?

No account, no telemetry, no cloud. The box runs Linux and it belongs to you. Reach it over your LAN or Tailscale.