NexusDock Cloud · Managed SaaS for AgentDock

Your AgentDock fleet.
One cloud control plane.

Sign in, pair your devices, and bring Recall, Workflows, live Runtime and MCP into one hosted workspace. NexusDock Cloud runs the control plane so you do not have to.

No Nexus server to deploy Outbound-only device connections Execution stays on your devices
cloud.nexusdock
U
Personal workspace

Good evening

Plus
Devices online3All connected
Recall148documents
Workflows5reusable templates
Device statusView all
M
Mac minimacOS · AgentDock
Online
W
Work PCWindows · AgentDock
Online
L
ServerLinux · AgentDock
Online
Managed cloud control plane Local execution Unified MCP access Mac · Windows · Linux
01 / Cloud

The shared layer lives in Cloud.
The work still runs where it should.

NexusDock Cloud hosts identity, your personal workspace, shared Recall and control state. AgentDock keeps machine-local execution on each device and connects outward to Cloud.

Web consoleYour browser
MCPAI clients
HTTPS / MCP
DevicesRecallWorkflowsRuntimeMCP
Outbound WebSocket connections
AgentDockmacOS
AgentDockWindows
AgentDockLinux
01

No control-plane ops

No Nexus container, database, reverse proxy or TLS stack to maintain before you can pair a device.

02

Execution stays local

Commands, files, browser automation and machine-local tools continue to run on the AgentDock device that owns them.

03

One personal workspace

Sign in and your workspace is ready. Devices, MCP access and shared state stay attached to your verified account.

02 / Product

Everything your AgentDock fleet shares.
Without duplicating the runtime.

01

Devices

Pair AgentDock on macOS, Windows and Linux with a short-lived code, then see connection state and manage devices from one account.

Mac miniWork PCServer
02

Recall

Keep shared searchable memory in Cloud. Agents write through MCP while the web console gives you a focused place to browse and search it.

project.mdrunbooks/decisions/
03

Workflows

On Plus, publish, version and reuse proven Workflow templates so recurring operations start from a known process instead of a blank prompt.

check→execute→verify
04

Live Runtime

Inspect node-local Tasks, Skills, Plugins, dynamic MCP servers and diagnostics live. Cloud routes the view without pretending to own the device runtime.

Tasks 4Skills 18MCP 6
05

One MCP endpoint

Authorize compatible AI clients once, then reach NexusDock tools and capabilities from your connected AgentDock devices through one Cloud MCP endpoint.

/mcp→NexusDock Cloud
03 / Start

From account to connected device.
Three steps.

Cloud removes the server setup from the path. Create your account, pair AgentDock, then use the web console or connect an MCP client.

01
@

Sign in

Use email verification, GitHub or Google. Your personal workspace is provisioned automatically.

02
#

Pair AgentDock

Create a short-lived pairing code in Cloud and run the generated command on the AgentDock machine.

03
⌁

Use Cloud or MCP

Manage devices in the web console and authorize AI clients against one NexusDock Cloud MCP endpoint.

04 / Plans

Start simple.
Grow when your fleet does.

NexusDock Cloud has a Free plan for getting started and Plus for more capacity and reusable Workflow templates. Current limits are always shown inside Cloud.

For getting started

Free

Free

A personal Cloud workspace with the core device and Recall experience.

  • Personal workspace
  • Core device management
  • Recall access
  • Cloud MCP endpoint
Explore Free →

Prefer to run the control plane yourself? The open-source NexusDock self-hosted edition remains available separately.

NexusDock Cloud

Your devices stay yours.
The shared layer becomes effortless.

Use Cloud as the hosted home for your AgentDock fleet, or choose the open-source self-hosted edition when you want to operate the control plane yourself.