Founding 20 · design-partner programme
DevOps AI ToolKit for teams
Everything in Pro, made shared. The prompts that work for your stack, the incident analyses somebody already ran, and the troubleshooting session your colleague started at 2am — visible to the whole team instead of trapped in one person’s account.
We are taking 20 founding teams. Founding members get the price locked for the life of the subscription and a direct line to the person building it — and in return we expect to hear when something does not work.
20 of 20 places remaining
What a team seat adds
Pro is built around one engineer. These are the surfaces that only make sense with more than one.
Shared prompt library
Your team’s own prompts, versioned and searchable, alongside the public library. The ones that work for your stack stop living in someone’s notes.
Shared saved analyses
Incident reports, code reviews and monitoring packs are visible to the whole team, so the person on call at 3am can read what was done last time.
Team troubleshooting workspace
Sessions started by one engineer can be picked up by another, with the commands already run and the outputs already captured.
Shared academy progress
Onboarding tracks with visible completion, so "get up to speed on our Kubernetes setup" becomes a checklist rather than a conversation.
An onboarding session
A working session to set the team up properly — shared library seeded, tracks assigned, integrations connected.
A direct feedback channel
The point of a founding cohort. You get early access; we get to build against real teams instead of assumptions.
Who this is not for
- · Teams that need SSO, SCIM or a signed DPA today. Those are not built yet, and saying otherwise would waste your time.
- · Anyone who needs a finished, stable product. A founding cohort means rough edges you will be asked about.
- · Teams larger than about 25 engineers — the shared surfaces have not been tested at that scale.
If that rules you out, Pro is available now with no waiting, and consulting covers one-off engagements.
Apply to the Founding 20
A person reads every one of these. The last question is the one that matters most.
Application received
A real person will read it and reply, usually within a couple of working days — either with a scheduling link or a straight answer that it is not a fit yet.
In the meantime, Pro is available now, and My Toolkit works on a free account.
Questions
Why is the price a range?
Because the scope is genuinely still being set with the first cohort, and quoting a precise figure we have not committed to would be a fiction. The range reflects team size and which integrations you need. Whatever you join at is locked for the life of the subscription.
What does "founding" actually mean?
That you are shaping the product rather than receiving a finished one. You get early access and a direct line to the person building it; in exchange we expect you to tell us when something does not work. If you want a mature, stable Team tier, waiting is the honest recommendation.
How many engineers does a team seat cover?
The founding cohort is designed around 5-10 engineers. Smaller teams are welcome, and larger ones are possible but the shared surfaces have not been tested at that size yet — which is worth saying plainly rather than discovering together.
What happens after I apply?
A reply from a person, usually within a couple of working days, either with a scheduling link or with a straight answer that it is not a fit yet. There is no automated drip sequence and no sales call you have to sit through to get pricing.
Is my data shared with the rest of my team automatically?
No. Shared surfaces are explicit — you choose what goes into the team library. Personal saved work stays personal unless you share it, because the alternative makes people stop saving things.