Ways to run Nethür

Browser, desktop, a team server, SSH or a cloud VM — pick where the agents run.

Nethür separates the workspace from the machine that runs it. Agents, terminals and git live on a server; the browser, desktop app and phone are clients. You can move between clients without moving the work.

At a glance

ModeWhere agents runBest for
BrowserAn existing serverJoining a team, working from any device
Desktop (local)The computer in front of youSolo work, fastest setup, offline-friendly
Team serverA VPS, home server or office machineShared projects, always-on agents, mobile
SSH targetA remote host with your repo and toolsGPU boxes, build machines, existing infra
Cloud VMA disposable VM or sandbox you controlIsolated experiments, per-workspace compute

Nethür charges per seat, not per server. You bring the machine and your own AI subscriptions; Nethür does not resell model access.

1. Browser

Sign in at nethur.com, pick a server and work. The server keeps running when you close the tab, so agents continue and you can return from another device.

This is the default for teams. The browser has the full surface: chat, terminal, editor, source control, browser, tasks, notes, contents and team chat.

2. Desktop app, local server

Install the desktop app, start the local server and use Nethür without a separate host. The app shows the same web client in a native window and can host the server in the background.

This is the easiest solo setup. It also works offline for local repos, although agents still need network access to reach their providers.

3. Team server

Run the server on a machine that stays online: a VPS, a home server, a Mac mini or an office box. Team members connect from the browser or the desktop app, each with their own account.

The server owns:

  • projects and workspaces,
  • agent processes and terminals,
  • provider accounts and their usage,
  • team chat, notes and contents.

See Remote servers for pairing, access and updates.

4. SSH target

Keep Nethür's server where it is and run selected workspaces on another machine over SSH. Agents and git worktree run on the remote; the UI stays with you.

Use this when the remote already has the repo, credentials and toolchain. Ports, remote terminals and file transfer are covered in SSH workspaces.

5. Cloud VM / per-workspace environment

A recipe in nethur.yaml can create a disposable environment for a workspace — a cloud sandbox, VM or local container. Nethür is the wrapper; your provider account and billing stay yours.