AI Coding Agent Platforms
How do I contact Mastra sales for enterprise support/SLAs or an on-prem deployment?
6 min read
For enterprise teams that need formal support, SLAs, or to discuss an on‑prem or private deployment, the fastest path is to contact the Mastra sales team directly via the website contact form or company email so we can scope your requirements and set up a tailored demo.
Quick Answer: Use the Mastra “Contact Sales” flow to reach our sales team with your company email, outline whether you need enterprise support, SLAs, or an on‑prem deployment, and we’ll follow up to schedule a conversation and custom demo.
Frequently Asked Questions
How do I contact Mastra sales for enterprise support, SLAs, or on‑prem?
Short Answer: Go to the Mastra site, open the Contact/Sales page, and submit the form with your company email, use case, and whether you’re interested in enterprise support, SLAs, or on‑prem deployment.
Expanded Explanation:
Mastra has a dedicated sales path for organizations that want more than community support—things like response‑time SLAs, production rollout guidance, and help planning on‑prem or private cloud deployments. When you submit the contact form with a company email, the sales team can quickly route you to the right person (technical, security, or commercial) and line up a custom demo focused on your requirements: e.g., running Mastra agents behind your firewall, integrating with your existing observability stack, or aligning on incident and uptime expectations.
If you’re just exploring the framework, you can start open‑source with npm create mastra and community channels. But once you’re planning to make agents part of your core infrastructure, contacting sales is the right move to lock in enterprise‑grade support and guarantees.
Key Takeaways:
- Use the Contact/Sales form with a company email to reach Mastra sales for enterprise conversations.
- Be explicit about “enterprise support,” “SLAs,” or “on‑prem deployment” in your message so we can scope correctly.
What’s the process after I contact Mastra sales?
Short Answer: After you submit the form, Mastra will typically respond by email to clarify your needs, then schedule a live session to demo Mastra and discuss architecture, SLAs, and deployment options.
Expanded Explanation:
Once your request comes in, the sales team reviews your company details, tech stack, and the type of support you’re asking for (enterprise, SLAs, on‑prem). From there, we usually do a discovery call to understand your workloads—e.g., multi‑agent workflows, RAG assistants, MCP integrations—and your deployment constraints (VPC‑only, specific clouds, data residency).
That conversation drives a tailored demo and proposal: where Mastra fits your current stack (Next.js, Express, Hono, or other), what observability/exporter setup you’ll need, and what level of support and SLA makes sense based on your traffic and risk profile.
Steps:
- Submit the contact form on the Mastra site using your company email and describe your enterprise/on‑prem needs.
- Respond to the follow‑up email to schedule a discovery + demo call with the sales/engineering team.
- Review proposed architecture, support model, and SLAs, then move into proof‑of‑concept and rollout planning.
What’s the difference between community usage and enterprise support/SLAs?
Short Answer: Community usage is self‑serve, best‑effort help around the open‑source framework; enterprise support adds contracted SLAs, prioritized assistance, and deeper guidance for production and on‑prem deployments.
Expanded Explanation:
Mastra’s open‑source framework (Apache 2.0) is free to use: you can spin up Agents, Workflows, RAG, Memory, MCP, and Evals locally with npm create mastra, integrate with your own servers, and get informal help via the community (Discord, X). That’s ideal for prototypes, internal tools, and lower‑risk workloads where you own all operational overhead.
Enterprise support and SLAs are for teams where Mastra is part of mission‑critical infrastructure. You’re running production agents, need predictable response times on issues, and may require security reviews, data handling guarantees, or on‑prem/VPC‑only deployments. In that mode, sales helps you define formal support coverage and escalation paths, instead of relying solely on community channels.
Comparison Snapshot:
- Community (OSS only): Self‑guided, best‑effort community help; you manage reliability, costs, and incident response.
- Enterprise (with SLAs): Contracted support, defined response times, access to experts for architecture, performance, and on‑prem planning.
- Best for: Teams treating agents as core infrastructure (e.g., Plaid/Elastic‑style deployments) should talk to sales about enterprise/SLAs; small experiments can start with OSS + community.
How do I prepare for an on‑prem or private deployment conversation with sales?
Short Answer: Come with your target environment (cloud/on‑prem), security constraints, and expected workloads so the Mastra team can map Agents, Workflows, and Observability to your infrastructure.
Expanded Explanation:
On‑prem and private deployments are about aligning Mastra’s TypeScript‑first architecture with your existing stack and controls. Before you talk to sales, it helps to know where you want to run Mastra (Kubernetes, VMs, specific cloud), how you plan to expose agents (APIs vs bundled in apps like Next.js or Express), and what your observability/storage requirements look like (e.g., self‑hosted ClickHouse, OpenTelemetry exporters).
That detail lets us skip generic slides and talk concretely about running the Mastra Workspace, configuring Observability exporters, managing MCP servers/clients behind your firewall, and handling things like file:./mastra.db not being suitable for serverless environments. You’ll get a more actionable deployment plan and clearer guidance on the right enterprise support level.
What You Need:
- Your preferred deployment model and stack (cloud/on‑prem, container/orchestration, frameworks like Next.js/Express/Hono).
- Security and compliance constraints (VPC, data residency, logging/telemetry rules) plus rough traffic and use‑case descriptions.
Why should an enterprise team talk to Mastra sales instead of just using the OSS repo?
Short Answer: If you’re betting on agents as infrastructure—needing reliability, observability, and support at scale—sales can align you with enterprise support, SLAs, and deployment patterns proven in production at companies like Plaid and Elastic.
Expanded Explanation:
The open‑source repo is enough to build powerful agents. But enterprises typically need more than code: they need help designing multi‑step workflows that won’t break under load, safe tool access via MCP with proper auth, and observability that captures token usage, tool calls, and memory operations across environments.
Talking to sales connects you to the broader Mastra offering: guidance from a team that’s been building OSS JavaScript for a decade, has raised $13m from Gradient, basecase, and Y Combinator, and ships production‑grade patterns used by teams like Plaid, Elastic, Replit, Docker, and SoftBank. You get a structured path from build/iterate into productionize/test and deploy/scale with support that matches your risk profile.
Why It Matters:
- Enterprise support and SLAs reduce operational risk when agents are customer‑facing or revenue‑critical.
- Direct access to Mastra’s team accelerates architecture decisions for agents, workflows, RAG, MCP, and observability in your environment.
Quick Recap
To talk about enterprise support, SLAs, or on‑prem deployments, contact Mastra sales via the website with your company email and a short description of your requirements. From there, we’ll schedule a discovery + demo session, dig into your stack and constraints, and propose a deployment and support model that fits how you want to run Mastra agents—as real infrastructure, not just prototypes.