Mastra

Mastra's docs open by calling it a TypeScript framework for building AI agents and applications. A project starts from npm create mastra@latest, which scaffolds an agent harness with a local workspace, shell tools, memory, task tracking, web access and recurring schedules, and opens Studio, a local UI for the project.

The homepage groups the framework into agents, workflows ("typed steps, retries, and branches"), a harness for multi-mode agents, memory with observational memory and semantic recall, a server that registers agents and workflows and deploys "the same app to Mastra Cloud", and Factory, "a system of specialized AI agents that takes software from issue to production." Observability covers traces, metrics, logs, evals and datasets.

MCP works in both directions.

The pricing page has two tabs, Mastra Platform and Self-Hosted, and no monthly/annual billing switch.

On the platform, Starter is $0 a month with 100K observability events (then $10/100K), 24 CPU hours (then $0.35/hr), 15 days of retention and unlimited users, deployments and projects. Teams is $250 a month with 1M events (then $8/100K), 250 CPU hours (then $0.25/hr), 6 months of retention, and "Multiple teams, SSO, and SOC 2 docs". Enterprise is custom priced, with RBAC, audit logs, uptime SLAs and a dedicated support engineer.

The base fee is only part of the bill. The comparison table also meters data egress (10GB on Starter, 100GB on Teams, then $0.10/GB), a persistent 24/7 server at $100 per project, gateway tokens at "Market Rate + 5.5%", memory tokens at $10/1M past the allowance, retrieval storage at $20/GB, and LibSQL rows, Postgres compute hours and database storage, each with its own overage rate. No cost calculator is published.

On the Self-Hosted tab, the framework is free and "Apache 2.0 licensed".

The license page describes a dual model: Apache 2.0 for most of the codebase, and the Mastra Enterprise License for anything under an ee/ directory, including @mastra/core/auth/ee, @mastra/core/agent-builder/ee and @mastra/editor/ee. That code is source-available and free for development and testing.

The page lists exactly what needs a license in production. Authentication on API routes with any provider (Auth0, Clerk, Okta, WorkOS and others) does not. A Studio sign-in screen with a third-party provider, role-based access control, fine-grained authorization and Agent Builder do. A team that plans to give non-engineers Studio access through its identity provider is buying the Enterprise license.

The trust center says Mastra "received our SOC 2 Type II Report in October 2025" and offers the report on request.

The same trust center carries Mastra's incident report for June 16, 2026. Anyone who installed @mastra packages in that window was exposed to the credential theft.

The about page says Mastra started in 2024, has 45 people working remotely and is based in San Francisco. It names Sam Bhagwat (founder and CEO), Abhi Aiyer (CTO) and Shane Thomas (Chief Product Officer), and says the team previously built Gatsby. It states $35m raised from investors including Spark Capital, Gradient, basecase and Y Combinator, and the founders' video caption refers to a $22m Series A.

The homepage links customer stories from Salesforce, Sanity, WorkOS, MongoDB and Range, all hosted on Mastra's own site.

The getting started pages show no Python SDK and no route for a team that does not write TypeScript, so a Python shop or a non-technical buyer gets nothing from the framework directly. Agent Builder, the closest thing to a no-code surface, is an Enterprise-licensed feature in production.

Teams that need predictable spend should model the platform's metered lines before committing, since CPU time, egress, gateway tokens and databases are each billed separately above the plan allowance. Teams that want to avoid metering entirely can self-host the Apache 2.0 framework, or pay the flat annual Self-Hosted Enterprise fee once they need SSO, RBAC or Agent Builder.