How billing works on Mastra
@Mastra recently launched their open-source, configurable software factory.
If you gave it a spin and created your account, you might have received this email from their CEO @calcsam.
Welcome to the Mastra platform! I wanted to quickly walk you through how to choose the plan that's right for you.
We start you off on our Starter plan (free). You get a small bucket of observability events, CPU hours, data egress, and 15 days of data retention. You can add as many users, projects, and deployments as you want. It's great for development when you're building an agent.
When you're ready to ship to prod, or are monitoring your agents in prod, we recommend upgrading to Teams ($250 / month). This gives you 6 months of data retention, 1 million observability events, and 250 CPU hours.
Or consider our Server Always-On ($100 / month), which keeps your server warm around the clock (otherwise there's a boot-up time on request), and folds in a full month's worth of CPU hours.
Here's a blog post from our head of platform Joel with the full pricing details. Happy building!
Personally I really enjoy this approach, humble and direct. From my previous experiences working at dev-first companies like @Clerk and @Mintlify, I know how resourceful developers are. They need to experience your product first, on their own time, so they can determine whether or not it's right for them.
Curious to have your thoughts about this first-time experience.
@Mastra recently launched an open-source, agent-powered software delivery environment. It combines persistent coding agents, repository workspaces, issue intake, planning, implementation, and pull request review in a web application you control. The product ranked #1 Product of the Day and #1 Product of the Week.
Replies
The gap that'll hurt is free to $250 with nothing in between. I've got agents in prod that will never touch a million observability events, and I'm not paying $250 to keep them warm, so I self host and Mastra gets nothing from me. The $100 always-on is the closest thing to the missing rung and it's framed as an add-on rather than a plan, which is why nobody will find it. The email itself is good though, because it names CPU hours and retention instead of saying for growing teams.