Mastra launches Knowledge, a standalone service for company-wide agent context

From Slack agents to a company-wide knowledge graph

According to Mastra, the way the team works has changed over the last few months. Instead of logging into a system to find out what happened, staff ask an agent in Slack. Example questions include what users' responses were to last week's new feature, and what new objections are surfacing in the sales pipeline. Answering such questions usually means querying multiple systems.

Mastra says the answers are no longer in one person's head, but "in everyone's feed." Many of these agents were initially powered by separate knowledge graphs. Last month, using its software factory, the company built a single company-wide knowledge graph. Mastra reports that its coding agents then had context on the decisions behind building certain features, and that it saw a noticeable improvement in the quality of code shipped. In the company's words, agents began building things the way the team would want, rather than in a naive way.

Why a company brain is hard to build

Mastra argues that agents are getting easier to build, but constructing a company-wide context layer is not. It lists three lessons from its own work:

• Freshness requires versioning. An organization exists to update important information quickly, so "checked recently" does not mean "correct now." Without automatic updates, Mastra says, a base error rate is introduced.
• Complete answers need feature-based organization. Topics span systems used by different teams, and even a simple feature might span several code repositories. Mastra compares a knowledge graph to a local cache of company information, and says mapping the relationships between systems and topics is difficult.
• Decision records matter. One feature's record reached 1,054 lines with 19 dated change headings. Such a record preserves the reasoning so future contributors do not unintentionally repeat paths already considered.

What Knowledge does

Knowledge is described as a standalone service that holds company and team context and gives it to an agent when the agent needs it. Users connect the systems where their organization already writes, such as Slack and Monday, and Knowledge keeps itself current.

It sits alongside Mastra memory, which handles per-user and per-thread context, while Knowledge covers the company and the team. Organizations can run separate knowledge bases per function, for example coding and support, and set permissions at the individual, team and org level.

Design partners and what comes next

Mastra says it is already working with organizations that want their own knowledge bases, ranging from a couple of companies valued above $50B to 50-person startups. One early design partner feeds questions its support agent could not answer back into its company brain, so the agent gets them right the next time.

The company is now accepting eight more design partners. It is aimed at teams that are building internal agents and considering how to expand them into a company brain. The source gives no pricing or general availability date.