AI agent security for organizations
Find out what your AI agents can reach, and contain them.
Your people run Claude Code, Codex, Cursor, Copilot and agents they wrote themselves, often on machines your MDM does not manage. Each one can read files, run commands, hold API keys and reach the internet. We find out what they can do on your network, write the policy that governs them and put the controls in place.
What we offer
Assessments, E-Series, and C-Series on your machines or ours.
- Available now
AI agent security assessment
We inventory the AI agents on up to about 25 machines, review what they are configured to do and what they can reach, and give you a written report with the fix for each finding. About one week.
About the assessment - By arrangement
E-Series
An AI DMZ on hardware you own: an edge that checks who is signing in, outbound rules for every agent and a sandbox for each agent run. Offered as a pilot.
About E-Series - Waitlist open
C-Series Cloud
A C-Series Host on a machine of its own, which we set up, secure and keep up to date. Nothing of Privatae's sits in front of it but the server it runs on. You hold the key to its disk.
Join the waitlist - Open source · available now
C-Series
An open-source AI agent that runs on your own machine, licensed AGPL-3.0. The source is on GitHub and builds and runs today.
About C-Series
Who it's for
Machines your MDM and endpoint security don't cover.
Linux workstations and servers, research and GPU machines, developer laptops, contractors' machines: the parts of a Windows, macOS and Linux fleet that often sit outside device management.
If you can't say which AI agents run on which machines, or what they can reach, this is for you.
How an engagement runs
From the first call to a team that runs it.
- 1. Onboarding callWhat you run, on which machines, and what worries you. We agree the scope and the price.
- 2. AssessmentAbout one week: inventory, configuration and network review, and a written report.
- 3. Policy and enforcement planA written policy for AI agents in your organization, and how each rule is enforced on each kind of machine: which agents are allowed, and what they may reach.
- 4. ImplementationPutting the controls in place: firewall and egress rules, network segmentation and access control, the agents' own managed settings where the tool offers them, and the bastion where it fits.
- 5. Turnover and trainingYour team gets the runbooks and a training session, so they can keep the policy enforced and monitored after the engagement ends.
The assessment is the first step. Each later step is quoted from what the assessment finds, so you know the cost before that work starts.
Who does the work
I'm Casey.
I've spent 16 years in network infrastructure, security, and operations: as a network engineer for the US Air Force, ITA Pentagon, and lead network access control engineer at a federal research campus.
I started Privatae when I saw the systemic issues created by bringing AI into a network that isn't ready for it.
Start with a call.
Tell us which tools your team runs and how many machines are in scope. We reply with dates.