Staging and production

There is no separate "environments" setting to learn, because you already have the right tool: teams. Run a staging team alongside your production team, under the same account.

The pattern

  1. Create a team named, for example, Staging.
  2. Point your staging agents at it using that team's API key.
  3. Route its alerting to a quieter channel, or switch it off.
  4. Leave Evaluate runs off for the staging team.

That last step matters: evaluations are a per-team switch, and teams you create later start with it off. So a staging team consumes none of your account's evaluation allowance unless you deliberately turn it on. Health checks still run, so you keep basic signal without spending evaluations on throwaway runs.

What counts

Teams are unlimited on every plan. Usage from every team, staging included, counts toward your account's limits: events, evaluations, and agents are pooled across the account, not per team.

Unlimited teams on every plan; usage counts toward your account's limits.

One team per client

The same pattern separates clients: one team per client, each with its own API key, its own status page, and its own alert routing, all billed under one account.