Roll out governed Claude Code to every developer machine.

One install command per operating system puts PRAE on a machine, enrolls it in its group and installs the Claude Code hook for every user on it. From then on the control plane keeps it current: each group runs one signed policy version and one approved prae-cli version, a change reaches every endpoint in seconds, and each endpoint reports its health and integrity on every heartbeat. The decisions stay on the machine; their metadata is shipped as evidence.

One policy per group, on every machine, with proof it is still in force.

  1. 01 · Admin

    Approves a policy version (a second admin signs it off), promotes it to a group, and mints a registration code.

  2. 02 · Control plane

    Signs one manifest per group: the policy version, the prae-cli version, the deployment profile, and how long it stays valid.

  3. 03 · Endpoint

    prae-agentd checks for a new manifest every few seconds, verifies its signature, and never accepts an older one.

  4. 04 · Claude Code

    The hook in managed settings judges every tool call against the policy in force, for every user on the machine.

  5. 05 · Fleet view

    Each endpoint healthy, out of sync, degraded, disconnected or tampered — with the reason — and its decisions as evidence.

Govern → Enforce → Prove

Shipping · execution control
  1. 01

    Govern

    Immutable policy versions, each approved by a second admin; promoted to a group, rolled back, or frozen. A deployment profile sets what an endpoint does when its policy expires or never arrived — blocked by default, or the bundled baseline alone — and how it answers tampering. A profile that weakens a default needs a second admin too. A group can be pinned to an approved prae-cli version: each endpoint checks it against the integrity the manifest carries, tests it and moves to it, with no reinstall; pinning an earlier one rolls the group back.

  2. 02

    Enforce

    The policy is cached and signed on the machine, so a plane that cannot be reached changes nothing: the hook keeps enforcing. A corrupt cache or a bad signature blocks every call. A profile can block every call on a tampered machine until an admin clears it, or revoke the machine outright.

  3. 03

    Prove

    Every endpoint checks its own installation on each heartbeat — managed settings, the hook, the runtime, the policy state and each ledger — and reports what changed. Each user’s ledger rows are shipped to the control plane’s evidence store as metadata.

Coverage today: Claude Code endpoints on macOS, Linux and Windows, enrolled from a generated install script, driven from the command line and a signed API. The admin console is in design. Signed macOS and Windows installer packages and ready-made MDM bundles wait for code-signing identities; until then the install script runs under any MDM that runs a script. WSL is detected, not protected. A hosted plane only; customer-hosted is on the roadmap.

Developer agents →Claude Code →Live fleet steering →AI compliance & audit readiness →

What does the control plane receive?
Machine and OS-account names, versions, health and integrity results, and each decision’s metadata: the tool, the verdict, the rule, the policy version, hashes and times. Never prompts, commands, a rule’s reason, or the paths or contents of the files your agents touch.
Where does it run?
Hosted by PRAE on AWS in the EU (Stockholm). The store, signer and evidence sink sit behind interfaces, so a customer-hosted plane is on the roadmap.
How do admins drive it?
With prae org from the command line, every request signed with the admin’s own key. The admin console is in design.
# The admin: a registration code for one group, and its install script
prae org code --team platform --out platform.json
prae org install-script --file platform.json --os linux --out install-prae.sh

# Each machine, as root (or Administrator on Windows)
sudo sh install-prae.sh

# The fleet
prae org fleet
  • Not an MDM

    Your MDM delivers the install command; PRAE does not replace it. A machine without MDM runs the same script by hand.

  • Not a proxy

    Nothing routes your traffic through PRAE. Decisions are made on the machine, from the signed policy it holds.

  • Not tamper-proof

    Prevents for standard users, detects for administrators: the files are owned by the system, and a local administrator’s change is caught and reported.