What ZnowPulse does
ZnowPulse is a managed monitoring service. Monitors check individual endpoints; Nexus Points combine those checks into a service-level signal. Alerts tell your team when something changes, incidents record the response, and public status pages communicate availability to customers.
A monitor and an endpoint refer to the same monitored resource in the app. A group organizes monitors. An organization holds your monitors, members, alert routes, settings, and subscription.
Set up your workspace
- Create an account with email and password, then complete the email verification flow shown on screen. Google and GitHub signup are currently unavailable. If registrations are temporarily unavailable, follow the website's availability message.
- Sign in and open the dashboard. Check the selected organization before creating resources or changing settings.
- Open Settings to review your account and display timezone. Preferences apply to you; organization settings affect your workspace.
Already invited? Open the invitation link from your organization and finish the acceptance flow using the invited email address. See teams and account access.
Add your first monitor
- Open the dashboard's add-monitor control and give the monitor a recognizable name, such as “Production API”.
- Select HTTP / HTTPS endpoint and enter a complete public URL, such as
https://example.com/health. Replace this example with an endpoint you control. - Choose a check interval allowed by your plan. Free checks run every five minutes; Pro supports intervals as short as ten seconds.
- Save, then open the monitor detail page and wait for a check result. Review the result time, response status, and latency. A pending monitor has not yet demonstrated availability.
For a service that requires credentials, a specific response keyword, a TCP port, or a DNS record, use the monitor configuration guide.
Make the first failure actionable
Open Settings → Alerts. Add a destination and select what the route covers. Connect a delivery service first if your chosen channel requires one. Saving a route does not prove delivery: send a supported service test and check the destination. Email and SMS need a real alert to verify receipt; use a disposable monitor you control to exercise failure and recovery without interrupting production.
When you have multiple dependencies, create a Nexus Point. Pro organizations can also publish a status page and invite teammates.
Explore before signing up
The demo contains a prepared sample workspace for exploring monitoring and incident response. Its data is illustrative and its controls are restricted. It does not provide unrestricted creation or editing of monitors or Nexus Points, and changes there are not production monitoring configuration.