Start with one site
Choose representative endpoints and network equipment. Identify what you want to observe before enrolling devices.
A connected workflow.
A clearer next step.
Bring a site online, discover its devices, follow their condition and investigate what needs attention.
From first signal to clear action
How Pulse works
Connect your infrastructure, explore your site inventory, and investigate the signals that need your attention.
Bring an endpoint into your workspace. Keep its identity, agent status, and latest check-in together.
A clear starting point for every endpoint.See discovered devices grouped by site, with their addressing details. Move from an isolated endpoint to the wider site inventory.
Infrastructure you can navigate.Follow host metrics and configured thresholds. Read recent activity before deciding what needs a closer look.
Signals with context, in one place.Explore logs with AI assistance. Use the evidence behind a signal to understand the next step.
A shorter path from a signal to an explanation.Pulse
Endpoint enrollmentConnected
Endpointproduction-api-01
- Operating system
- Linux
- Agent status
- Reporting
- Last check-in
- Just now
Network discovery03
Site inventoryProduction site
Gateway10.0.0.1
DiscoveredAPI server10.0.0.12
DiscoveredDatabase10.0.0.24
DiscoveredHost metrics
CPU utilization34%Configured threshold · 80%
14:0014:1514:30
Log investigation
production-api-0114:21:06 INFO Request received14:21:06 WARN Upstream response delayed14:21:07 INFO Retry completedAI-assisted context
The delayed response was followed by a successful retry. Review the upstream service and the surrounding logs.
Give each step its own context.
A practical setup begins with a bounded site and a small set of devices.
Connect the right signals
Use the endpoint agent, SNMP or a native vendor connector. Add NODE when site-local collection is useful.
Make alerts useful
Set rules against the metrics you can actually collect. Review severity and duration with the team that will respond.
PULSE / NODE
A local presence, when the site needs one.
NODE provides a relay and local collection point. Agents discover it on the LAN and can use the direct path when a relay is unavailable. Review the network topology during setup.
IntegrationsSite network
Pulse NODELocal relay
Endpoint
NAS
Switch
Good questions.
Clear answers.
What does Pulse monitor?
Pulse collects endpoint metrics on Windows, macOS and Linux. SNMP and configured vendor collectors extend visibility to NAS, network equipment and Redfish-compatible servers.
Can I manage several client sites?
Devices, discovery results and alerts are organized by site inside the tenant workspace. You can move between an overall view and the context of a specific location.
Do I need a NODE appliance?
NODE is optional. It provides a local relay and collection point at a site. Agents can also send telemetry directly to the ingest service.
What does the AI assistant do?
It helps investigate collected device logs using context and log summaries. It requires an AI provider configuration and does not autonomously remediate devices.
How do I start?
Book a demo to map your devices, sites and integrations. The setup and commercial configuration are confirmed against your environment.