Product · Fleet control plane
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.
-
01 · Admin
Approves a policy version (a second admin signs it off), promotes it to a group, and mints a registration code.
-
02 · Control plane
Signs one manifest per group: the policy version, the prae-cli version, the deployment profile, and how long it stays valid.
-
03 · Endpoint
prae-agentd checks for a new manifest every few seconds, verifies its signature, and never accepts an older one.
-
04 · Claude Code
The hook in managed settings judges every tool call against the policy in force, for every user on the machine.
-
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 controlCoverage 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 →
For DevOps & engineering
- 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 How it differs
-
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.