Macro: An All-in-One Workspace Built with SolidJS and Rust

According to a report on macro-inc on GitHub Trending, a new workspace tool called Macro has been released. It is an all-in-one platform that integrates email, messages, documents, tasks, AI agents, and CRM into a single fast interface for teams. All elements are connected via @ links and are searchable, designed so that teams and their agents do not need to switch between tools.

Development Background and Objectives

The development team faced the problem of tool fragmentation as they scaled their previous venture to around 20 people. They adopted numerous excellent software solutions such as Slack, Linear, Notion, HubSpot, and Superhuman, but these did not work together as a single system. Each team had its own tools, with MCP and Zapier holding the entire company together, leaving the company in a state of chaos rather than computability.

Macro was created as a result of redesigning work software as a single system from the ground up to solve this problem. It was designed in New York and Toronto and was field-tested for two years by a team of about 15 people. Emphasizing speed and reliability, it is built with SolidJS and Rust.

Technical Features and Architecture

Macro is composed of modular components called “blocks.” Each block works with others like LEGO bricks and is extensible. Each block is purpose-built for a specific function, yet all use a shared backend. Cross-references between documents and tasks, as well as links between channel messages and email, are natively stored as a bidirectional graph.

SolidJS and Rust were chosen for the technology stack. SolidJS is known as a reactive UI framework and provides fast performance. Rust is a systems programming language with excellent memory safety and concurrency, enhancing backend reliability. This combination aims to maintain responsiveness even during large-scale data processing.

Details of Key Features

Macro’s main features are provided as the following blocks.

Email: Integrates multiple Gmail accounts into a single inbox, operable with keyboard shortcuts. It adopts a keyboard-first interface inspired by Superhuman and includes tagging and sharing features. Multiple accounts can also be organized separately.

Messages: Provides channels and direct messages specialized for technical discussions. It achieves more focused communication than existing chat tools.

Tasks: Features task management inspired by Linear. Closely integrated with channels, email, and agents, enabling centralized management of task progress.

Documents: Real-time collaborative documents based on CRDT. Natively supports Markdown and includes @mention functionality.

Canvas: A two-dimensional board where embedded links to tasks, files, and email can be set. Used for visual workflow management.

Agents: AI agents with team-level shared memory. They execute actions on behalf of users and work with documents and tasks. Agents can also reference call logs recorded and transcribed in the Calls block.

File storage: Makes files automatically imported from email and channels fully searchable. Pull requests are linked to tasks, embedded in channels, and available to agents.

CRM: Manages customer and contact objects, offering custom properties, email synchronization, and enrichment features. All customer data is integrated within a single system.

Deep Dive into AI Integration and CRM

Macro’s AI capabilities aim for integration beyond a simple chatbot. It features an MCP surface that allows agents to search across multiple inboxes and retrieve information accurately. For example, it is envisioned to automatically parse @ links in documents and task statuses to provide context-aware suggestions.

The CRM function goes beyond being just a customer management tool, enabling bidirectional links with email and messages. All interactions with customers are consolidated into a single profile that can be shared across the entire team. This is expected to improve the efficiency of sales and customer support.

Regarding the difference from existing workspace tools, Macro is distinctive in that it eliminates data fragmentation between tools and manages information on a single graph database. This is a different domain from the security issues discussed in the article Microsoft Secure Boot remains vulnerable for 13 years, but it may share common challenges in terms of vulnerability management and the increasing complexity of access control resulting from the integration of the entire system.

Market Position and Challenges

Macro is positioned as an “operating system” for teams at startups and large enterprises. In the current work software market, Slack, Microsoft Teams, Notion, Linear, and others hold dominance in their respective domains, and integration relies on middleware such as MCP and Zapier. Macro enters as a single solution that replaces these tools.

However, this approach also faces challenges. The migration cost from existing tools is high, and the need for all team members to adopt a single platform can be a barrier. Moreover, competing with established players who have large ecosystems and integrations requires significant resources and trust-building.

As shown in the article Meta pauses Conversation Focus subscription charges, subscription models and pricing directly affect user adoption. Similarly, for Macro, the balance between pricing strategy and value proposition will be important.

Editorial Opinion

In the short term, Macro is likely to attract attention from small and medium-sized businesses and startups struggling with tool fragmentation. The development team’s hands-on experience enhances credibility, but for market adoption, import features that facilitate migration from existing tools and a robust set of phased deployment options are essential. Over the next three to six months, beta testing and the accumulation of implementation case studies will be key.

In the long term, it appears likely to accelerate the trend toward integration of workspace software. The deep integration of AI agents and CRM suggests a new stage of business automation. However, data privacy and security—particularly the management of confidential information as shared memory—will be major challenges for enterprise adoption. As the article Mesa Rusticl and Mali Panfrost enabled by default shows, the choice of technology stack affects long-term maintainability, so it will be important to watch how the adoption of SolidJS and Rust supports sustainable development.

References

• “macro-inc /

  macro", by **macro-inc** — GitHub Trending, 2026-08-13 (ARR)

• Source URL: https://github.com/macro-inc/macro