Macro is the all-in-one workspace that combines email, messages, docs, tasks, code, agents, calls, and CRM. With team-level memory, you can query your entire workspace and never lose context.
I'm Jacob, the founder and CEO of Macro (macro.com) - an open source, all-in-one workspace.
In our last startup, we ran on Slack + Linear + Notion + Superhuman + 17 other tools. All of these are fine individually but as we scaled it became chaotic to manage, and information was everywhere.
We built Macro to replace siloed apps and put them all into a unified workspace with shared AI memory.
Already Macro has:
Email inspired by Superhuman, with better AI for triaging ("Signal vs. Noise")
Notion-like documents with fast CRDT's instead of last-write-wins, @linked to everything
Messaging, like Slack, but more focused for deep work
Linear-like tasks but deeply integrated with channels, auto-created and auto-assigned
Video calls with Google Meet performance that are transcribed and added to your team
A unified brain for all of this, in one place, and much more
We've also chosen to be open source in order to keep customizability at the core of our company. You can check out the repo here https://github.com/macro-inc/macro and see what we're building in the Pull Requests tab.
Macro is an ambitious project. But that's also what makes it so useful and fun to work on.
Team-level memory that lets you query your whole workspace is the compelling part - most unified-workspace tools stop at search. Does the memory span everything (docs, calls, CRM) from day one, or is there a lookback window before it kicks in?
Open source is a smart trust move for a workspace that wants to hold email, docs, tasks, calls, and CRM in one place! The adoption challenge is that most teams will not move their whole stack at once. Are early users starting with Macro as an email client first, or are they bringing docs and tasks in from day one?
The constant hopping between apps is one of those small daily drains you stop noticing, so seeing it all pulled into one calm place is a relief.
finally something that pulls my chaotic slack, gmail, and notion stuff into one place without me copy-pasting between tabs. the team memory search is genuinely useful for digging up old context
How does the team-level memory actually work across different tools like email and code—does it pull context live or do you need to keep everything inside Macro for it to be useful?
replacing 17 tools with one app is the pitch every all-in-one workspace makes, and it usually means each individual piece ends up 80% as good as the dedicated tool it replaced. what's actually best in class here vs just "good enough to not need Slack anymore" - email triage, docs, or something else
Inheriting the launching user's permissions is a sane default. Where it got us was memory writes: once the agent summarizes something into shared memory, a teammate with lower access can pull that derived summary later even if they were never allowed to see the source it came from. Does a memory entry carry the ACL of its most-restricted source, or does it just inherit the channel it was created in?
The shared memory part is the bit I’m most curious about. Feels like a lot of tools are getting better at storing more context, but more context is not always the same as useful context. How does Macro decide what is actually worth remembering? Is it mostly things I tell it to save, or does it start picking up patterns from how I work over time?
the super-app graveyard is real. slack tried to be your inbox, docs, calls, CRM. teams too. both ended up as chat with a lot of tabs nobody clicks. the thing that would actually make one of these work is the connective tissue between the parts. team memory is that, if it knows who said what where.
genuine question: is the memory a permission-scoped graph or a flat corpus? that's where team products either become invaluable or become HR nightmares.
Shared memory is the hook here, but the trust boundary feels just as important. Can teams choose which channels, docs, or calls get added to agent memory, or is everything in the workspace queryable by default?
I've been waiting for a workspace where AI actually understands everything happening across emails, docs, and tasks. This looks like a promising step in that direction. Best of luck with the launch!
The unified surface demos well, but the hard part is team memory respecting permissions at retrieval time. If I query 'the workspace' and the answer lives in a doc or DM I'm not on, does retrieval enforce ACLs per chunk, or is the index shared and you filter after? We built agent memory over mixed-permission sources and the lesson was that access control has to live inside retrieval, not the prompt, or the model will happily quote something the user was never allowed to see. Being open source makes that auditable, which is a real plus.
How does the team-level memory actually work across all those different tools, especially for things like email threads from a few months back that I barely remember starting?
This is one of those products that immediately makes sense. Bringing docs, tasks, communication, and AI into a single workspace could eliminate so much context switching. The shared AI memory is an especially interesting idea. Looking forward to trying it out—congrats on the launch and best of luck! 🚀
Huge shoutout for going open source with this 👏 @jacob_beckerman qq Is there a native desktop app with global shortcuts for quick capture, or is everything running out of the browser for now?
About Macro on Product Hunt
“Unifies your work into one app with shared memory”
Macro launched on Product Hunt on July 2nd, 2026 and earned 154 upvotes and 27 comments, placing #5 on the daily leaderboard. Macro is the all-in-one workspace that combines email, messages, docs, tasks, code, agents, calls, and CRM. With team-level memory, you can query your entire workspace and never lose context.
Macro was featured in Productivity (655.1k followers), Task Management (84.1k followers) and Artificial Intelligence (472.5k followers) on Product Hunt. Together, these topics include over 257.1k products, making this a competitive space to launch in.
Who hunted Macro?
Macro was hunted by Ben Lang. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Macro stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Hey Product Hunt!
I'm Jacob, the founder and CEO of Macro (macro.com) - an open source, all-in-one workspace.
In our last startup, we ran on Slack + Linear + Notion + Superhuman + 17 other tools. All of these are fine individually but as we scaled it became chaotic to manage, and information was everywhere.
We built Macro to replace siloed apps and put them all into a unified workspace with shared AI memory.
Already Macro has:
Email inspired by Superhuman, with better AI for triaging ("Signal vs. Noise")
Notion-like documents with fast CRDT's instead of last-write-wins, @linked to everything
Messaging, like Slack, but more focused for deep work
Linear-like tasks but deeply integrated with channels, auto-created and auto-assigned
Video calls with Google Meet performance that are transcribed and added to your team
A unified brain for all of this, in one place, and much more
We've also chosen to be open source in order to keep customizability at the core of our company. You can check out the repo here https://github.com/macro-inc/macro and see what we're building in the Pull Requests tab.
Macro is an ambitious project. But that's also what makes it so useful and fun to work on.
Give it a try: https://macro.com/