MSP / provider access

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.

Request MSP Starter Request Growth or Scale
PROVIDER Your Pulse Account CLIENT A Workspace own dashboards own alerts own users own audit history ISOLATED RUNTIME CLIENT B Workspace own dashboards own alerts own users own audit history ISOLATED RUNTIME CLIENT C Workspace own dashboards own alerts own users own audit history ISOLATED RUNTIME
Isolation

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.

Hosting

Provider-hosted by default

You run the workspaces on your own infrastructure, next to your clients. Pulse-hosted operation is available by request.

Accountability

Per-client audit trails

Separate users, audit history, and reports per workspace, so client boundaries hold up under scrutiny.

Every workspace is full Pulse

Client workspaces are not cut-down views. One client runs Proxmox, another runs Docker on Podman hosts, a third runs Kubernetes: each workspace monitors that client's whole stack, with the same Pulse the homelab community runs.

Pulse Docker overview in a client workspace showing five container hosts with CPU, memory, disk, uptime, and swarm roles
A Docker-heavy client: hosts, containers, swarm roles.
Pulse Kubernetes overview in a client workspace showing development, production, and staging clusters with node, pod, and deployment counts
A Kubernetes client: clusters, nodes, pods, deployments.

What you run as the provider

Clients get full Pulse; you get the layer above it. Your Pulse Account portal holds the whole client fleet, and every workspace can produce client-ready reports.

Pulse Account provider portal listing three client workspaces with setup status, active alert rollups, health, and onboarding actions
The provider portal: every client, one screen.

One portal for the whole fleet

Your Pulse Account lists every client workspace with its setup status, live alert rollup, and runtime health, and tells you which client to review next. Critical alerts surface at the fleet level, so the morning check is one screen, not ten logins.

  • Setup, alerts, and health per client at a glance.
  • A repeatable onboarding path for each new client.
  • Open any client workspace with one click when something needs attention.

Reports your clients actually see

Every workspace generates scheduled PDF performance reports covering uptime, resource usage, and fleet health over the period, ready to land in a client inbox. With white-label, they carry your name and logo, not ours.

  • Per-client scheduled reports from each workspace.
  • Uptime and resource trends over 24h, 7d, or 30d periods.
  • White-label branding available as a request-assisted add-on.
Cover of a white-labelled Pulse client report titled Harbour Logistics Monthly Infrastructure Report, branded with a fictional provider logo and name
A client report cover carrying the provider's branding (example provider and client).

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.

Starter

$149/mo

Up to 5 client workspaces, provider-hosted.

Request MSP Starter
Growth

$249/mo

Up to 15 client workspaces, provider-hosted.

Request Growth
Scale

$399/mo

Up to 40 client workspaces, provider-hosted.

Request Scale
Larger fleets, white-label, or Pulse-hosted rollouts stay request-assisted: start an MSP conversation.

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, then 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
Not a provider? See self-hosted pricing for single environments.