Reference · 2 min read
LAN bind
Optional LAN access for Miton Studio — consent flow, bearer token, configuration, and security expectations.
- Product stage
- Pre-release development
- Last reviewed
- 2026-07-23
- Successful result
- The change is visible in the active project.
Who this is for: power users who want Miton Studio — the local browser console — reachable from another device on the same network (tablet, phone, second machine).
By default Studio serves only on loopback (127.0.0.1:7745). LAN bind opts in to listening on your
local network address.
Overview and tiles: Miton Studio handbook. Discovery: mDNS.
Before you enable it
LAN bind means any device on your network can reach the Studio URL. Miton shows a consent modal the first time you turn it on. You must acknowledge that:
- The console binds to your LAN address (not just localhost)
- Access is gated by a per-device bearer token you must keep secret
- A holder of the token has the same capabilities as the local Studio session (including opt-in write actions when enabled)
Consent is logged per device. Re-open it from Settings → Studio → Show consent again.
Bearer token
Each client device needs its own token:
- Enable LAN access in Settings
- Generate a token; copy it immediately — it is shown once
- Send requests with
Authorization: Bearer <token>
Invalid or missing tokens receive 401 Unauthorized. Revoke tokens anytime in Settings → Studio →
Bearer tokens — revocation is immediate.
Treat tokens like passwords. Rotate them if a device is lost or shared.
Configuration
Settings → Studio → LAN access
| Setting | Default | Notes |
|---|---|---|
| Enable LAN bind | Off | Loopback only when off |
| LAN address | First non-loopback IPv4 | Pick another interface if needed |
| Port | 7745 |
Must match firewall rules |
| mDNS announce | On when LAN enabled | See mDNS |
| Bearer tokens | Per device | Generate and revoke in Settings |
Configuration is per machine — laptops and desktops keep separate tokens.
Security expectations
- Studio is not exposed to the public internet by LAN bind alone — only your LAN
- Traffic is plain HTTP on the LAN unless you terminate TLS with your own reverse proxy
- Studio runs in the Miton desktop process — token holders can trigger the same opt-in write actions you can locally
- Do not share tokens with untrusted devices
For internet exposure you must supply your own reverse proxy and hardening — outside Miton’s default scope.
Disable LAN access
Settings → Studio → LAN access → Disable — stops listening on the LAN and withdraws mDNS announcement.