Privacy & security

We don't ask for your trust. We prove it.

"Free" isn't an argument when you're asking someone to hand over their API keys. So OpenAxis doesn't ask you to take anything on faith. No account, no cloud, no telemetry — and the whole thing is open source. Here's where every secret and every byte of your data lives.

Keys in an encrypted file, never on disk

Your API keys are stored in an encrypted file at ~/Library/Application Support/openaxis/secrets.enc (AES-256-GCM). Not in a config file, not in local storage, not inside any tool's view. The proxy loads them into memory and passes them as environment variables when a process starts.

The proxy is localhost-only

The LLM proxy binds to 127.0.0.1 and nothing else. It requires a Bearer token on every call, so no other process on your machine can quietly burn your key. The tools only ever receive a fake local token.

Sandboxed views

Each wrapped tool runs in a hardened view: context isolation on, sandbox on, Node integration off. The bridge between the shell and the views is tiny and validated, and never takes a raw disk path as input.

No server, because there's no backend

OpenAxis has no cloud component. Nothing is sent to an OpenAxis server, because one doesn't exist. The only outbound calls are the ones you trigger, going straight to the model provider you chose.

Full transparency

Where every piece of your data lives.

All of it is local, in your home directory. You can open these files yourself.

DataWhere it lives
API keys~/Library/Application Support/openaxis/secrets.enc (AES-256-GCM)
Projects~/.config/openaxis/projects.json
Memory~/.config/openaxis/memory.json
Tool config~/.config/opencode/opencode.json
Chat historylocal storage + a file backup on disk
Orchestrator deliverablesa workspace folder you choose
The short version: nothing is sent to an OpenAxis server, because there isn't one. Your inference calls go to the provider you picked, and your keys never leave your Mac.
Auditable by design

If you don't trust it, read it.

Open source isn't a marketing badge here, it's the security model. The proxy, the way secrets move from the encrypted file into memory, the sandboxing, the override layer: all of it is published under the MIT license. A tech lead can audit it before rolling it out to a team. You can too.

One more thing: the agent that runs shell commands is bound to localhost with a per-session password that's never logged. The orchestrator's code agent runs with shell execution deliberately switched off — write and edit access is enough. A blocked shell can't run arbitrary commands.

Your keys. Your machine. Your call.

Download OpenAxis, add your keys to the Config panel, and watch where they go: nowhere but your Mac.