How it works

One loop for every change.

Request, policy, approval, run, verify, receipt — every time, whoever asked. Install a one-command agent, see what's really patched per CVE, and run every patch, restart or reboot through the same loop, with a receipt you can verify offline.

The loop

Request, policy, approval, run, verify, receipt

Every change — a patch, a restart, a reboot or a diagnostic — goes through the same six steps.

1

Request

Someone on your team asks for a change: a patch, a restart, a reboot or a diagnostic.

2

Policy

Your org's policy decides. By default, diagnostics run straight away and patches, restarts and reboots wait for approval.

3

Approval

An approver signs off on the exact action: server, action and parameters, bound by a hash. Change anything and it needs a new approval.

4

Run

The agent checks the server's local allowlist, then runs the action as a fixed argument list. No shell unless you turned it on.

5

Verify

After a patch, Patch Proof re-checks the CVEs it targeted from the inventory the agent sends back. A restarted service must report active, a rebooted server a new boot ID.

6

Receipt

Who asked, the policy, who approved, what ran and what the agent reported back: hash-chained, exportable, checkable offline.

Step one

Connect a server in one command

Get the token from Add server in the app. Read install.sh first if you like: it pins the agent's SHA-256 hash, and the agent is a single Python file.

Install the agent

curl -fsSL https://app.hostcrust.com/agent/install.sh | sudo HOSTCRUST_ENROLL_TOKEN=… sh

The agent only makes outbound HTTPS connections. It opens no ports, and you never share SSH keys with us.

On your server

The limits live on the server, not in our app

A local allowlist on each server decides which kinds of action the agent will ever run. HostCrust can't change that file, and the agent refuses anything it doesn't allow, even when our app asks.

  • Shell is off by default. The agent runs each action as a fixed argument list, never a shell command, unless you turn shell on locally.
  • Leave a class out of the allowlist and the agent refuses every action in it — read, patch, service or reboot.
  • If HostCrust itself were breached, an attacker could at most queue the catalog actions your servers allow, with validated parameters.
  • Every server gets its own random agent token, stored only as a hash and revocable at any time.

Run your first change through the loop

Sign up, connect a server, and watch a patch go request → approval → run → verify → receipt.

  • 3 servers free — every feature, not a trial
  • Connect a server with one command
  • No credit card, no sales call
Start free

During early access, everything is free.

FAQ

How it works — questions

How do I connect a server?

Run one command on the server: it downloads the agent, pins its SHA-256 hash and enrols with a token you get from Add server in the app. The agent is a single Python file and only makes outbound HTTPS connections.

What happens when someone requests a change?

Your organization's policy decides. By default, read-only diagnostics run straight away, and patches, service restarts and reboots wait for an approver who signs off on the exact action.

What does the agent check before it runs anything?

The agent checks the server's own local allowlist, then runs the action as a fixed argument list. No shell unless you turned it on, on the server itself.

How is a change verified?

After a patch, Patch Proof re-checks the CVEs it targeted from the inventory the agent sends back. A restarted service must report active, and a rebooted server a new boot ID. These results are reported by the agent on the server.

Can I check the record myself?

Yes. Every change lands in a hash-chained, append-only receipt. Export it as JSON and check it offline with hc-verify, our open-source verifier — edit an entry and the check fails.