Centralized Control for AI Teams
Deploy the AiKey control plane on an intranet host to manage upstream providers, invite team seats, and issue virtual keys in bulk to your developers.
Server Administrator
Deploys the control plane on an intranet host, onboards upstream providers like Claude and Codex, and issues virtual keys to seats.
Developer User
Installs the CLI on their workstation, logs in to the server, and uses the virtual keys issued against their email for local development.
Administrator Workflow
Deploy AiKey Server as a systemd-managed stack on your Linux infrastructure.
Step 01: Prerequisites
Step 02: Deploy Control Plane
gh auth login
export GITHUB_TOKEN=$(gh auth token)
gh release download v1.0.0-rc.3 -R aikeylabs/launch-master -p server-install.sh -D /tmp
bash /tmp/server-install.sh --version v1.0.0-rc.3 --yesStep 03: Control Panel Login
Access the UI at http://SERVER_IP:3000
Developer Workflow
Onboard your workstation to the team control service.
Install Local CLI
curl -fsSL https://github.com/aikeylabs/releases/download/v1.0.0-rc.3/local-install.sh | bash -s -- --version v1.0.0-rc.3
source ~/.zshrcLog in to Server
aikey web
aikey login --email developer@example.com --control-url http://SERVER_IP:3000Use Virtual Keys
Click the install-hook banner in the web vault. Open a new terminal and run claude to verify routing.
Edition Comparison
Factual overview of deployment models based on source documentation.
Deployment Target
Infrastructure hosting environment
Local Workstation
Intranet Linux Host / Control Plane
User Roles
Access and permissions management
Single Developer
Server Administrator + Developer Users
Credential Source
Upstream provider authentication
Local Vault
Provider Accounts (Claude, Codex, etc.)
Access Distribution
Key provisioning and lifecycle
Local Route Tokens
Seats and Virtual Keys (aikey_vk_*)
Usage Visibility
Activity logging and telemetry
Local Usage Receipts
Centralized Reporting to Server
Operations
Service management and maintenance
Local CLI Tools
aikey-server status/logs/restart
Transcript Retention
Whether conversation content is stored
Not available — transcripts stay on the workstation
Optional "Conversation Audit": full transcripts stored on a server you own
Compliance Hit Retention
Whether matched original text is stored
Not uploaded — matched text stays on the workstation
A short snippet of the matched original text (≤512 bytes) is stored with the compliance event on a server you own, kept 90 days. On by default on a fresh install; upgrading an existing deployment leaves it off
- Compliance detection (the checkpoint): detection runs on the employee's own machine and masks or blocks sensitive content before it reaches the model. 🔴 Corrected 2026-08-11: this page previously said "
never uploads the conversation text — nobody can retrieve the original wording after the fact", and that statement is now void. On Team / Cluster editions, when your organization's compliance privacy policy is at its highest level, a snippet of the matched original text — roughly 24 characters either side of the match, at most 512 bytes — is uploaded with the compliance event to a server you deploy and own, is readable by your administrators, and is kept 90 days before being cleared. Personal edition uploads nothing. - 🔴 That setting is ON by default on a fresh install — read both defaults: a fresh install of Team / Cluster ships turned on, so from day one after the one-command deployment your employees' matched sensitive content is being uploaded to your own server; upgrading an existing deployment changes nothing (it stays off) until an administrator enables it. The switch is a server-side organization policy — no employee machine can enable or disable it.
- Two different kinds of "original text": compliance detection keeps a short snippet per hit (≤512 bytes), governed by the compliance privacy policy; Conversation Audit keeps the whole turn, governed by the Conversation Audit capture switch. The two switches are independent — with Conversation Audit off, hit snippets are still uploaded.
- Conversation Audit: a separate switch. When enabled it uploads the full transcript (complete prompt + complete AI reply + system prompt) to a server you deploy and own, readable by anyone who can sign in to your console. Defaults: not available on Personal · off on single-host Production · on at install time on Cluster.
- Capture happens before masking: content that compliance detection redacts is still readable in clear text inside Conversation Audit.
- Employees see no notice: collection is a silent side lane, so the duty to notify employees sits with you (the data controller). AiKey only ships the switch and its default.
- The data never leaves your company (true of both lanes — this one has not changed): the server is your own machine, and neither the hit snippets nor the full transcripts ever reach any AiKey server — AiKey (the vendor) neither operates nor can access it. "Vendor collection" and "retention on your own servers" are different things.