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

How projects work

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

1. Open the project dropdown

   Click the project dropdown at the top-left of the screen.

2. Create the project

   Click Create a new project +.

3. Name it

   Give the project a descriptive name in project settings.

4. Bring in your team

   Invite teammates and set up notification channels for the new project.

What belongs to a 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

Next steps