Haven vs OpenDuet

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.

OpenDuet

Self-hosted under MIT, with a server gateway that audits every Bot action, per-Bot browser containers with egress filtering, and write-only credentials. Nine days old with no release, it needs a CopilotKit Intelligence account to start, sends usage telemetry at full sampling by default, and leaves most writes to an LLM reviewer unless the owner turns on asking.

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.

OpenDuet

1. Follow the README's Quick start (bun install, bash scripts/start.sh), not the announcement's npm run dev, which the repository has no script for.
2. Run bun openbot/scripts/setup-learning.ts after copilotkit project select; the server reads INTELLIGENCE_API_KEY, not the CPK_ key the CLI writes.
3. Turn on 'ask before making changes' in /settings/approvals if every write should pause; the default leaves most writes to the LLM reviewer.
4. To bring your own agent, register it as a remote-ag-ui Bot in agents.yaml; its tool calls still pass through the gateway's policy and audit.
5. Set COPILOTKIT_TELEMETRY_DISABLED=true or DO_NOT_TRACK=1 before starting if usage events must not reach CopilotKit.