Mastra opens Knowledge design-partner access for company and team context

Mastra announced Knowledge on October 26 as a standalone service that supplies company and team context to an agent when needed. The company said it was opening access to eight more design partners, on a first‑come, first‑served basis. That is an invitation to a limited early‑access program; the announcement does not establish that places remain available at the time someone applies.

For teams building internal agents, the question is whether the agent needs information shared across the organization or history from an individual conversation. Knowledge is presented as that shared context layer, alongside Mastra’s existing memory system.

According to [Mastra’s description](https://mastra.ai/blog/announcing‑mastra‑knowledge), its memory system handles per‑user and per‑thread context, while Knowledge handles the company and team. Organizations can maintain separate knowledge bases for functions such as coding and support, with permissions at individual, team and organization levels. Those distinctions matter when deciding which context an agent should receive. A support function and a coding function can have separate knowledge bases, while a conversation’s own history remains a different scope. The described permission levels are product capabilities reported by Mastra, rather than an independent assessment of enforcement or compatibility with every upstream source’s access rules.

The [post names Slack and Monday](https://mastra.ai/blog/announcing‑mastra‑knowledge) as examples of systems an organization can connect and says Knowledge keeps its information current. It also argues for preserving decision records: the reasoning behind a feature can be useful context, beyond the latest description of what that feature does. For a prospective design partner, that makes source selection and responsibility for updating decisions part of the implementation discussion. “Keeps itself current” is Mastra’s feature description, not a measured freshness guarantee. The announcement does not provide a deployment walkthrough, package version, price, hosting specification or service‑level commitment. Those details still need to be established before treating the invitation as a ready‑to‑deploy production plan. *AI‑generated conceptual illustration by OpenTools Team: a shared document cabinet represents company and team context. This is illustrative artwork, not an actual product interface, company location, hardware device or tested result.*