Team · Available on Team

Monitors that belong to the team, not to one person's login.

Organizations with Owner/Admin/Member roles — Team tier adds up to 5 seats so on-call is a shared responsibility, not one person's alone.

Start Free → See pricing

Free forever plan, no card required.

Why it matters

Team workspaces

When monitoring lives in one person's personal account, it leaves with them — literally, or just when they're on vacation and nobody else has access. Organization-owned monitors, contacts and status pages mean the team keeps working when one person is out. It's an easy trap to fall into: someone sets up the first monitor to solve an immediate problem, it works, and eighteen months later half your critical infrastructure is being watched by an account only one person can log into. Then that person changes jobs, or is just asleep during an outage, and nobody else even knows where to look. Structuring monitoring around the organization instead of an individual login means access, alert contacts and status pages all survive personnel changes instead of quietly becoming a single point of failure themselves. It's the organizational equivalent of a single point of failure hiding in plain sight, right up until it isn't hypothetical anymore. The fix is cheap and easy to do early — set it up as an organization from the start — and expensive to untangle later once everything's tied to one login.

Role-based access

Owner, Admin and Member roles control who can change monitors, contacts and billing. That means a new teammate can be given enough access to actually help — checking on a status page, seeing incident history — without also being handed the ability to delete a monitor or touch the billing plan on day one. It's the same principle behind least-privilege access anywhere else in your stack, just applied to monitoring. It's the same reason most software with any real stakes offers role-based permissions instead of an all-or-nothing account.

Invite your team

Up to 5 seats on Team tier, with a clean invite flow — no shared logins or password spreadsheets. Everyone gets their own login, their own two-factor authentication, and their own audit trail of what they changed, instead of a single shared password getting passed around in a message nobody can find later. It scales the way an actual team does — by adding people, not by handing out more copies of one password. It's designed to make onboarding a new teammate a five-minute task, not a security compromise.

Nothing is siloed

Monitors, contacts and status pages belong to the organization, not to any one individual account. When someone leaves the team, none of that has to be recreated or handed off manually — it was never tied to their login in the first place, so the org just keeps running exactly as it was. It's what makes the organization, not any single login, the thing your monitoring setup is actually built around. It's a small structural choice that quietly prevents a much bigger problem down the line.

FAQ

Team workspaces, answered.

How many teammates can I add?

Team tier includes up to 5 seats on one organization. Free and Starter are single-seat plans, so once more than one person needs access, Team tier is the one to use. Each seat gets a full login with its own role, not a shared account split across multiple people. That's a deliberate line — Team tier exists specifically for the moment a monitoring setup stops being one person's responsibility. That's plenty of room for most small teams sharing on-call duty.

Do teammates share a login?

No — each teammate is invited individually and given a role (Owner, Admin or Member) that controls what they can change, so nobody needs a shared password just to check on a monitor. That also means each teammate can enable their own two-factor authentication, and losing access for one person doesn't lock out the rest of the team. It also means an audit of who changed what is always attributable to an actual person. It's built the way any modern team tool should be, not like an account everyone has to remember one password for.

What happens to monitors if someone with access leaves?

Nothing — because monitors, contacts and status pages belong to the organization, not to the individual who created them, removing a teammate's access doesn't touch anything they set up. An Owner or Admin simply removes their seat, and every monitor keeps running exactly as it was. It's one of the clearest arguments for organization-owned monitoring over an individual account in the first place. It's one less thing to worry about when someone's role on the team changes.

Get Started

Team workspaces. Free, starting now.

Start Free →