Comments URL: https://news.ycombinator.com/item?id=47049478

Points: 3

# Comments: 0

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.

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

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

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.

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

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

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.

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.