One family, four distinct AI tools.
Cordy covers browser assistance, supervised CLI work, Android chat, and a self-hosted gateway. Each product documents its own storage, account, and network boundaries.
One philosophy, every surface
Choose the product whose runtime and data boundaries fit your work.
Choose your providers
Chrome and Mobile accept your provider credentials, Desktop launches independently configured CLI agents, and Gateway operators issue member access to configured models.
Local-first by design
Chrome and Mobile keep their app data locally. Desktop persists workspace, terminal, browser, site, and credential-vault data on its host. Gateway uses your hosted Postgres and Redis.
Private by default
Provider calls, browser sites, CLI tools, and optional Gateway observability have different data paths. Each product guide states what leaves the device or host.
No lock-in
Choose among supported providers and local runtimes, export supported client data, and operate Gateway on your own infrastructure.
Four surfaces, one AI stack
Pick where you work. Cordy meets you there.
Cordy Gateway
One endpoint for configured models
A self-hosted, OpenAI-compatible text gateway with operator and member access, API keys, prepaid billing, routing, and optional observability.
Cordy for Chrome
AI that understands your tabs
A browser-direct assistant: chat about pages, act on selected text, and organize tabs, history, read-later items, and bookmarks.
Cordy Desktop
The workbench for CLI coding agents
Run CLI coding agents in project-root workspaces with supervised terminals, files, Git tools, notes, and a built-in browser.
Cordy for Mobile
A calm AI chat you control
Android-focused, bring-your-own-key chat with local conversation storage, provider catalogs, usage controls, and multimodal source paths. iOS runtime remains unverified.
Own your AI stack.
Bring your keys. Keep your data. Run it your way — on the web, your desktop, your phone, or your own server.
Get started