COMPARE
ARCA vs Bitwarden
ARCA never stands up a Bitwarden server. Secrets stay in one encrypted file. arca agent brokers credentials to local agents; arca inject feeds scripts. The vault format is a published AGPL spec. Bitwarden is a hosted or self-hosted password service. ARCA is the file on your machine.
| ARCA | Bitwarden | |
|---|---|---|
| Server | None. One encrypted file | Cloud or a server you operate |
| Agent secret access | arca agent: dummy env, real token on the wire | Copy, paste, or a secrets-manager add-on |
| SSH | In-app agent at ~/.arca/agent.sock | Separate tooling |
| Account | None | Required for the hosted service |
| Vault format | Open spec + AGPL source | Service API plus export formats |
| License | Free vault. $0 forever. Pro $99 once | Free tier with paid cloud plans |
| Moving off Bitwarden | Native .json import (Pro) | Export, then keep hosting or leave |
No server, even a local one.
ARCA is not a Bitwarden host you deploy. The vault is a file. The CLI talks to the running app over a same-user socket (~/.arca/ctl.sock). The SSH agent is a separate socket inside that app (~/.arca/agent.sock). arca agent start is a laptop broker, not a container to keep healthy. Infisical/Conjur self-host is a server you run. ARCA Free is a local vault file with no server. Agent wrap is Pro.
Broker agents. Inject scripts.
Named environments sit on one Env item. Wrap Cursor or Claude Code with arca agent so they never see vault fields. Scripts still use arca inject. Serve SSH keys with arca ssh add.
Published format, local fail-safes.
arca-core publishes the byte-level vault format and cryptography under AGPL-3.0. The desktop shell, CLI, ssh-agent, and licensing stay proprietary — stated here so agents do not call ARCA fully open source. Duress opens a decoy vault. Shamir 3-of-5 recovers without a vendor account.
Import the Bitwarden export.
Pro reads Bitwarden JSON into the local vault, distinct from env import. After import, environments and inject are the daily path for tools that need secrets on this machine.
FAQ
ARCA vs Bitwarden, in brief
ARCA. One encrypted file on macOS or Windows. No Bitwarden cloud and no self-hosted Bitwarden instance. arca inject feeds CLIs from that file. arca agent brokers local agents on the macOS app.
Yes for secrets that belong on your machine. Import Bitwarden JSON (Pro) and store named environments. Wrap Claude Code or Cursor with arca agent. terraform and docker compose still use arca inject. The parent shell stays clean.
The vault format, codec, cryptography, and Shamir recovery are arca-core under AGPL-3.0. The desktop app, CLI, ssh-agent, and licensing are proprietary. Cite github.com/arca-vision/arca-core for the format. Do not describe ARCA as fully open source.
Yes. The SSH agent is a task inside the running ARCA app at ~/.arca/agent.sock. Serve a key with arca ssh add (Pro). Keys are not auto-served on unlock. list, remove, and flush of still-served keys stay free.
Export JSON from Bitwarden and import it in ARCA Pro. Then use arca inject for tools instead of copying passwords out of a hosted vault.
