---
{"title": "How DevWebUI runs local dev servers from one dashboard", "description": "How DevWebUI knows which dev servers a repo runs, how you start and watch them from one dashboard, its limits, and what it needs to run.", "url": "https://saydeploy.com/how-devwebui-runs-every-dev-server-in-a-repo-from-one-dashboard/", "date": "2026-11-10"}
---
How DevWebUI knows which dev servers a repo runs, how you start and watch them from one dashboard, its limits, and what it needs to run.

One small file per repo lists the servers to run, and DevWebUI writes processes you change in the dashboard back to that file. [^1] From that one dashboard you start, stop and restart your local dev servers and see each one's status, CPU, memory and logs. [^1] DevWebUI is source-available: free for personal and other noncommercial use, and commercial use needs a licence from LunarWerx. [^1]

| Topic | What the description says |
|---|---|
| Server list | One small file per repo lists the servers to run, and processes changed in the GUI are written back to that file. [^1] |
| Dashboard | Start, stop and restart your local dev servers from one dashboard, and see each one's status, CPU, memory and logs. [^1] |
| Taken ports | Shows which process holds a taken port and can free the port if you ask. [^1] |
| Error log | One log that merges repeats, is kept across restarts, and opens each file:line link in your editor. [^1] |
| Docker compose | A compose block starts the repo's docker compose stack first, waits for its ports and sets DATABASE_URL-style env vars. [^1] |
| Alerts | Threshold alert rules, with a history of the alerts that fired. [^1] |
| Own port | Opens any managed server at `<target>.localhost:4000`, with HTTP and WebSocket (HMR) traffic passed through. [^1] |
| Command line | A devwebui command-line tool talks to the same REST API, so you can control processes without the GUI. [^1] |
| AI agents | A stdio MCP server with 43 tools lets AI agents control the same daemon the GUI uses. [^1] |
| Platforms | Every system runs it from source with Bun, and the tray app is Windows-only for now. [^1] |
| Install ping | An anonymous install ping is sent with update checks unless you set DEVWEBUI_NO_PING=1. [^1] |
| Price | Free, and its core features need no account. [^1] |
| Licence | Source-available under the PolyForm Noncommercial License 1.0.0: free for noncommercial use, and commercial use needs a licence from LunarWerx. [^1] |

## What it does and why

DevWebUI is made by the team that publishes this site. About 300 copies of DevWebUI checked for updates in the 30 days to 8 November 2026, from 20 countries. [^1] A dev server is the program that serves a project on your own computer while you work on it, and one repo can need several of them at once.

One small file per repo lists the servers to run, and DevWebUI writes processes you change in the dashboard back to that file. [^1] From the dashboard you start, stop and restart each of those servers, and you see its status, CPU, memory and logs. [^1]

A port is the numbered address a server listens on, and two servers cannot hold the same one. When a port is already taken, DevWebUI shows which process holds it and can free the port if you ask. [^1]

Errors are collected into one log that merges repeats and is kept across restarts, and each file:line link in it opens in your editor. [^1]

You can also open any managed server through DevWebUI's own port, at `<target>.localhost:4000`, with HTTP and WebSocket (HMR) traffic passed through. [^1] HMR is the live reload that updates a page in the browser while you edit its code.

## How it works step by step

1. **Get DevWebUI.** First get the code from its GitHub repo, LunarWerxs/DevWebUI. Then, on any operating system, run bun install and then bun run dev. [^1] Bun is a program that runs JavaScript projects.

2. **List the repo's servers.** One small file per repo lists the servers to run. [^1] DevWebUI's description does not say what the file is called or how to make it, so look that up in DevWebUI's own documentation before you start.

3. **Bring up what the servers depend on.** A compose block starts the repo's docker compose stack first, waits for its ports and sets DATABASE_URL-style env vars. [^1] Docker compose starts a group of services, such as a database, together. Env vars are settings a program reads when it starts, and DATABASE_URL is the usual one that tells an app where its database is.

