calcsam

Those are both good options. You should try us all out and see which one you like best!

Our cloud platform is in beta so it's free right now!

You found the Easter egg!

thanks!

Thanks for the feedback. We hear from a lot of devs with fond memories of Gatsby but if it cuts the opposite way for you that's also fair!

Most of us spent a lot of the last decade building Gatsby so it's sort of a personal identity/pride thing for us more than a marketing thing. But maybe we need to keep our identity small! Either way, thanks for saying something, worth thinking about.

Cloud-hosted observability + studio features (and self-hosted with EE bits).

You can take a look at the cloud platform at cloud.mastra.ai, it's in beta currently

It's the same play we did at Gatsby to get to several million in ARR in a couple of years

Re: Tanstack AI, really depends on adoption. We've known Tanner since his react-static days and if it takes off we'll def work together.

Re: Mastra cloud -- this is basically hosted services, eg observability, hosted studio, hosted serverless deployments, as distinct from the framework.

With server adapters you can now deploy your studio in your infra. We're going to pull multi-project / multi-user Mastra cloud features into a Mastra admin feature so you can run these locally or deploy them on your infra as well (with EE licensing for stuff like RBAC). Stay tuned here.

ah crap, thanks for heads-up. looking into it.

Thank you for using us, and for the feedback!

Do you have code snippets you can share about how you wanted to write the rules? Want to understand desired grammar / syntax better.

Have a ton of respect for the AI SDK team. Initially we only used AI SDK model routing, but now we also have our own built-in model routing as well.

I see each of us having different architectures. AI SDK is more low-level, and Mastra is more integrated with storage powering our studio, evals, memory, workflow suspend/resume etc.

Thank you! We have an incredible designer and we love obsessing about this stuff.

We've always supported letting folks specify their agent hierarchy, eg agent supervisor, workflow orchestrator, mix and match, etc.

But people kept asking us for a multi-agent primitive out of the box so we shipped `agent.network()`, which is basically dynamic hierarchy decided at runtime, pass in an array of workflows and agents to the routing agent and let it decide what to do, how long to execute for, etc!

https://mastra.ai/docs/agents/networks

Less frequently sites and more frequently a SaaS app, for example Sanity released a content agent in their CMS, Factorial released an agent inside their HR/payroll product.

But tons of other use cases too, eg dev teams at Workday and PayPal have built an agentic SRE to triage their alerts, etc etc

When Langchain was the only option rolling your own made a lot of sense!

These days we see things going the other way, where teams that started rolling their own shift over to Mastra so they can focus on the agent vs having to maintain an internal framework.

The Latent Space article swyx linked earlier includes a quote from the Brex CTO talking about how they did that.

And I actually hadn't seen that Brex piece so thanks for sharing!!

LOL thanks swyx. Yeah we realized although we _could_ fight that war again...it would be better for everyone if we didn't...

Re: lessons from coding agents, we're building some of the key abstractions like sandboxes, filesystem, skills/knowledge as Mastra primitives in over the next month.

For any agent you're shipped to production though you probably want a harness that's open-source so you more fully control / can customize the experience.

I mean we're framework guys so I would agree!

Thanks! And of course hope you try Mastra out when you do.

Thanks! That's a lot of why we built Mastra. We wanted something that felt like it was made for us.

You should use whatever framework you feel like has the best DX / fits your stack best!

We're TypeScript-first, TypeScript-only so a lot of the teams who use us are full-stack TypeScript devs and want an agent framework that feels TS-native, easy to use, and feature-complete.

Thanks, great to hear!

There's the normal stuff you'd expect -- we're all Opus-pilled, use Claude Code, a PR review bot etc. But it's been especially helpful with highly templatized code like our storage adapters, we already have 10-15 working examples which makes the n+1st adapter almost trivial to write.

interesting idea, this benchmark maps fairly closely to the types of output I typically ask LLMs to generate for me day-to-day

We have a ticket to allow this actually!

You’re right that the syntax was inspired by the desire to avoid nested structures. But the syntax here is interesting as well and fairly readable. Worth thinking about!

awesome! let us know how it goes

1. what are you wanting to create?

currently agents and workflow endpoints are created at `/api/workflows/workflow-id` and `/api/agents/agent-id/` for workers and agents

2. we are thinking about it -- curious what you'd use it for?

https://www.artifact.engineer/

Agentic's tool library _should_ also work for Mastra via its AI SDK adapter.

(We haven't tested this, so if you do try let us know if you see quirks!)