Zeroko CloudPlans
Zeroko Cloud

Plans

What each plan gives a workspace, and what happens at its limits.

PlanPriceServicesRequests a monthStorage
Free0 €310,0001 GBSleeps when idle
Hobby6 € a month10100,0005 GB
Pro12 € a month201,000,00010 GBCustom domains, soon
Team20 € a member a month505,000,00025 GBMembers and roles

Free, Hobby and Pro are for a workspace of your own; Team is for a team. One workspace on Free each. Every plan has every binding, the skill, logs, versions and rollback. See Pricing.

At the limits

  • Rate: each client (by its address) may make 10 requests a second to each service on Free, 25 on Hobby, 50 on Pro and 100 on Team, with bursts of twice as many; past it, 429 with Retry-After. A service can set a lower rate of its own (PATCH /api/services/<name> {"rate_limit": n}).
  • Services: making one past the plan's number answers 403 with plan_limit. Delete one, or move to a bigger plan.
  • Storage: the plan's storage is shared among as many services as it allows: on Free, 341 MB each (1 GB over 3). A service can't be given more than its share.
  • Requests: past the plan's requests in a calendar month (UTC), the workspace's services answer 429 until the month ends. Zeroko never charges for more.
  • Sleeping: on Free, the workspace's runner stops after 15 minutes without a request, and the next request starts it again, in under a second. Paid plans stay up.

Each workspace's runner also has the plan's memory and CPUs, and its services the runner's own limits per service: see Limits. Settings shows the plan's limits and this month's requests.

Changing plans

In Billing, the workspace's owner changes its plan whenever they like:

  • Up: at once. Paid plans go through checkout (Polar) the first time, and are prorated after.
  • Down: once the workspace fits in the smaller plan. Its services and data stay as they are when the plan changes, so delete what's too much first; the panel says what.
  • Back to Free: the paid plan runs to the end of its month, and can be kept until then.

If a payment stops, the workspace goes to Free. If it's too big for Free, its services pause (they answer 503, their data kept) until it fits, or until it's paid for again; the panel and the API keep working, to make it fit.