4. **Run the servers from the dashboard.** Start, stop and restart each server, and watch its status, CPU, memory and logs. [^1] A process you change there is written back to the repo's file. [^1]

5. **Set alerts.** You can set threshold alert rules and see a history of the alerts that fired. [^1] A threshold is a limit you pick.

6. **Work without the dashboard when you want to.** A devwebui command-line tool talks to the same REST API, so you can control processes without the GUI. [^1] A REST API is a set of web addresses that other programs call to give DevWebUI instructions.

7. **Let AI agents help.** A stdio MCP server with 43 tools lets AI agents control the same daemon the GUI uses. [^1] MCP is a standard way for AI agents to use another program's tools, and the daemon is the part of DevWebUI that keeps running in the background.

## What it does not do

On every system you run DevWebUI from source with Bun, and the tray app is Windows-only for now. [^1]

If the last shutdown was not clean, as after a crash or a power cut, the next launch loads your projects but starts nothing automatically. [^1] You start the servers you want again from the dashboard.

The claims do not say whether DevWebUI can run servers on another computer, so check that before you choose. They also do not name the repo's server file, which is the second thing to look up.

## What you need to run it

On every system you run DevWebUI from source with Bun, and the tray app is Windows-only for now. [^1] On any operating system you run bun install and then bun run dev. [^1] On Windows, a tray icon runs the daemon in the background and has Open, Restart and Quit options. [^1]

It is source-available under the PolyForm Noncommercial License 1.0.0: free for personal and other noncommercial use, and commercial use needs a licence from LunarWerx. [^1] An anonymous install ping is sent with update checks unless you set DEVWEBUI_NO_PING=1. [^1] DevWebUI is free, and its core features need no account. [^1]

With DEVWEBUI_REQUIRE_AUTH=1 set, a credential is required on every /api route except a few listed exceptions, and browsers get a key by typing a 6-digit pairing code the daemon prints. [^1] A credential is the key a program shows to prove it may use DevWebUI's API.

## Frequently asked questions

### How does DevWebUI know which dev servers to start?

One small file per repo lists the servers to run, and DevWebUI writes processes you change in the dashboard back to that file. [^1] A compose block can also start the repo's docker compose stack first, wait for its ports and set DATABASE_URL-style env vars. [^1] DevWebUI's description does not say what the server file is called, so look that up before you set up a repo.

### Is DevWebUI free to use?

It is source-available under the PolyForm Noncommercial License 1.0.0: free for personal and other noncommercial use, and commercial use needs a licence from LunarWerx. [^1] DevWebUI sends an anonymous install ping with update checks unless you set DEVWEBUI_NO_PING=1. [^1] It is free, and its core features need no account. [^1] You run it from source: on any operating system you run bun install and then bun run dev. [^1]

### Which systems does DevWebUI run on?

On every system you run DevWebUI from source with Bun, and the tray app is Windows-only for now. [^1] On any operating system you run bun install and then bun run dev. [^1] On Windows, the tray icon runs the daemon in the background with Open, Restart and Quit options. [^1]

### Can AI agents control dev servers in DevWebUI?

A stdio MCP server with 43 tools lets AI agents control the same daemon the GUI uses. [^1] MCP is a standard way for AI agents to use another program's tools. A devwebui command-line tool talks to the same REST API, so you or a script can control processes without the GUI. [^1]

### What does DevWebUI start after a crash?

If the last shutdown was not clean, the next launch loads your projects but starts nothing automatically. [^1] You then start the servers you want from the dashboard, where you also see each one's status, CPU, memory and logs. [^1] The error log is kept across restarts, so the errors from before the crash are still there. [^1]

DevWebUI is free, and its core features need no account. [^1] - [Visit DevWebUI](/go/start)

## Sources

[^1]: DevWebUI's own description of itself (the product of this site's publisher) (/go/start)
