Six teams.
Direct line to engineering.
Founding pricing forever.
Six engineering teams running blastmap against repos that matter. Real production use. Weekly 30 minutes with the people writing the code. Founding-customer pricing locked for the life of the company. We close cohort zero when we close it.
One seat filled. Five open.
Cohort zero is six slots. The first partner is on board. The remaining five close as we find the right shape of team for each.
From install to incident, what the first month looks like.
We install in your VPC together. Your code never leaves. By end of the call you are walking a live graph of your services with confidence on every edge.
PR comments start landing on real merges. The first time the bot flags a downstream consumer you would have missed, the conversation about this product changes inside your team.
Runtime overlay is wired. The static graph becomes a live twin. Drift between staging and prod is named. The first incident the model scopes faster than your on-call rotation is the moment cohort zero pays for itself.
Weekly 30 minutes for the first six weeks. Shared Slack channel after. Things you need by Tuesday move to the top of the queue if we can justify them to the rest of the cohort.
What we ask for. What you get.
- Real production use.
Run blastmap against repos that matter, not a sandbox. Real complexity is the only thing that sharpens the product.
- Weekly 30 minutes for six weeks.
We watch you use it, you tell us where it lies to you, we ship the fix the next release. After six weeks, it shifts to async.
- Honesty over politeness.
If the bot says something stupid, tell us. If the docs confuse, tell us. Politeness wastes the cohort.
- Tolerance for v0.x scars.
Things will break. The MCP tool list will change. The graph schema will migrate. You are getting in before the polish.
- Founding-customer pricing forever.
Whatever the managed offering ends up costing, you will never pay more than the cohort-zero rate. Locked for the life of the company.
- Direct line to engineering.
Shared Slack channel. No support tier. Your bug report goes to the person who wrote the code.
- Roadmap influence.
Things you need by Tuesday move to the top of the queue if we can justify them to the rest of the cohort. You are explicitly building this with us.
- Public credit, only if you want it.
A case study, a quote, a launch-day shoutout. Only on your terms. Opt-in, not opt-out.
The shape of a great cohort-zero partner.
- 15 to 100+ microservices spread across multiple repos and orgs.
- Bitten by at least one cross-service regression in the last six months nobody could have caught manually.
- Already using AI coding agents that do not know what they do not know about your architecture.
- A staff engineer or platform lead with authority to install something inside your VPC without a six-week procurement cycle.
- Read the manifesto and nodded.
- Single-repo team with no cross-service complexity yet.
- You need SOC 2 today. Honest answer: that is post-revenue for us.
- You want a polished v1. We are shipping a sharp v0.
- You want a managed-cloud install. Not in v0.1.
- You cannot tolerate the schema migrating under you twice in a month.
Five fields. A real human reads each one.
No screening call required to apply. We respond within 48 hours, even if it is a 'not yet'.