Security at Korden
Last updated 10 June 2026 · Early access
Korden is built so that the most sensitive thing you own — your source code — stays under your control. The architecture is local-first, and the few cloud features are opt-in and protected in transit.
Local-first by default
- Repos, terminals, and crew worktrees live on your device. Nothing about your code is uploaded for normal local use.
- AI requests go directly from your machine to the model provider you connect (your Claude plan, your API key, or a local model). Korden does not proxy or store them.
- Cloud sync and shared Cloud workspaces are off by default. They only transmit data when you turn them on.
Installers & updates
Updates are delivered through a cryptographically signed auto-update channel, so the app verifies each update genuinely came from us and hasn't been tampered with, and builds are produced by an automated CI pipeline rather than by hand. Authenticode signing of the Windows installer is in progress — until it lands, Windows may show an “unknown publisher” notice on first run.
Credentials
Your model logins and API keys are stored locally on your device and used to talk to your chosen provider. We don't collect or store your model API keys on Korden's servers.
Accounts & payments
- Authentication is handled by Amazon Cognito, with email, Google, and GitHub sign-in. Linked logins for the same verified email resolve to one account.
- Payments are processed by Stripe. We never see or store full card numbers.
- Account and any opted-in cloud data are hosted on AWS and transmitted over TLS.
Responsible disclosure
Found a vulnerability? We want to hear from you. Email support@kordenhq.com with the subject “Security disclosure” and steps to reproduce. Please give us a reasonable window to investigate and fix before any public disclosure — we'll keep you in the loop.