Skip to content
buildbay.
Macro logo

Macro

macro-inc · CRM

GitHub stars

4,515
—Collecting 30d data

Stats updated

4,462 stars on Sep 27 to 4,515 stars on Oct 2, up 53.6 measured star snapshots

What is Macro?

Macro’s linked workspace gives a task the email or conversation that created it, lets a CRM record lead back to related messages and files, and lets agents search shared team context. Its modular surfaces remain connected rather than forcing people to reconstruct decisions across separate tools.

Macro is an open-source workspace that brings email, chat, docs, tasks, calls, code, CRM, and AI agents into one connected system. Shared memory and bidirectional links keep work and context available across every surface.

Core capabilities

  • Email, chat, docs, tasks, calls, code, and CRM share one workspace and one navigation model.
  • Team-level AI memory connects company context across conversations, documents, tasks, and meetings.
  • Fully open-source AGPLv3 codebase built primarily with Rust and SolidJS, with a self-hosting path.

Work surfaces connected by bidirectional links

Email, channels, documents, tasks, calls, files, pull requests, and CRM records share one workspace. @-links connect those objects in both directions, so a task can retain the discussion that created it and a company record can lead back to the messages, mail, and files behind the relationship.

  • email
  • chat
  • docs
  • CRM

Shared context for teammates and agents

Macro builds team-level memory from the connected workspace and makes that context searchable across product surfaces. Built-in agents can act with the same company context, while external clients can use MCP connections rather than starting each request from an isolated prompt or chat history.

  • shared memory
  • agents
  • MCP
  • self-hosted

Where it fits

Use cases

  1. 01

    Run company work in one system

    Replace separate email, chat, docs, task, call, and CRM tools with linked surfaces inside a shared workspace.

  2. 02

    Give agents company context

    Make team memory and linked workspace objects available to built-in agents and external MCP clients.

  3. 03

    Self-host and extend the workspace

    Deploy the AGPLv3 codebase yourself, contribute changes, or build on its Rust and SolidJS architecture.