Fleet
Connect, find, and manage the Msty Nexus machines in your workspace
Fleet shows every Msty Nexus machine connected to the current workspace and the addresses available for reaching each one.
Free includes the current local computer. Pro includes 3 managed machines. Enterprise uses the managed-machine limit assigned to the organization.
Local and managed machines
The desktop app opens directly into a local workspace. The current computer appears without requiring account enrollment.
After signing in with Pro or Enterprise, you can add the current device to the account or connect other machines. Enrollment preserves the machine's existing models, providers, routes, settings, and local token store.
Add a machine
Use either supported path:
- Select Add a machine and run the generated setup command on the target computer.
- Sign in through the desktop app on that computer and approve Add this device.
Both paths consume the same managed-node allowance. Nexus checks capacity when creating the enrollment reservation and again when the machine joins.
Never replace a connector identity that belongs to another account. Switch accounts or continue without adding that device.
Find and identify machines
Give each machine a recognizable name and location. Fleet search can use these labels when a workspace grows beyond a few nodes.
The machine switcher at the top of the Console changes which Runtime the rest of the workspace is managing. Check the selected machine before changing providers, models, routes, tokens, or settings.
Private network access
Private network access makes a Runtime reachable at its advertised LAN or private-network address. Enabling it changes the Runtime listener and requires a restart.
Verify the advertised address before distributing it. Prefer trusted LAN or private VPN connectivity and use a separate client token for each app or operator.
Access from anywhere
Pro Enterprise
Access from anywhere gives a managed machine a hosted HTTPS address that applications can call from outside its private network. It is useful when a desktop tool, server, or trusted teammate needs to reach Nexus without joining the same LAN or VPN.
Free cannot enable Access from anywhere. Pro includes one remote endpoint per managed machine by default. Enterprise uses the remote endpoint allowance assigned to the organization.
How it works
The managed machine keeps an outbound connection to Msty Nexus. Requests sent to its hosted address are relayed to that machine's gateway, so you do not need to open an inbound firewall port, configure router port forwarding, or publish Runtime directly.
The hosted address is only a route to the machine. It is not a credential and does not bypass Nexus authentication. Applications use one of that machine's existing client tokens as the API key.
Provider credentials remain on the managed machine and are never copied into the endpoint configuration.
Turn it on
- Open Fleet and select an online managed machine.
- Expand Connection details.
- Under Access from anywhere, choose Turn on.
- Copy the hosted access address from the confirmation dialog.
- Open Client Tokens and create a dedicated token for the application.
- Configure the application with the hosted address as its Nexus base URL and the client token as its API key.
The same compatible gateway routes, model names, presets, Smart Routes, and Smart Balancer pools available on that machine can be addressed through the hosted URL.
Availability
The machine must remain enrolled, online, and connected to Fleet. If it goes offline, exits its Fleet connection, or loses its endpoint entitlement, the hosted address cannot reach Runtime.
Turning off Access from anywhere stops traffic to that address immediately. Applications configured with it will stop working until they use another available address.
Security and privacy
- Create a separate client token for each application so access can be scoped and revoked independently.
- Treat the hosted address as public information and the client token as the secret.
- Requests and responses travel through the Msty-hosted relay. HTTPS protects traffic in transit, but this is not a local-only data path.
- Use private network access or a trusted VPN instead when your policy does not allow inference traffic through a hosted relay.
- Review browser CORS settings separately when the caller runs in a web page.
See Security before enabling remote access for sensitive or regulated workloads.
Manage several machines
Fleet batch actions can prepare the same change across selected machines, including supported model-engine installs, updates, model downloads, and Nexus updates.
Review eligibility before starting. Work already accepted by a machine continues if you stop launching the remaining batch actions. Follow progress from Activity.
Revoke or erase a machine
Revoking removes the machine from the managed workspace but does not erase its local installation.
Use the explicit erase workflow only when decommissioning a setup-managed Nexus installation. Nexus removes only its own services, settings, history, fleet state, and saved Nexus credentials. Downloaded models are removed only when explicitly selected; external runtimes and external caches remain untouched.