NanoCorp vs Rakazo: Business Goals or Persistent Bots?
Compare NanoCorp's business agent with Rakazo's persistent bots on goals, event-driven routines, permissions, memory and pricing.
Founder, Task Machine
NanoCorp and Rakazo diverge on what you are putting an agent in charge of: an online business with goals and checkout, or a persistent bot with a job, memory and routines. Start by deciding whether you need the business environment provided or want to configure bots around work you already do.
A founder launching a site has a different review problem from a builder maintaining an inbox-triage bot. The founder needs to judge whether a business goal reached its result. The builder needs to inspect triggers, permissions and the notes a bot carries from one conversation to the next.
NanoCorp packages the business with its agent
NanoCorp's business guide describes one main agent for a business, with a website, checkout and repository. You steer it in chat, and it can make, check and publish changes to the site. Existing code can be imported as a one-time copy.
Its goal description gives goals a result and checks, and goals can track a number over time. Proposed goal cards include limits and a credit allowance. Failed steps or checks become work for the agent to fix, which gives a founder a concrete result to inspect.
This package also has boundaries. NanoCorp's documentation says running the project on your own infrastructure or self-hosting the service is not currently supported. Repository access is available on plans from $120 a month, a relevant threshold if inspecting or exporting source is part of your launch criteria.
Rakazo gives bots a continuing working context
Rakazo's bot guide describes persistent conversations, instructions and bot jobs. Its memory documentation lets you read, edit, download and delete notes, alongside shared space memory. That suits work where a bot's remembered instructions need regular inspection.
A bot can organize other bots and schedule their work. The optional Labs ticket board adds owners, priorities, comments and status changes shared with you, and assigning a ticket to a bot starts work. Check that optional board as part of evaluating your own workflow.
Rakazo's public docs do not describe an owned goal with measurable targets and progress tracking. A bot's ongoing job and a routine's history provide a different kind of record from NanoCorp's goal checks. Choose the record that matches the decision you need to make at the end of the work.
Match the trigger to the recurring job
NanoCorp's command-line documentation describes scheduled routines. Its published recurring-work description also permits check-ins up to eight times a day, but does not describe outside events triggering agent work. A business routine can be scheduled without establishing that an incoming service event wakes it.
Rakazo's routine documentation supports schedules, webhooks, GitHub events, email and Slack messages, with a run history for each routine. Connection and sender restrictions apply to message-based triggers. This is a concrete difference if your job must begin when a message arrives.
For a daily research summary, either published schedule mechanism may be relevant. For a response to an outside event, inspect Rakazo's trigger and sender configuration. In both cases, avoid equating recurring prompts with a defined multi-step workflow: neither product's cited workflow description establishes an enforced process with branches and conditions.
Inspect permissions and remembered instructions together
NanoCorp's connection guide offers account-level read-only and autopilot modes. Its update says the agent asks before spending money, messaging people or deleting data, while the connection documentation also describes autopilot posting, replying and sending. Those differing descriptions mean you should confirm messaging behavior for the actual account you connect.
Rakazo's approval guide describes Ask, Auto and Never ask, editable Allow and Block lists, and cards in chat. Auto judges actions against your request. The routine guide warns that Always allow on a broad tool such as a shell or browser lets outside text use it freely in routines.
Memory is another inspection boundary. NanoCorp keeps memory in the business repository, but its public pages do not establish user inspection or correction of that memory. Rakazo publishes editable notes, although bots keep at most 4 KB in MEMORY.md and merge or remove notes to make room. Optional services or manual additions can extend that arrangement.
Price the package you will actually use
NanoCorp's plan documentation lists Founder from $30 for 30 monthly credits up to $2,000 for 2,000, with rollover. Its withdrawal documentation specifies a 20% fee on each withdrawal, with possible additional Stripe conversion and cross-border fees. The $4.99 monthly Light offer during Founder cancellation excludes agents and credits.
Rakazo's pricing page lists free self-hosting, hosted own-model plans from $15 a month or $12 a month billed yearly, and credits starting at $20 a month. Credits fund model use at provider prices and computer hours. Monthly credits expire at renewal while added credits do not.
The hosting choice is separate from the model connection. Rakazo supports provider API keys, recommends Anthropic API keys for Claude and warns against Claude consumer subscription credentials for its model connection. Its public overview calls Cloud beta even though the pricing page sells hosted plans, so confirm that status for your intended deployment.
NanoCorp and Rakazo, point by point
This table presents both products' answers to the same questions, with sources and individual check dates. Read the justifications alongside the labels to distinguish goal checks from bot procedures.
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 | NanoCorp | Rakazo |
|---|---|---|
| Goals |
NanoCorp
Yes
A business agent works toward goals, and a goal can track a number over time. Goals have checks for their results. |
Rakazo
Partly
You give each persistent bot its job in chat and can schedule recurring work. Its docs do not describe an owned goal with measurable targets and progress tracking. |
| Leads |
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. |
Rakazo
Partly
A bot can organize other bots, rewrite their instructions and schedule their work. Its docs do not describe a project, goal or team lead responsible for reviewing progress. |
| Tasks |
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. |
Rakazo
Yes
The Labs ticket board is shared by you and your bots, with owners, priorities, comments and status changes. Assigning a ticket to a bot starts its work. |
| Recurring work |
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. |
Rakazo
Yes
Routines run on schedules, webhooks, GitHub events, email or Slack messages, and can watch for changes. Each routine keeps a run history. |
| Workflows |
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. |
Rakazo
Partly
Skills save written steps for bots to repeat, and routines run prompts on triggers. Its docs do not describe an enforced multi-step process with branches and conditions. |
| Autonomy |
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. |
Rakazo
Yes
Ask, Auto and Never ask modes control actions, with editable Allow and Block lists. Approval cards collect requests in chat, and Auto checks actions against what you requested. |
| Learned autonomy |
NanoCorp
Not published
Goals can start automatically without approval. NanoCorp's pages do not describe proposing permission changes based on approval history. |
Rakazo
Not published
Its docs do not describe proposing permission changes from your approval history. Always allow is a choice you make on an approval card, while Auto judges actions against your request. |
| Memory |
NanoCorp
Partly
The agent keeps memory in the business's repository. Its pages do not establish that users can inspect or correct that memory. |
Rakazo
Yes
Bots keep persistent notes and shared space memory. You can read, edit, download or delete notes, and optionally connect services for recall by meaning. |
| Planning |
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. |
Rakazo
Partly
Each bot has a continuous chat and an editable Open work list. Its docs do not describe turning a planning conversation into a reviewed execution plan before work starts. |
| Intake |
NanoCorp
Yes
A connected assistant can send messages and attachments to a business agent through NanoCorp's MCP tools. |
Rakazo
Yes
A webhook URL and key route an outside POST request to a bot's routine. Email and Slack messages can also start routines, subject to connection and sender restrictions. |
| Connectors |
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. |
Rakazo
Yes
The app catalog supports custom remote MCP servers, OpenAPI and GraphQL connections. Routines accept webhooks and GitHub events, while self-hosted catalog availability depends on server configuration. |
| Models |
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. |
Rakazo
Partly
You choose a main model, per-bot or per-routine overrides, and ordered fallbacks for failures or limits. Its docs do not describe automatic model selection by task. |
| Cloud or your own computer |
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. |
Rakazo
Yes
Rakazo offers hosted computers and self-hosting on your server or computer. The desktop app can run Rakazo locally or connect bots to your own computer for commands and files. |
| Your own subscription |
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. |
Rakazo
Yes
You can connect provider API keys or sign in with an eligible ChatGPT plan's Codex allowance. Rakazo recommends Anthropic API keys for Claude and warns against using Claude consumer subscription credentials for its model connection. |
| Pricing |
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. |
Rakazo
Yes
Self-hosting is free. Hosted own-model plans start at $15 a month, or $12 a month billed yearly. Rakazo credits start at $20 a month for model usage at provider prices and computer hours. |
| Correctness |
NanoCorp
Yes
Goals include one to five checks, and failed goal steps or checks become work to fix. |
Rakazo
Partly
A skill taught by demonstration includes what to check, and Test runs it once. Its docs do not describe a general system that scores delivered results against defined acceptance criteria. |
For software work
| What you compare | NanoCorp | Rakazo |
|---|---|---|
| Code review rules |
NanoCorp
Not published
NanoCorp maintains business code repositories and supports collaborators. Its pages do not describe automated review against discovered repository rules. |
Rakazo
Partly
Rakazo publishes a pull-request review bot template and lets you edit bot instructions. Its docs do not establish code review against repository rules. |
| Adversarial review |
NanoCorp
Not published
NanoCorp checks site changes before publishing. Its pages do not describe independent adversarial reviewers for high-risk changes. |
Rakazo
Not published
Its docs do not describe an independent second review of risky code changes. The README says bots can check each other, and groups can use parallel helpers, without specifying that review process. |
| Risk rating |
NanoCorp
Not published
NanoCorp provides access to business code on qualifying plans. Its pages do not describe rating merge risk for an exact revision. |
Rakazo
Not published
Its public pages do not describe rating a change's risk before merge. The GitHub catalog lists pull-request inspection and merge actions, rather than a risk assessment. |
| Pull requests |
NanoCorp
Partly
Collaborators can open pull requests in the business repository on plans from $120 a month. Its pages do not describe agents working on pull requests and addressing review feedback. |
Rakazo
Partly
The GitHub catalog includes creating pull requests, reading reviews and replying to review comments. Its docs do not establish an agent delivery loop that revises code in response to review feedback. |
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. NanoCorp and Rakazo are named only to identify them, and there is no relationship between the companies. Has something changed? Tell us.
Who each one suits
Pick NanoCorp if a provided website, checkout and business agent working toward checked goals fit your experiment. Accept the withdrawal fee and confirm the repository-access tier before relying on code export.
Pick Rakazo if persistent bot conversations, editable memory and event-started routines are your primary requirements. Its docs do not establish general acceptance scoring of delivered results, and its Cloud overview uses a beta label.
Where Task Machine fits
Task Machine connects measurable Goals to Tasks and repeatable Workflows, with plan review before execution and acceptance checks before human review. Its Goals documentation describes leads monitoring linked Metrics and proposing missing work. That fits a founder who wants the outcome and the individual reviewed jobs connected.
Task Machine is the wrong pick if you need free application self-hosting, since its docs do not describe a free, open-source self-hosted application. See Switch from Rakazo to Task Machine. Compare Task Machine vs NanoCorp and Task Machine vs Rakazo for that boundary. Select one event-driven job and write down its trigger, permission and acceptance requirement before checking the two comparisons.