Network Access & Team Use

Kitted runs a local web server on the machine where the app is installed. By default it listens on all network interfaces, which means anyone else on the same local network can open Kitted in their browser without installing anything.

How It Works

When Kitted starts, it binds its built-in web server to port 9090 on all network interfaces (e.g. 0.0.0.0:9090). Team members on the same Wi-Fi or wired network can reach it by opening the URL shown in Settings → Network access in their browser - no installation required on their end.

The Kitted app itself (the Electron window) connects to the same server via http://localhost:9090. Remote browsers connect using the machine’s LAN IP address instead.

Enabling or Disabling Network Access

Go to Settings → Network access.

The Listen on all network interfaces toggle controls whether remote connections are accepted:

State	Behaviour
Enabled (default)	The server listens on all interfaces. Devices on the same network can connect.
Disabled	The server listens on `localhost` only. Only the machine running Kitted can access it.

Changing this setting requires an application restart to take effect. After saving, a prompt reminds you to restart.

Finding the Connection URL

When network access is enabled, Settings → Network access shows the URL (or URLs, if the machine has multiple network adapters) that remote devices should use. A QR code is displayed alongside each URL for quick scanning from a phone or tablet.

The URL format is:

http://<local-ip>:9090

For example: http://192.168.1.42:9090

The IP address shown is the machine’s current local IP, assigned by your router. If the host machine’s IP changes (e.g. after a router restart), team members will need to use the updated URL. Assigning a static IP to the host machine on your router avoids this.

Connecting from Another Device

Make sure the host machine is running Kitted.
Open a browser on the other device (phone, tablet, or another computer on the same network).
Navigate to the URL shown in Settings → Network access, or scan the QR code.
You will be presented with the login screen. Enter the password set during first-run setup (username: admin).

Once logged in, the browser session behaves identically to the desktop app. All data is shared in real time - changes made on any device are immediately visible to everyone.

Authentication Behaviour

Connection source	Login required?
The host machine running the app	No - signed in automatically (unless Require password on this machine is enabled in Settings → Security)
Any other device on the network	Yes - the admin password is always required

There is currently one user account (admin). All team members share this account and have full access to all features.

Firewall Considerations

For remote devices to connect, port 9090 must not be blocked by a firewall on the host machine.

Windows: Windows Defender Firewall may prompt you to allow Kitted when the app first starts. If you dismissed the prompt, add an inbound rule manually: Windows Security → Firewall & network protection → Advanced settings → Inbound Rules → New Rule for TCP port 9090.
macOS: macOS may prompt for confirmation when Kitted first attempts to accept incoming connections. If blocked, go to System Settings → Network → Firewall → Options and ensure Kitted is not listed as blocked.
Linux: If you have ufw active, run sudo ufw allow 9090/tcp. Other firewalls (firewalld, iptables) will need an equivalent rule.

The server only accepts connections on your local network. Port 9090 should not be exposed to the public internet.

Restricting Access to This Machine Only

If you want to prevent anyone else on the network from accessing Kitted, disable Listen on all network interfaces in Settings → Network access and restart the application. The server will then only accept connections from localhost, and no login screen will be shown to remote devices (connections will simply time out).