macro-inc/macro

The problem

Small teams accumulate a stack of best-in-class tools — chat, docs, issue tracking, email, CRM — that were never designed to talk to each other. Links between them are faked with Zapier, MCP bridges and copied URLs, so the chain from "why are we doing this" to "who shipped it" is broken. Macro's answer is to rebuild all of those surfaces on one backend, with a shared bidirectional graph and shared team-level memory for humans and agents alike.

What's different

The usual approach is to adopt Slack, Notion and Linear separately and glue them together, or to pick a lighter "all-in-one" that is really a docs tool with a database bolted on. Macro's distinguishing claim is that every surface is first-class but shares one graph: an email can be @-mentioned in a doc, a task can be created from a channel message and traced to the PR that closes it, and a CRM contact can be queried from the inbox. The second differentiator is agents as first-class members with workspace-wide retrieval — the README's example is an agent searching parsed email attachment PDFs directly rather than paging through threads. Third, tasks are deliberately lightweight and coupled to chat, a direct bet against dedicated issue trackers.

Who it's for

Startups and small teams — roughly 10 to 50 people — that feel the integration tax of five SaaS tools and are willing to run their company inside one product. Engineering-heavy teams that want chat and tasks adjacent to code links fit best. Teams that already have deep, heavily customized workflows in Jira, Salesforce or a large Slack workspace with hundreds of integrations should stay away: the value proposition is consolidation, and migrating a mature workflow into a young product is the opposite of consolidation. Anyone needing on-prem control should check the self-hosting story before committing.

Cost of adoption

It is a full workspace replacement, so the real cost is migration and retraining, not installation. The stack is Rust plus SolidJS, licensed AGPL-3.0 — acceptable for internal use, but a constraint if you plan to embed or rebrand it. The project is young (created November 2025) and the README is a product tour rather than a deployment guide; self-hosting details, data export guarantees and API stability have to come from the docs. Features like version control are explicitly labeled v1.

Verdict

Macro is a brand-new project, not an established one: about 350 days old, 4,902 stars, with only two days on the trending board and a modest +202-star week. That is early interest, not a proven trajectory, and the single 8-point Show HN thread suggests the audience is still small. The idea — one graph under mail, chat, docs, tasks and CRM — is the right critique of the tool-sprawl problem, and a two-year dogfood by a ~15-person team is a better signal than the star count. Betting your company's operating system on it means accepting AGPL terms, migration work and the risk that a young product changes under you; try it with one team before moving everything.