Security at CockpitAI
Cockpit attaches to the agents on your own machines. Your code stays on your hosts, your AI subscriptions stay yours, and the backend holds only what it needs to sign you in, sync your settings and connect your browser to your hosts.
Where your data goes
- Model traffic: agent CLI → cockpit-proxy on your host → your AI provider. Cockpit never calls an LLM itself and does not see your prompts on their way to the provider.
- Desktop: the app connects to your hosts directly over SSH, a local shell or WSL2.
- Phone and browser: Cockpit Web reaches your host through an outgoing relay that the host opens to cockpitai.dev – no open ports on your host.
- Backend: your account, your devices, your synchronised settings, the encrypted vault, the token manager for your AI accounts, and your subscription state.
All connections use TLS. The details – what we store, why and for how long – are in the Privacy Policy.
Your vault
Secrets you keep in Cockpit's vault are encrypted on your device with a key derived from your passphrase (Argon2id, AES-256-GCM). The server stores the encrypted blob but cannot read it – and cannot recover it if you lose the passphrase.
AI account credentials
The token manager holds the credentials of your AI accounts encrypted at rest, with a key kept outside the database. It refreshes them for you, and your hosts receive only short-lived access tokens, end-to-end encrypted to each host – the synchronisation service and the web server never see them.
Cockpit Web
Every relay connection is authenticated per host, and only your own browser sessions – and
the members you invite into a shared project – can use it. Sign-in uses a session cookie
(HttpOnly, Secure) and no tracking. You can review and sign out
devices and browser sessions in the app at any time.
Signed releases
The desktop app installs an update only when it carries Cockpit's release signature, and the proxy installed on your hosts is verified the same way.
Our operations
The backend runs in the European Union. Operator access needs a passkey and is recorded in a tamper-evident audit log. Services run in separate containers with least privilege; the token manager has its own database.
Reporting a vulnerability
Please report security issues to security@cockpitai.dev with the steps to reproduce them. We read every report and respond, without a guaranteed time. Please give us a reasonable time to fix an issue before you disclose it, and do not access other users' data or disrupt the service while testing.