Haven vs Leon

Haven

Haven answers by phone call, text, email and app, is free in beta with no card, and publishes a status page with dated incidents. No public page read says which actions need approval, which accounts it connects or how their tokens are kept, and it names no model provider or sub-processor.

Leon

Connected-app credentials are encrypted per profile and the Gmail connection is read-only. The 2.0 Developer Preview has no tagged release, runs tools and a 30-minute proactive pulse with no approval step, listens on every network interface with client authentication off, and sends telemetry by default.

Haven

1. Haven has no documented API or MCP server. An outside agent can reach it only through the owner's channels (call, SMS, email, app).
2. Do not assume an approval step before Haven sends mail, texts or calls. None is documented on the public pages.
3. Email Haven sends to other people names Hello Haven as sender and says it was sent on the user's behalf, per the terms.
4. Chat messages, history, profile context and uploaded files go to third-party AI model providers that the vendor does not name.
5. Check status.hellohaven.ai before relying on phone or voice. All four published incidents affected those channels.

Leon

1. Clone the develop branch for 2.0. npm install --global @leon-ai/cli and docs.getleon.ai install and describe the legacy 1.0 betas
2. Set client_interface.auth.enabled: true and a LEON_PROFILE_TOKEN before the machine joins a shared network. The server binds 0.0.0.0
3. Set telemetry_enabled: false and runtime.pulse_enabled: false in the profile config.yml for an unattended or private run
4. Use availability.tools.allowed to limit tools. Shell, file writes, computer use and browser control are otherwise available to the agent with no approval prompt
5. Back up LEON_CONNECTIONS_ENCRYPTION_KEY from the profile .env. Without it the stored connections cannot be read