Plans and limits
Three plans, and what each one counts. Sessions are never counted. Go over a limit and nothing is lost.
WatchThe three plans #
| Seed | Grove | Orchard | |
|---|---|---|---|
| Price | $0 | $8 a month | $24 a month |
| Environments | 1 | 5 | 25 |
| Machines | 1 | 5 | 25 |
| Extra environments | Not available | $2 a month each | $2 a month each |
| Shortest heartbeat | 5 minutes | 1 minute | 1 minute |
| Concurrent sessions | Unlimited | Unlimited | Unlimited |
| History | 7 days | 30 days | 90 days |
| Alert channels | Email and 1 webhook | Email, webhooks, push, Slack | Email, webhooks, push, Slack, SMS |
| Alert destinations | 1 | 5 | Unlimited |
| Members | 1 | 1 | 10 |
| Console charts | Not included | Included | Included |
| Read API and SDKs | Not included | Not included | Included |
| Audit trail export | Not included | Not included | Included |
| Support | Community | Priority email |
"Unlimited" sessions means fair use: run as many as your box can hold.
An environment is one agent login running one agent server. A box with a login for each of three clients is three environments on one machine.
The open-source tools on the box are free on every plan and with no plan at all. nucleate, nucleated and the box recipe never check what you pay.
What the limits are for #
Sessions are not limited, on any plan, because a session costs Watch almost nothing: a handful of small messages. Capping them would punish exactly the use Nucarium exists for.
The limits sit on what costs something to run: how often boxes report, how long history is kept, how many alerts are sent and by which channel, and support.
Seed is a real plan, not a trial. One environment on one machine is enough to stop one box wasting your nights. Its slower heartbeat means a dead box takes about 15 minutes to alert where a paid plan takes about 10.
What happens over a limit #
Suppose you are on Seed and add a second agent login to your box. Its heartbeats name two environments, and your plan shows one.
Nothing is rejected and nothing is lost. Watch accepts and stores what the second environment sends, exactly as it does for the first. What changes is what you see:
- The extra environment is hidden. It is listed by name, so you know it is there, with nothing else shown.
- It is never alerted on.
- The account page says how many environments are hidden.
The first environments to report keep showing; the newest ones are the ones hidden. Upgrade, or delete an environment you no longer use, and the hidden one appears with its state intact, as if it had been there all along.
The reason for hiding instead of refusing: if Watch threw away data from an account that had gone over, moving down a plan would look exactly like a box failing. You would get a "down" alert for a machine that was fine. Nothing in Watch should be able to do that.
Other limits are plainer, because nothing is at stake when they are hit:
| Limit | At the limit |
|---|---|
| Machines | The console will not add another, and says what your plan allows. |
| Alert destinations | The console will not add another. |
| History | Ended sessions and fired alerts older than your plan's window are removed. |
| Shortest heartbeat | A deadline shorter than your plan allows is refused, with the allowed range. |
Change plan, or leave #
Your plan is on the account page in the console.
Moving up takes effect at once: hidden environments appear and the faster heartbeat starts at the next report. Moving down does too: deadlines that your new plan does not allow move to the nearest value it does, and environments beyond the new limit are hidden, not deleted.
Deleting your account deletes every machine, environment, session, token, alert destination and alert it owns. The console asks you to confirm, because it cannot be undone. What leaves the box has the detail.