Dock vs NanoCorp: Specialists or One Business Agent?
Compare Dock and NanoCorp on agent coordination, goal checks, approvals and the different work their plans cover.
Founder, Task Machine
Choosing Dock vs NanoCorp starts with a coordination question: do you need specialists handing work to each other, or one main agent operating a business? Dock's handoff guide describes a Chief of Staff that briefs other agents. NanoCorp's business documentation puts a website and checkout around a business agent.
The deciding difference is who carries the work between jobs. A reporting line helps when research, outreach and operations need separate owners. A business agent with checked goals suits a founder who wants to direct the business through chat, including changes to its site.
Dock organizes specialist handoffs
Dock's handoff guide describes a Chief of Staff that prepares specialists, sets routines and maintains shared knowledge. A handoff makes an agent or person responsible for finishing a task. Agents can escalate decisions through their reporting line.
Its product page describes shared workspaces and an append-only activity log. For a small team dividing research and sales work, that gives the handoff a recorded owner and sequence of actions. Dock also shows agents working toward targets, although its docs do not describe tracked goal metrics beyond progress reported in conversation.
That distinction matters when the weekly question changes from who is doing the outreach to whether the outreach is moving the target. Specialist coordination and outcome measurement answer different questions. You should decide which record your team needs to inspect at the end of a run.
NanoCorp centers the business and its goals
NanoCorp's business documentation describes a website, checkout, repository and main agent for each business. You steer that agent in chat. It runs in an isolated sandbox, and its FAQ says self-hosting or running the project on your own infrastructure is not currently supported.
Its goal overview describes cards containing the intended result, checks, limits and credit allowance. A goal can track a number over time and contains one to five checks. That makes it relevant when a founder wants an explicit result attached to the business agent's work.
The task-list documentation describes a list that people and the agent can edit. Businesses with goals use routines for agent work, however. Its public pages do not establish shared task ownership, task-specific discussion or history, so an editable list should not be treated as the same handoff record Dock describes.
Compare result checks with coordination
Dock says agents inspect their own results, and its routine guide describes a nightly Chief of Staff review that preserves lessons. Its docs do not describe checking delivered work against defined acceptance criteria or tests. A nightly review can help an agent improve its approach without establishing that a particular deliverable met an agreed requirement.
NanoCorp's goal update says failed steps or checks generate work to fix. The distinction is useful for a recurring business objective: you can ask what check failed and what follow-up it created. NanoCorp's published coordination model still centers one main agent, with no documented lead or owner roles across goals, projects and teams.
For a client report, separate the reporting job from its acceptance test. Dock's model lets you hand research and operations work to specialists. NanoCorp's goal checks give you a published mechanism for deciding whether a stated goal result needs more work. Neither product's pages establish a general user-defined process that repeats the same multi-step sequence every time.
Approval boundaries need an account-level check
Dock's permission guide lets you choose Allow, Ask or Deny by action type for each agent. Ask requires permission each time. Its Inbox guide describes conversations needing a decision, including replies you can make without opening the workspace.
NanoCorp's goal update says the agent asks before spending money, messaging people or deleting data. Its connection guide also describes read-only and autopilot account modes, with autopilot able to post, reply or send. These descriptions differ on messaging approval, so confirm the control for each connected account before relying on a general promise.
Both approaches leave you with a concrete evaluation task. For Dock, map an action such as sending outreach to the specialist's permission setting. For NanoCorp, check the account mode and whether the action requires another approval. Its public pages do not establish configurable action approvals collected for review in the same way.
Execution and billing cover different commitments
Dock's cloud-agent guide offers cloud agents and local agents through its Mac app. Cloud work can continue when the laptop is shut. Its model guide limits subscription funding to local agents using supported models. Cloud agents always use Dock usage.
Its pricing page lists Starter at $40, Standard at $100 and Scale at $200 per person per month. The plans include 5, 10 or 20 cloud agents and 10,000, 20,000 or 50,000 business credits respectively. Additional usage or credits can be purchased and roll over. Dock's terms state that it is in beta.
NanoCorp's plan documentation lists Founder from $30 for 30 monthly credits up to $2,000 for 2,000, with rollover. Light costs $4.99 monthly during Founder cancellation and includes no agents or credits. Its withdrawal documentation specifies a 20% withdrawal fee, with possible additional Stripe currency conversion and cross-border fees. The agent allowances, credits and withdrawal charges are different billing units, so the headline payments do not establish which service fits your budget.
Dock and NanoCorp, point by point
The table compares both products against the same questions. Each answer includes its source and check date, including limits on what the public pages establish.
Both columns answer the same questions from each company's public pages. Yes means the company publishes the capability the question asks about, Partly means something narrower, No means it says it does not offer it, and Not published means its public pages do not describe it. Every answer links to its source and shows when we last checked it. The oldest check on this page was November 13, 2026.
| What you compare | Dock | NanoCorp |
|---|---|---|
| Goals |
Dock
Partly
Agents accept goals and delegate parts to specialists, and a channel example shows progress toward a lead target. Its docs do not describe tracked goal metrics beyond conversational progress reports. |
NanoCorp
Yes
A business agent works toward goals, and a goal can track a number over time. Goals have checks for their results. |
| Leads |
Dock
Yes
A Chief of Staff runs work involving several agents, briefs each specialist, sets routines and keeps shared knowledge current. Agents escalate decisions up their reporting line. |
NanoCorp
Partly
Each business has one main agent, and check-ins pick the next useful work. Its pages do not describe lead or owner roles coordinating goals, projects or teams. |
| Tasks |
Dock
Yes
Handoffs transfer responsibility for finishing a task to an agent or a person. An append-only log records who did what and when. |
NanoCorp
Partly
People and the agent can read and edit a shared task list. On businesses with goals, the agent works routines rather than one-off tasks from that list, and shared ownership and task-specific discussion or history are not documented. |
| Recurring work |
Dock
Yes
Agents run hourly, daily, weekly or one-off routines in your timezone. Webhook rules wake specific agents from outside events, with optional batching between check-ins. |
NanoCorp
Partly
Routines run on their own schedules, and check-ins can run up to eight times a day. Its pages do not describe outside events triggering agent work. |
| Workflows |
Dock
Partly
You can split recurring work among specialists and specify handoffs and human decisions. Dock describes agents adapting their steps, rather than a defined multi-step process that runs the same way each time. |
NanoCorp
Partly
Scheduled routines repeat work, and a goal can show steps and checks. Its pages do not describe a user-defined repeatable multi-step process that runs the same way each time. |
| Autonomy |
Dock
Yes
Each agent has Allow, Ask or Deny permissions by action type, with Ask requiring approval every time. The Inbox collects work needing a decision and lets you reply without opening the workspace. |
NanoCorp
Partly
NanoCorp says its agent asks before spending money, messaging people or deleting data. Connected accounts have read-only and autopilot modes, with different published descriptions of messaging approval. Configurable action approvals collected for review are not established. |
| Learned autonomy |
Dock
Not published
Its docs describe manually moving permissions from Ask to Allow and learning your working preferences. They do not describe proposals to change an agent's authority based on your approval history. |
NanoCorp
Not published
Goals can start automatically without approval. NanoCorp's pages do not describe proposing permission changes based on approval history. |
| Memory |
Dock
Yes
Agent memory updates during work and carries standing knowledge into later conversations. You can read, edit or delete entries in the Memory tab. |
NanoCorp
Partly
The agent keeps memory in the business's repository. Its pages do not establish that users can inspect or correct that memory. |
| Planning |
Dock
Partly
The Chief of Staff plans and coordinates work in conversation, and shared docs can hold plans. Its docs do not establish a conversation becoming a plan artifact reviewed before execution. |
NanoCorp
Yes
An agent proposes goals in chat as cards with a result, checks, limits and credit allowance. Some goals can start automatically without approval. |
| Intake |
Dock
Yes
Each connected tool gets a webhook URL, and plain-language rules route events to agents. Channel events can also tag the right person and let an agent pick up work in the thread. |
NanoCorp
Yes
A connected assistant can send messages and attachments to a business agent through NanoCorp's MCP tools. |
| Connectors |
Dock
Yes
The official CLI documents MCP endpoints, API keys and webhook configuration. Incoming webhook rules wake agents from connected services. |
NanoCorp
Yes
Connections supports LinkedIn, Gmail, Notion and over a thousand other apps, with account-level read-only or autopilot modes. NanoCorp also offers an MCP server and an API for custom integrations. |
| Models |
Dock
Partly
You choose a model and reasoning effort for each agent and can switch models in the composer. Its docs do not describe automatic model selection for each task or step. |
NanoCorp
Not published
NanoCorp says users cannot choose which AI model runs their tasks. NanoCorp picks the agent's model, but does not describe automatic selection per task or step. |
| Cloud or your own computer |
Dock
Yes
Choose cloud agents on Dock's machines or local agents through the Mac app. Cloud agents keep working with your laptop shut, while local agents can access your Mac's files and tools. |
NanoCorp
Partly
NanoCorp provides a business website and runs its business agent in an isolated sandbox. Self-hosting NanoCorp or running the project on your own infrastructure is not currently supported. |
| Your own subscription |
Dock
Partly
Connected Claude subscriptions and supported ChatGPT models can fund local agents instead of Dock usage. Cloud agents always use Dock usage, and not every OpenAI model supports subscription funding. |
NanoCorp
Partly
NanoCorp documents a Gemini key for your deployed site and at-your-own-risk overrides of managed providers through Secrets. Its FAQ says Claude and OpenAI API keys are unsupported. |
| Pricing |
Dock
Yes
Starter is $40, Standard $100 and Scale $200 per person per month, including 5, 10 or 20 cloud agents and 10,000, 20,000 or 50,000 business credits. Additional usage or credits can be purchased and roll over. |
NanoCorp
Yes
Founder costs $30 for 30 monthly credits up to $2,000 for 2,000, with rollover and a 20% withdrawal fee. Light costs $4.99 monthly during Founder cancellation and has no agents or credits. |
| Correctness |
Dock
Partly
Dock says agents check their own results, and the Chief of Staff runs a nightly self-review to retain lessons. Its docs do not describe evaluating delivered work against defined criteria or tests. |
NanoCorp
Yes
Goals include one to five checks, and failed goal steps or checks become work to fix. |
A fact we cannot find or cannot check is left out, and prices can change after the date shown. Task Machine publishes this comparison and is an interested party. Dock and NanoCorp are named only to identify them, and there is no relationship between the companies. Has something changed? Tell us.
Who each one suits
Pick Dock if separate business specialists, explicit handoffs and per-agent action permissions fit how your team works. Its honest limit is that published self-review does not establish acceptance checks against defined requirements, and the service remains in beta.
Pick NanoCorp if you want a business agent, website and checkout with goal checks that create follow-up work. Accept its 20% withdrawal fee and resolve the conflicting messaging-approval descriptions before connecting an account that can send messages.
Where Task Machine fits
Task Machine answers the coordination-and-checking decision with owned Tasks and reviews against acceptance requirements. You review the plan first, and delivered work receives a Pass, Fail or Uncertain check for each requirement. Goals can have agent leads and linked Metrics, while Workflows repeat defined steps with branches, approvals and verifier feedback.
Task Machine is the wrong pick if you require a bundled business website and checkout, because its docs do not describe a bundled business website, email address or customer checkout. See Switch from NanoCorp to Task Machine. To evaluate reviewed work records against specialist coordination, read Task Machine vs Dock, then use Task Machine vs NanoCorp to check the business-agent tradeoff for one job you already run each week.