Run Pulse for every client from one account.
Standard self-hosted plans cover one Pulse environment. Pulse MSP gives providers a single Pulse Account to run many clients, with an isolated Pulse runtime per client workspace — separate dashboards, alerts, webhooks, users, audit history, and reports. Provider-hosted by default; Pulse-hosted by request.
A runtime per client
Each client workspace is its own isolated Pulse runtime with its own data directory — not a tag filter inside one shared install.
Provider-hosted by default
You run the workspaces on your own infrastructure, next to your clients. Pulse-hosted operation is available by request.
Per-client audit trails
Separate users, audit history, and reports per workspace, so client boundaries hold up under scrutiny.
Plans
MSP checkout is request-assisted while public MSP signup is in assisted preview: email me, and I set up your provider account against the published pricing below. No discovery calls, no custom quotes for the standard tiers.
Choose MSP when
- You operate Pulse for multiple paying clients and need clean per-client boundaries.
- Clients need their own dashboards, alert routing, users, and reports.
- You want one commercial relationship covering the whole client fleet.
Stick with self-hosted plans when
- You monitor one environment, even a large one — Community, Relay, or Pro covers it.
- Your "clients" are internal teams happy to share one workspace and one audit trail.
- You are still evaluating Pulse — start free, and move to MSP when real client boundaries appear.
After you request access
I reply from [email protected], confirm the tier and workspace count, and send a direct checkout link for the published price. From there you get your provider Pulse Account and set up client workspaces on your own infrastructure.
Request MSP Starter