Rakazo vs ChatGPT dots: Self-Hosting vs Managed AI Teammates

A common misunderstanding in recent coverage claims: "ChatGPT dots costs $100/month, while Rakazo is completely free." That confuses two separate things. As of October 2, 2026, $100 is the entry-level monthly price for ChatGPT Pro (alongside $200 and $500 tiers). OpenAI's documentation confirms that your first dot is included in eligible Pro or Business Premium plans at no extra charge. Meanwhile, Rakazo's Apache-2.0 open-source license removes software licensing fees, but hosting, model inference tokens, and infrastructure maintenance still carry real costs. The real engineering question is: Do you want an agent running inside a fully managed cloud sandbox, or do you want to own and maintain the runtime environment yourself?

Draft a persistent task spec first

Before choosing an infrastructure path, define what the agent is actually supposed to do. Take a common engineering routine: checking an upstream repository's release notes every weekday morning and summarizing breaking changes with source URLs. Open two standard chat prompts.

In Prompt A (Drafting): "Draft a structured task card for checking project updates every weekday morning. Specify trigger time, exact source URLs, comparison logic, output format, and mandatory pause conditions. Do not run any commands or access external tools."

In Prompt B (Auditing): "Review this task card for edge cases. What happens on day one when no baseline exists? How does the agent distinguish a transient network timeout from 'no updates found'? Update the card with strict safety boundaries."

You end up with a verified task contract:

• Trigger: Weekdays at 09:00 (explicit timezone).
• Scope: Canonical documentation & release feeds only.
• Baseline: Compare against the previous successful run state.
• Output: Maximum 3 validated items with publication timestamps and direct URLs.
• Circuit Breakers: Halt immediately if encountering authentication walls, CAPTCHAs, contradictory data, or write actions.

Core takeaway: Before spinning up an autonomous daemon, write down when it triggers, what it inspects, what it delivers, and where human approval is strictly required.

Architectural trade-offs: dots vs Rakazo

Dimension	ChatGPT dots (Managed)	Rakazo (Self-Hosted)
Runtime & Sandbox	Managed cloud computer & browser provided by OpenAI	Managed by you (local Docker, VPS, E2B, Daytona, Box)
Model Selection	GPT-6 Astra within ChatGPT ecosystem	Any model provider via Pi / OpenAI-compatible APIs
Integrations	4,000+ plugins via ChatGPT catalog	Composio, Pipedream Connect, MCP servers, OpenAPI
Cost Mechanics	Bundled in Pro/Business Premium tiers (subject to usage caps)	Base server hosting + variable model inference tokens
Data Boundary	Managed within OpenAI infrastructure	Host server is self-controlled; remote model calls still transit external APIs

Self-hosting

Rakazo gives you complete control over your bot profiles, schedules, and desktop environments, but calling third-party commercial LLMs still transfers prompt payloads over external networks.

Cost & approval models

"24/7 always-on" does not mean unlimited deep inference. ChatGPT dots operates under account-level work limits. With Rakazo, your total cost equation is:

Monthly Cost = VPS Hosting + Model API Invocations + External Sandbox Services + Maintenance Time

On permissions: OpenAI enforces approval gates for financial transactions and password management. Rakazo's verification test suite confirms that destructive computer actions wait for approval before executing once.

What not to do right now

If you choose to experiment with Rakazo's quick-start script:

mkdir -p rakazo && cd rakazo && curl -fsSLO https://raw.githubusercontent.com/elie222/rakazo/main/infra/compose/install-images.sh && bash install-images.sh

Hold off on these steps initially:

• Do not immediately link production Slack channels or primary email accounts.
• Do not automate outward communication without human-in-the-loop review.

Run the release-check routine for 3 consecutive days on public data. Verify that URLs resolve, false positives are eliminated, and failures are reported accurately before putting persistent bots into production workflows.