rcourtman
4cb769d02f
## Why
Every commit that touches user-visible frontend source had to rewrite
the single file `frontend-modern/browser-verification.json`. Any two
open frontend pull requests therefore conflicted the moment either
merged. A merge could not repair the loser: concluding it staged
`main`'s frontend files as if the author had changed them, and the guard
demanded a receipt covering files the author never ran. The only honest
recovery was to rebuild on the new `main`, run the browser pass again
and open a superseding pull request. On 2 and 3 October one
storage-table fix went #2415 → #2418 → #2433 that way.
## What changes
- **One receipt file per commit** under
`frontend-modern/browser-verification/`. The file name is the first 16
hex characters of the SHA-256 of the receipt's `content_sha256` map, so
it is fixed by the verified content, never chosen, and two changes only
share a file if they verified identical bytes. Receipts are only ever
added, so git merges them unaided.
- **Every binding the guard had is kept**: the commit's own parent, the
exact changed paths and their content digests, a viewport of at least
1024 and one of at most 768, non-empty routes, states and interactions,
and the range check that each changed frontend file's final content in
`base..head` matches a receipt from a non-merge commit in the range. A
hand-named receipt is not evidence.
- **Concluding a merge** no longer counts content a merged parent
already carries as the commit's own change. Merged content that neither
parent holds is flagged and still needs a follow-up receipt in range
mode; a merge commit may not record one.
- **`--write-template`** writes the skeleton at the path the staged
content requires. `--print-template` still prints it and now names that
path.
- **`--prune`** deletes receipts already on `origin/main`. A change that
records a receipt may not delete one, and the guard enforces that per
commit in both modes: git reads a deleted receipt beside a new one as a
rename, and that rename conflicts with any other change that deletes the
same receipt.
- **The shared file is retired**: no commit may write it again. It stays
in the tree, untouched, in this pull request, because deleting it would
conflict with every open pull request that still rewrites it. A
follow-up deletes it.
## Open pull requests that still rewrite the shared file
They keep working. A commit that modified the shared file while its own
parent still carried it remains valid evidence in range mode. The first
such pull request to merge lands untouched. Each later one still
conflicts on that file, and is now repaired without a rebuild or a new
browser pass:
```bash
git merge origin/main
git checkout MERGE_HEAD -- frontend-modern/browser-verification.json
git commit --no-edit
```
## What this does not change
Two open pull requests that edit different parts of the *same* frontend
file used to be stopped by the receipt conflict. They now both merge if
git can combine the edits. The range check still evaluates the merged
result, on the pull request when its check runs and on the push to
`main`; combined content that no receipt verified fails there and needs
a follow-up receipt. `browser_verification_guard_test.py` pins this.
## Proof
`scripts/release_control/browser_verification_guard_test.py` (45 tests)
covers the staged index, concluding merges, the integration range, the
retired file and pruning.
Run against a throwaway clone of this repository, with this change as
`main`: two branches cut from the same `main`, one editing
`components/shared/Table.tsx`, the other `utils/format.ts`. The first
merges; the second then merges with no conflict, and the workflow's own
"Validate final frontend browser evidence" step passes on that merge
ref.
```
### 3. Second PR against the moved main
git merge-tree main pr-b exit=0 (0 = no conflict)
merge ref 7e01f7cca9, parents ba458dded0 a7e11f39d6
pull_request range ba458dded0...7e01f7cca9:
Browser verification guard passed (1 frontend source file(s) across ba458dded03e..7e01f7cca90a covered by in-range receipts).
workflow step exit=0
### 4. Contrast: the same two edits under the shared receipt (74fd189fd0)
CONFLICT (content): Merge conflict in frontend-modern/browser-verification.json
git merge-tree exit=1 (1 = conflict)
```
Pulse
Real-time Proxmox, Docker and Kubernetes monitoring that finds what needs attention.
Pulse is a self-hosted monitoring workspace for Proxmox, Docker, Kubernetes, TrueNAS, physical and virtual machines, and early-access VMware vSphere environments. It combines live infrastructure state, history, alerts, recovery visibility, and scheduled health checks without requiring a conventional enterprise monitoring stack.
Why Pulse
- It watches between visits. Alerts and Pulse Patrol find failed backups, capacity pressure, restart loops, unhealthy containers, clock drift, and other problems that dashboards cannot surface when nobody is looking.
- It keeps each platform familiar. Proxmox, Docker, Kubernetes, TrueNAS, vSphere, and machines have dedicated views, backed by one shared resource model for search, alerts, history, and investigation.
- It stays operator-controlled. Credentials are encrypted at rest, API tokens are scoped, agent commands are disabled by default, and governed fixes require the configured policy and approval path.
Platform coverage
| Platform | Coverage |
|---|---|
| Proxmox VE, PBS, and PMG | Nodes, guests, storage, backups, replication, Ceph, mail gateways, and alerts |
| Docker and Podman | Hosts, containers, Compose projects, Swarm services, health, images, and updates |
| Kubernetes | Clusters, nodes, workloads, pods, services, storage, and events through the unified agent |
| TrueNAS SCALE and CORE | Pools, datasets, disks, snapshots, replication tasks, apps, VMs, and alerts |
| Linux, Windows, and macOS machines | Host health, filesystems, networking, temperatures, RAID, and availability through the unified agent |
| VMware vSphere | Early-access inventory, hosts, clusters, VMs, datastores, networks, snapshots, and recovery context; validate against your own vCenter before production use |
Platform pages keep storage and recovery information beside the infrastructure it belongs to. Alerts, Actions, and Patrol remain cross-platform views.
Patrol: monitoring that does rounds
Pulse Patrol runs scheduled checks across the current state and recent history of your infrastructure. Community installations can use a local model or their own AI provider for watch-only analysis. Pulse Pro adds investigation and policy-bound fixes with approval, verification, and an audit trail.
Pulse also includes an interactive Assistant and an MCP adapter for external clients such as Claude Code and OpenCode. Both sit on top of the same scoped inventory, metrics, alert, storage, and governed-action contracts.
Quick start
Choose an exact version from the latest release and keep that version pinned during installation.
Docker
docker run -d \
--name pulse \
-p 7655:7655 \
-v pulse_data:/data \
-e PULSE_DEPLOYMENT_METHOD=docker_run \
--restart unless-stopped \
rcourtman/pulse:vX.Y.Z
Open http://<your-ip>:7655 and follow the bootstrap-token setup. Docker host
monitoring is provided by the unified agent; the Pulse server container does
not need the Docker socket.
Proxmox LXC, Linux, and Kubernetes
The installer is signed. Verify install.sh against the pinned
pulse-installer key before running it:
export PULSE_VERSION=vX.Y.Z
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh" &&
curl -fsSLO "https://github.com/rcourtman/Pulse/releases/download/${PULSE_VERSION}/install.sh.sshsig" &&
ssh-keygen -Y verify \
-f <(printf '%s\n' 'pulse-installer namespaces="pulse-install" ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMZd/DaH+BldzOkq1A8KVTcFk73nAyrE8aJOyf7i00jm pulse-installer') \
-I pulse-installer \
-n pulse-install \
-s install.sh.sshsig < install.sh &&
bash install.sh --version "${PULSE_VERSION}"
Paste the whole block: installation stops if either download or signature verification fails. Do not run the final command separately to bypass a failure.
The GitHub installer installs the Pulse server. Install and upgrade agents (including v5-to-v6 agent upgrades) with the per-host command generated under Settings → Infrastructure → Install on a host.
Do you need an agent?
Often not. Proxmox VE, PBS, and PMG are monitored through the Proxmox API with a read-only token, so nothing runs on the host and the generated setup script creates a privilege-separated monitoring user. Install the unified agent only where you want data the platform API cannot provide, such as host SMART health, temperatures, Docker hosts, or standalone machines.
The agent is operator-controlled by design. Command execution is off by
default, the local listener binds to localhost, and generated systemd units
ship hardened. On Linux, the installer's --least-privilege profile runs the
service as a dedicated non-root user, with optional scoped sudo grants for
the few collectors that need elevation. The
agent security model documents exactly what the
agent can and cannot do at each privilege level.
Important
GitHub release assets and
rcourtman/pulseimages are Community builds. Relay, Pro, and eligible legacy customers should use the private image or Linux archive provided by the Pulse download portal. Replacing a private Pro runtime with a public Community build removes its private runtime hooks.
Editions
- Community — self-hosted monitoring, seven days of metric history, core SSO, update alerts, and Patrol with your own provider or local model.
- Pro — Community plus Patrol investigation, governed fixes, ninety days of history, centralized agent profiles, RBAC, audit logging, and reporting.
- MSP — for managed service providers: one Pulse Account running many client workspaces, each with an isolated Pulse runtime — separate dashboards, alerts, users, audit history, and reports. Free sixty-day two-client evaluation at Pulse for MSPs.
Relay is no longer sold. Existing Relay subscribers receive Pro features at their current price for as long as their subscription continues. Existing paired phones keep working until 31 March 2027. Relay connects the app, not the web UI. Use your own VPN or tunnel for remote web access. For phone alerts, add an ntfy, Gotify or Pushover destination and open Pulse in your phone's browser.
Core self-hosted monitoring is not gated by monitored-system or child-resource volume. See the runtime-aligned capability reference and current plans for details.
Documentation
- Install and deployment
- Production deployment and security
- Upgrade from Pulse v5
- Releases and update channels
- Configuration
- Platform and agent guides
- Pulse Intelligence
- Security and privacy
- Code signing policy
- Troubleshooting
- API reference and architecture
Localized getting started guides: Deutsch · Español
Development
Pulse uses Go 1.26 and a SolidJS/TypeScript frontend. The managed development
runtime starts the frontend at http://127.0.0.1:5173 and proxies API and
WebSocket traffic to the backend on port 7655.
npm ci
npm --prefix frontend-modern ci
npm run dev
Useful checks:
go test ./...
npm --prefix frontend-modern test
npm --prefix frontend-modern run type-check
python3 scripts/check_public_docs.py
See CONTRIBUTING.md before investing in a code change. Pulse uses an issue-first contribution process and does not normally accept unsolicited pull requests.
Community and support
- Ask questions in GitHub Discussions.
- Report reproducible bugs through GitHub Issues.
- Home Assistant users can use the community-maintained Pulse add-ons.
- If Pulse is useful to you, support its development through GitHub Sponsors or Ko-fi.
License
Everything in this repository is licensed under the MIT License. There is no dual licensing and no commercial or source-available code here.
Pulse Pro is a separate commercial product, built from private sources and distributed through pulserelay.pro. Its use is governed by the Terms of Service, which apply to that product only, not to anything in this repository.