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.
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.
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.
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!
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.
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.