We don't ask you to trust the agents.
K2 runs AI agents on a server your company controls, beside your staff. Here is what K2 enforces, what it doesn't, and the command that checks each.
- First step
- We scope the first job with your team and put it in the quote.
- Cost
- Free to self-host. If we run it, from $750 a month. Bigger or custom work: a written quote before anything moves.
We hold no outside security certificates and offer no SSO today. See all three limits →
Sample data. Phone approval is Beta.








What K2 does today, and how to check it.
Run the commands on your own box, signed in as the owner. If a row disagrees with your version, trust the box.
Checked 10 November 2026 on K2 0.46.10.
Limits
| Question | Answer | Check |
|---|---|---|
| Are agents kept apart? | Not from each other. Agents on one server share one user account, so a tricked agent could read other agents' files and the owner token, then act as owner. Built-in presets turn off each AI tool's own prompts, so an agent can do anything the K2 user can. | ls -l ~/.k2/daemon.tokenk2 preset show claude |
| What isn't recorded? | Terminal commands and file edits. Watch those with your own monitoring. | auditctl -l |
| Do you have SSO, SOC 2 or HIPAA? | No SSO, SAML, SCIM or MFA: passwords, with lockout. Owner, admin and member logins are trusted operators. A Voice and Chat only login joins voice rooms and sees only what you share with it. No SOC 2 report or ISO certificate, and no HIPAA claim. Your team can read the source, control the box and run these commands. | k2 users |
Your call
| Question | Answer | Check |
|---|---|---|
| What starts off? | Mail, DNS, apps and database, until an owner or admin grants them. K2 enforces this in software, so a tricked agent could step around it. | k2 dns accessk2 permission list |
| Where do keys live? | One encrypted vault per server. Agents use keys by name without seeing them. A key sent to a file or environment variable can be read, and agents with admin rights can reach the vault. | k2 vault status |
Ready
| Question | Answer | Check |
|---|---|---|
| What limits an App? | On Linux, each App gets its own container, an allow-list of outside hosts and an audit of its calls. This covers Apps, not agents. | k2 app egress <app> |
| Can we read the code? | K2 is open source under the MIT license: free to use, change, run and resell, keeping the copyright notice. Our chat and voice engine, Sew, is MIT licensed too. | Source on GitHub |
What you turn on decides what crosses your network.
- Local modelStays inNothing crosses
Needs a capable machine and a custom preset.
- Claude or ChatGPTGoes outAnthropic or OpenAI
That company receives what agents send it.
- K2 ConnectPhones and outside accessOut, encryptedOur relayAshburn, Virginia
It forwards only encrypted data.
- Support accessIf we set it up or run itIn, by your grantAlakazam Labs
Only the access you give us, agreed with your security team. You can revoke it.
Air-gapped, by agreement. Designed to run air-gapped with a local model, under an Enterprise agreement. Your staff let us in. Otherwise, K2's update check goes to GitHub.
Five things on record.
Two your monitoring must watch.
Keep groups that must never mix on separate servers.
K2's approvals and settings handle daily control. Your network is the hard line.
Server A, operations
A tricked agent could reach all of this.
Server B, people team
Its own files and owner token. Your network decides if they can talk.
Test us on one job, before anything moves.
Your current software keeps running the whole time.
- First
Scope it with us
We scope the first job with your security team and put it in a written quote.
- Next
Run one job
One back office job, on sample records until you sign off.
- After that
You run it, or we do
Your choice, at the price above.
Check it on a box you control.
K2 is the software. Alakazam Labs is the team behind it.