Costs and limits

Zugoid is free, open-source software when you run it on your own infrastructure. A Cloudflare Server runs in your own account, and Cloudflare bills that account directly for what the Server uses. Zugoid does not quote prices; check Cloudflare's current pricing for each product below.

Products a Server uses

Cloudflare bills the optional products by usage, so they matter only once you set them up and use them. A compute node uses paid Containers and Artifacts; the installer asks you to confirm those charges before it provisions one.

Box hours

Each Task an Agent works on gets one container, its box. Containers are billed while they run, so the cost is box hours, not Tasks:

• A box runs while its Agent works and stops after 10 minutes without a turn. A Task waiting for a merge or its next message costs nothing for its container. A turn waiting for your approval of a push or window keeps its box running until you decide or the Run ends.
• At setup you choose a box size (small, standard or large) and how many boxes may run at once (4 by default, at most 64). That number is the container application's max_instances, so it caps how many boxes, and their hours, can add up at the same moment. A Task whose box does not fit waits until one stops.
• Each box keeps its work in its own Artifacts repository, checkpointed when a turn ends. Artifacts are billed for storage and operations; a Task's repository is deleted when the Task is Done.
• Each Run also has its own limits in Server settings → Agents → Execution, including box runtime per Task (six hours by default).

Model Providers you connect, such as OpenRouter, Anthropic or ChatGPT, bill you separately.

Backups take storage

With R2, the Server writes a backup to its backups bucket every week and before each update. Zugoid does not delete old backups, so the backups bucket grows over time. Delete archives you no longer need in the Cloudflare dashboard, and keep at least one recent one. See Backups.

Free and paid Workers plans

A Server can start on a free Cloudflare account. Some limits are tighter on the Workers Free plan:

• Sending email to anyone outside your Cloudflare account needs Workers Paid. This covers Mailboxes and reset and confirmation emails.
• A self-update from Settings runs in one Durable Object alarm. On Workers Free its subrequest budget is tight for releases with large asset changes. If an update stops, use Retry update or run the update through the official installer.
• Cloudflare's daily and per-request quotas for Workers, D1, KV and Durable Objects apply to the whole account. If you run several Servers in one account, they share those quotas.

See Workers limits for the current numbers.

Zugoid limits on Cloudflare

Keep costs predictable

• Give each Server its own Cloudflare account. Usage and quotas then stay separate, and kept access reaches only that Server. A free account is enough unless the Server sends email.
• Enable optional products only when you need them.
• Set usage notifications in your Cloudflare account.
• Prune old backups in the backups bucket.