// the find
macro-inc/macro
Macro is a unified workspace for teams: email, chat, docs, tasks, agents, calls, and CRM — @-linked together with shared AI memory.
Macro is an all-in-one team workspace — email, chat, docs, tasks, CRM, calls, and AI agents — built by a startup as a Slack/Linear/Notion/HubSpot replacement for their own use, then open-sourced. It targets small companies or teams within larger orgs who want one connected system instead of a pile of point tools glued together with Zapier.
The architecture backs up the pitch: 167 Rust crates and 42 services in a hexagonal layout, CRDT-based docs with offline reconciliation, and a bidirectional graph linking every object type (email thread to task to PR) rather than a bolted-on 'integrations' layer. It's genuinely AGPLv3 open source, not open-core with the good parts held back. The MCP surface reportedly covers close to 100% of what the UI can do with no rate limits, which is a real commitment if true, most SaaS agent integrations are a thin subset of the product.
Ten product surfaces (email, chat, tasks, docs, canvas, agents, calls, files, PRs, CRM) built by a team of ~15 over two years is a lot of area to keep uniformly solid; expect real depth in a few blocks and thin coverage elsewhere. AGPLv3 is a hard constraint for anyone wanting to build a derivative hosted product on top — you're either fully open with your changes or paying for a different license. Doc version history is explicitly 'still v1' per their own README, and email currently only mentions Gmail/Google Workspace, so IMAP or Outlook shops are out of luck for now. Self-hosting 42 services plus Pulumi infra and a Nix dev shell is not a docker-compose-and-go affair despite the 'running locally' doc existing.