Security & trust

Straight answers, including the gaps.

The questions your security team will ask about a tool that can change your servers — answered with no badges, logos or endorsements. Where something isn't built yet, we say so.

Your servers

What the agent can and can't do

Today

What can the agent do on our servers?

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

Today

Do we open ports or share SSH keys?

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

Today

What if HostCrust itself is breached?

If HostCrust itself were breached, an attacker could at most queue the catalog actions your servers allow, with validated parameters. Running arbitrary commands needs shell, which stays off unless you turn it on locally.

Rolling out

Can an AI agent change production on its own?

Not today: there's no AI agent access to HostCrust yet. Access over MCP is rolling out during early access, and when it arrives, an AI agent can only propose a change. A person approves it.

The agent

The limits live on the server

The HostCrust agent is a single Python file that runs on each Linux server, built so you don't have to trust HostCrust. The installer writes /etc/hostcrust/agent.conf with four classes allowed: read, patch, service and reboot. Leave a class out and the agent refuses every action in it.

  • The agent only makes outbound HTTPS connections — no inbound ports, no SSH keys shared with us.
  • Shell is off by default; each action runs as a fixed argument list, not a shell command.
  • HostCrust can't change the allowlist. The agent refuses anything it doesn't allow, even when our app asks.
  • By default, patches, service restarts and reboots wait for an approver who signs off on the exact action.

Your data

Receipts, accounts and where data lives

Today

Can receipts be quietly changed?

Every action is written to a hash-chained, append-only log: who asked, the policy, who approved, what ran and how it was verified, as reported by the agent on the server. Our app's database role can't edit or delete it. Export it and check it offline with hc-verify, our open-source verifier.

Today

How are accounts and credentials protected?

Two-factor sign-in (TOTP) is required for every user. Passwords are hashed with argon2id, and every server gets its own random agent token, stored only as a hash and revocable.

Today

Can another customer see our data?

Every query on customer data is scoped to your organization, and automated tests try to reach another organization's data through every route.

Today

Where is our data stored?

Your HostCrust data is stored on our own server in Los Angeles, in the US. Every night, an encrypted backup of that data is copied to a separate server we operate in Canada.

What we don't have yet

The honest gaps

A rule we hold ourselves to: we never market a feature that isn't built, and we show no badges, logos or endorsements.

Coming next

What about snapshots, rollback and backups?

Not in v1. Snapshots, rollback and backups are coming next. We won't claim them until they're built.

Verify a receipt yourself, offline

hc-verify is our open-source (Apache-2.0) verifier. It recomputes every hash and reports the first broken link or missing record — pure Python, no network, so you can check a change without trusting our app.

Give your security team a tool they can check

Proof per CVE, a server that can say no, and a receipt for every change you can verify offline.

  • 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

Security questions

What can the agent do on our servers?

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

Do we open ports or share SSH keys?

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

What if HostCrust itself is breached?

If HostCrust itself were breached, an attacker could at most queue the catalog actions your servers allow, with validated parameters. Running arbitrary commands needs shell, which stays off unless you turn it on locally.

How are accounts and credentials protected?

Two-factor sign-in (TOTP) is required for every user. Passwords are hashed with argon2id, and every server gets its own random agent token, stored only as a hash and revocable.

Can another customer see our data?

Every query on customer data is scoped to your organization, and automated tests try to reach another organization's data through every route.