Plans and limits

What each plan includes, what counts against it, and how usage is measured.

Every organization is on a plan, and the plan sets how much it can hold at once. An organization's departments share its plan: the limits below are for the main organization and all of its departments together.

Your organization's current plan, and what it is using, are under Settings. An owner changes the plan there.

What counts

• Apps: every app, including each part of a one-click install and the Develop section's workspace.
• CPU and memory: what every running copy of every app reserves, with its extra processes and sidecars, and every database. A stopped app gives its CPU and memory back.
• Storage: every app's disk and every database's, including while stopped, because the disk is just as full.
• Wherever it runs: apps on your own servers count the same as on CloudJod's.

A change that would go over a limit is refused before anything is made, with a message saying which limit, and whether it was the plan's or a department's own cap. Notifications tell you when you are close to a limit and when you reach it.

How usage is measured

• Reserved, not observed. An app is measured by the CPU and memory it holds, not by how busy it is, because what it holds is what nobody else can use. Two copies of 250 millicores use 500 millicores for every second they run, busy or idle.
• Only while running. A stopped app, or one that never started, uses nothing but its storage.
• Builds are measured for as long as they run, whether they succeed or fail.
• Traffic is what your apps send out to the internet.
• The free plan is never charged, whatever it uses; it is held to its limits instead.