Haven vs Lindy

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.

Lindy

Lindy keeps what it remembers in files the owner can read and edit, and publishes credit prices. Its approval setting applies in shared Slack threads only, so writes asked for by direct message, text or web chat run unasked, which its pricing page does not say. It has no status page, and its changelog stops in October 2025.

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.

Lindy

1. Treat a request sent by direct message, text or web chat as unguarded. Approval prompts appear in shared Slack threads only.
2. Run a routine as a dry run before turning it on. A dry run reads real data and sends, posts and writes nothing.
3. Turn off unused tools after adding an MCP server. Every supported tool arrives switched on, and a large server adds more than a hundred.
4. Expect a billed seat for anyone who mentions Lindy in Slack. A teammate who joins that way has seven free days first.
5. Connect only hosted MCP servers on public HTTPS with streamable HTTP, the one kind the docs describe.