Halyard vs Mem.
Mem is a personal AI thought partner — clean capture, proactive resurfacing, a beautiful solo workflow. Halyard is organisational knowledge for agent-native teams. They address different problems, and in most cases you'd choose on audience more than features.
The right choice for individuals who want a personal AI thought partner. Capture a note, and Mem resurfaces related context as you type. The craft is in the individual writing experience — not in connecting to your team's work.
The right choice when your team's knowledge is scattered across Slack, Notion, GitHub, and meetings — and you want that knowledge automatically captured and surfaced to whatever AI tools your team uses. Multiplayer by default. No composer required.
Audience is the decision.
Pick Mem when…
- You're an individual (writer, researcher, solo builder) curating a personal second brain.
- You love the proactive resurfacing experience — notes finding you, not the other way round.
- Your capture is driven by your own writing — email, web clips, personal thoughts.
Pick Halyard when…
- The knowledge you need lives in your team's Slack, GitHub, and meeting notes — not your inbox.
- You want AI tools (Claude, Copilot, Cursor) to use your org's knowledge without everyone adopting a new app.
- You want capture to be automatic and attributed, not manual.
- Multiplayer + agent retrieval + human routing matter more than a solo writing UX.
These products don't really compete. Mem is a personal notes app; Halyard is organisational infrastructure. If you use Mem personally and want your team to have the same always-there context across AI tools, Halyard is the team-level equivalent — not a replacement for your personal vault.
Feature by feature.
A row-by-row honest read. Most "winners" here are a function of audience.
| Feature | Mem | Halyard | Winner |
|---|---|---|---|
| Who it's for | Individuals, solo creators, small teams wanting frictionless personal notes | An organisation's collective knowledge, queryable by every person and AI tool on the team | Depends |
| How knowledge gets in | Email forwarding, web capture via extension, iOS/desktop/web composer | Automatic capture from Slack, Notion, GitHub, Drive, Linear, Granola — no composer, no forwarding | Halyard |
| Proactive context resurfacing | Best-in-class — the Mem Copilot surfaces related notes as you write, without you asking | Retrieval-on-demand via agents, not proactive surfacing in a personal notes UI | Mem |
| Multiplayer / team use | Workspace tier exists, but positioning and core experience is individual-first | Team-native from day one — shared graph, attribution, role-based access | Halyard |
| AI retrieval from other tools | Not supported — Mem is a closed notes app; agents can't retrieve from it | Every AI tool your team runs reads the same grounded graph via MCP | Halyard |
| Integration ecosystem | Weak — email + web capture + Raycast. Notably few work-tool integrations | Slack, Notion, GitHub, Drive, Linear, Granola meetings — and growing | Halyard |
| Human expert routing | N/A — personal notes app | Agent hits an unknown → Halyard routes to the right human in Slack → reply becomes durable knowledge | Halyard |
| Authoring UX | Clean, fast, frictionless — Mem's core craft | Lightweight — Halyard is a knowledge layer, not a primary authoring surface | Mem |
| Product velocity | Development has been widely reported as slow over the past year | Active — shipping weekly | Halyard |
The team version of always-there context.
Halyard makes what your team produces retrievable by every agent your team uses.