We've integrated and partnered with a number of great technology companies this past year. Most start the same way: an engineer on the partner side wants to build an integration, files a PR, and we work it out from there. Here's how to get started.
Step one: ship an integration
Partnership begins with submitting a PR for the integration. A handful of related artifacts go alongside it. Most teams finish step one in under a week.
- Working integration. Either a PR into the Mastra monorepo as
@mastra/<yourproduct>, or a maintained package in your own repo. - Public repo. Integration example developers can clone.
- Blog post on your site. Tutorial, announcement, or use case.
- Docs cross-listing. We document you in our docs; you document us in yours.
MongoDB contributed @mastra/mongodb directly. Elastic shipped @mastra/elasticsearch. Public partner repos include elastic/mastra-elasticsearch-example, render-examples/ravendr, brightdata/brightdata-mastra-tools, and CopilotKit/with-mastra. For partner-side launch posts see Elastic, ravendr, WorkOS, and Bright Data; and for docs cross-listing examples, see Arcade, MongoDB Atlas, CopilotKit, Assistant UI, Bright Data, and Firecrawl.
Step two: co-market the launch
From here we add a shared event and a few co-marketing commitments alongside the integration. Render and AssemblyAI built ravendr, a voice research agent with Mastra at the agent layer, and co-authored the launch on AssemblyAI's blog. Bright Data went a similar route: a dedicated tutorial post on the integration, their AI frameworks roundup adding Mastra in April, and a joint case study in motion now. CopilotKit led with the shared event: the CopilotKit/with-mastra integration paired with a joint workshop on building browser-based TypeScript agents, and a Mastra section in their docs.
One shared event (pick at least one):
- Joint webinar or live stream
- Conference co-presentation
- Episode on the Agent Hour podcast
- Co-sponsored developer meetup
- Internal enablement session at each other's SKO
Pick at least three more:
- Social announcement on both sides at launch
- Guest post on the Mastra blog (we handle the PR)
- Joint case study with a shared customer
- Starter template or quickstart developers can clone
- Shared Slack channel between teams
- Named engineering contact on your side who owns the integration
- Featured listing on Mastra's partner directory
- Logo and brand copy exchanged on both sides
Step three: sell together
For when we decide to go to market together. Mastra runs inside your product as default or native, mutual referrals flow both ways, and there's a quarterly business review on the calendar.
- Formal mutual referral process. When your users need agent infrastructure, you point at us; when our users need what you do, we point at you.
- Monthly or quarterly business reviews. Regular check-ins on integration health, co-marketing pipeline, and mutual referral activity.
If you want to be next
If you're already building an integration, ship it. Put it in a public repo, write up what you shipped on your blog, and put us in your docs. We'll work to list you in ours if it makes sense.
For everything beyond that — a joint case study, a co-authored post, or an event together — reach out to ashwin@mastra.ai.
The Mastra docs are where every adapter is documented, and the reference lists what we already integrate with: vectors, storage, voice, auth, deployers, and tools.
Happy building!
