Managed Cloud Agents

Managed Cloud Agents run a dedicated Hermes agent on cloud compute so it can keep working when your laptop, desktop, and other personal machines are off. Each agent has its own persistent workspace, a stable endpoint, managed model access, and start/stop controls in HivemindOS.

Open More → Cloud Agents to deploy and operate them.

What You Get

• a dedicated Hermes runtime on cloud compute
• a persistent workspace that survives compute replacement
• browser chat from the HivemindOS dashboard
• server-metered running and stopped rates
• automatic compute shutdown when managed credit runs out
• one-click funding from an eligible governed Base wallet
• start, stop, health, and permanent-delete controls
• optional Tailnet enrollment that survives compute replacement
• optional Shared Brain pairing with an authorized Syncthing peer
• cloud-hosted remote MCP connections that remain available while personal machines are off

The initial deployment usually takes a few minutes while the pinned runtime image is installed. Starting a stopped agent recreates compute around the same workspace and may take a similar amount of time.

App Builder Projects

An existing running Managed Cloud Agent can own app projects in its retained workspace. HivemindOS uses the same project contract and reviewed starter for local and managed building, while the managed service remains authoritative for account and agent ownership.

The initial managed App Builder slice creates, lists, and reads stopped project workspaces. App execution and public previews are not enabled until the managed container lifecycle and resource-limit checks are complete. Users who do not need always-on cloud execution can build and preview through a local or fleet machine without managed credits.

Hivemind Cloud Plans

Hivemind Cloud separates the managed control-plane subscription from metered infrastructure. This keeps pricing aligned when one person operates many agents.

Cloud Pro and Cloud Team prices are launch hypotheses being validated with design partners. A plan shown as design-partner or contact-led is not a self-serve entitlement.

Metered Agent Sizes

Agent runtime, model, tool, hosted-app, and API usage is billed separately from the control-plane subscription. Current prices are always loaded from the managed service; rebuilding or editing the downloaded app cannot change official rates, recipients, balances, or resource entitlements.

Funding And Wallet Safety

Funding uses Base USDC. The managed service issues the amount, network, USDC contract, recipient, expiry, and quote identifier. HivemindOS verifies those requirements before asking the selected local wallet to sign.

The selected wallet still enforces its normal controls:

• spend must be enabled
• the wallet must use local custody on Base
• the top-up must fit the per-payment cap
• wallet daily and monthly budgets still apply
• company budgets and freeze switches additionally apply only when the top-up belongs to an active company Work Board task
• approval thresholds still pause the payment when required
• the same onchain transaction cannot be credited twice

The hosted account credential is encrypted in the local HivemindOS vault. Model provider keys, infrastructure credentials, official payment policy, and hosted runtime credentials are not shipped in the app.

Stop, Start, And Persistence

Stop deletes the compute instance while retaining the persistent workspace, stable address, firewall, Tailnet state, and cloud copy of the Shared Brain. The account moves to the lower stopped rate.

Start creates fresh compute, attaches the same workspace, and starts Hermes again. Files, runtime configuration, and Hermes state stored in the managed workspace remain available.

Delete removes both compute and the persistent workspace. This cannot be undone.

Integrations When Personal Machines Are Off

An integration only stays available when the service that owns it is still running:

HivemindOS does not silently copy existing OAuth tokens, MCP configuration, Shared Brain contents, or Tailnet access from a laptop into the cloud. Those remain separate trust decisions. In Cloud Agents, you can explicitly connect a reusable or ephemeral Tailscale credential, pair the Shared Brain with the local Syncthing peer, or add an HTTPS remote MCP. Hosted integration secrets are encrypted by the managed service. The bootstrap credential and Tailscale enrollment credential are cleared after use; only the resulting Tailnet identity remains on the agent’s retained Volume.

Machine-bound capabilities stay tied to the machine that owns them. Connecting the cloud agent to your Tailnet lets it reach an online machine; it does not make an offline Mac’s filesystem, browser, or local MCP process continue running.

This distinction prevents a cloud agent from pretending it can use an offline Mac and prevents local secrets from being uploaded without an explicit setup step.

Open-Source Boundary

Local, bring-your-own-key, and self-hosted HivemindOS remain available without managed credits. The public app contains the client, UI, wallet-policy checks, and self-hosted-compatible contract. Official balances, payment settlement, prices, metering, resource ownership, provider secrets, and cloud entitlements are enforced by HivemindOS-managed infrastructure.