---
title: Projects
description: Group monitors and status pages so scoping, permissions and alerting stay manageable as you grow.
sidebar:
  label: Projects
---

{/* Source of truth: packages/shared/src/projects.ts — name, slug,
    description, parentId (nesting). Routes: projects.* incl. addMonitors,
    removeMonitor, reorder, move/copy. Limit: maxProjects in plans.ts. */}

A project groups monitors and status pages. Projects can be **nested** via a
parent, so you can mirror however your systems are actually organised.

## Why they matter

Projects are the unit Glowo scopes other things by. The most valuable use is
[notification channel scoping](/alerting/channels): point an SMS channel at the
"Production" project and every monitor added to that project later is covered
automatically.

Scoping a channel to a list of monitors instead means the list silently goes
stale, and nobody notices until an alert does not arrive.

## Organising

Common structures:

- **By environment** — Production, Staging
- **By product** — Web app, API, Mobile backend
- **By team** — Payments, Identity, Platform
- **By customer** — for agencies or per-tenant deployments

Nesting lets you combine them, for example `Production → Payments`.

Pick the structure that matches how you want to be *alerted*. That is what
projects are load-bearing for; everything else is presentation.

## Managing monitors in a project

- Add monitors to a project, in bulk.
- Remove a monitor from a project — it stays in the workspace.
- Reorder monitors within a project.
- Move a monitor between projects, or copy one.

A monitor can belong to several projects (up to 20), which is useful when a
service is both "Production" and "Payments".

## Projects and status pages

Status pages can also be attached to projects, which keeps a large workspace
navigable. It does not change what the public sees — that is controlled by the
page's [components](/status-pages/components).

:::note
The number of projects is plan-gated. See [Plans and limits](/billing/plans).
:::