Hosted Pulse, without running the server yourself.
Pulse Cloud is the hosted deployment model for Pulse. You get a real Pulse tenant, the same runtime self-hosted users run, while install, upgrades, and the hosted edge are handled for you.
A real Pulse tenant
Your hosted deployment is a dedicated Pulse instance, not a thin dashboard on top of shared state.
Managed for you
Provisioning, upgrades, licensing, and the hosted edge are owned by the Pulse Cloud control plane.
Same mobile path
Pulse Mobile pairs with a hosted tenant through the same encrypted Relay connection as self-hosted Pulse.
Where Pulse Cloud is today
Hosted signups are not open yet. The self-hosted product is the current focus, so hosted capacity is paused rather than half-launched. If you want a hosted Pulse tenant, register your interest and I'll email you when signups open: no waitlist spam, just the one email.
Register InterestManaged does not mean shallow
A hosted tenant watches your infrastructure with the same depth self-hosted Pulse does: Proxmox, Docker, Kubernetes, TrueNAS, vSphere, backups, and disk health included.
- A dedicated hosted Pulse tenant under the Pulse Cloud control plane.
- Managed deployment lifecycle instead of manual install, upgrade, and host patching.
- Mobile access through Pulse Relay instead of exposing a runtime yourself.
- The Pulse experience for teams who do not want to own the infrastructure stack.
What it is not
- Not a different product. It is the hosted deployment model for the same Pulse core.
- Not required for mobile access: self-hosted Pulse with the Relay plan covers that.
- Not the right fit if you want to own the runtime, the upgrade timing, and the environment. Self-hosted stays first-class.
Why it is not open yet
- The self-hosted product comes first. Hosted capacity is paused, not half-launched.
- When signups open, hosted tenants go through the same release line self-hosted users run, not a separate fork.
- Registering interest gets you one email when it opens. Nothing else.
When Pulse Cloud makes sense
Good fit
- You want Pulse outcomes without operating another server.
- You want managed upgrades and a hosted edge handled for you.
- You are happy to wait for hosted signups to open properly instead of an early half-supported version.
Choose self-hosted instead
- You want Pulse today: self-hosted is live now and free to start.
- Your monitoring data must stay inside your own environment.
- You already run infrastructure and one more container is trivial for you.