Project setup
Organize your monitoring, status pages, and team access into separate workspaces.
Projects are the top-level containers in Hyperping. Every monitor, status page, teammate invitation, maintenance window, and API token belongs to a specific project. This means you can run completely separate monitoring setups from a single Hyperping account, each with its own team members and notification channels.
Projects are useful when:
- You manage multiple clients and want to keep their monitoring isolated
- Different teams in your organization need their own dashboards and alerts
- You want to separate production and staging environments
- You need project-level access control so teammates only see what they should
The project dropdown lets you switch between projects and create new ones.
How projects work
Usage, including the number of monitors and teammates, is counted at the account level. You can create unlimited projects within a single account, and your plan limits apply across all of them.
When you sign up for Hyperping, a default project called Untitled project is created automatically. You can rename it in your project settings.
Create a new project
- Click the project dropdown at the top-left of the screen.
- Click Create a new project +.
- Give the project a descriptive name in project settings.
- Invite teammates and set up notification channels for the new project.
What belongs to a project
| Resource | Scope |
|---|---|
| Monitors | Created and managed per project |
| Status pages | Tied to a single project |
| Teammates | Invited per project, only see that project |
| Notification channels | Configured per project |
| Escalation policies | Defined per project |
| API tokens | Scoped to a single project |
| Maintenance windows | Scheduled per project |
Common project structures
By client: Agencies and MSPs create one project per client. Each client's team only sees their own monitors and status page.
By team: Larger organizations split projects by team (infrastructure, backend, frontend) so each group manages their own alerts independently.
By environment: Separate production monitoring from staging to avoid alert noise from non-critical environments.
Troubleshooting
I created a monitor in the wrong project.
Monitors cannot be moved between projects. Delete the monitor and recreate it in the correct project.
My teammate cannot see a project.
Teammates only have access to projects they were explicitly invited to. Switch to the correct project and invite them from the Teammates page.
I want to rename or delete a project.
Go to project settings to rename a project. Only the account Owner can delete a project, and doing so removes all monitors and data within it.
