You'd be one of the first. We're not going to pretend otherwise.
This is the page where most companies at our stage show a wall of logos they have no right to. We do not have customers to name yet, so we are not going to imply we do. What we have is a small design partner programme, and a genuine reason to be in it early.
Closer than a later customer will ever get.
Adopting infrastructure tooling early is a real risk and we are not going to talk you out of feeling that. What you get in exchange is access that stops existing the moment we have a customer base.
Design partners talk to the people building this, not to an account manager relaying it. What you ask for changes what gets built next — not as a gesture, but because at this stage your requirements are the roadmap.
That is true now. It will not be true in two years, and we would rather you take advantage of it while it is.
What that means concretely
- Direct access to the people writing the software, not a support tier
- Your requirements shape what gets prioritized, visibly
- Onboarding done with you rather than handed to you as documentation
- Commercial terms that reflect the risk you are taking on
- A straight answer about what is shipped and what is not, every time you ask
Being first should not mean being a test subject.
Early access to an unfinished product is a fair thing to be nervous about. Early access to unfinished controls is not, so those are not the part we ask you to tolerate.
Rules from day one
Your limits on spending, regions and destructive changes apply to your first request, not to a later release.
You approve everything
A named person on your team authorizes every change. This is not a setting we enable for mature accounts.
Verification, not a demo
What runs is checked against what you asked for. The checking is the product, not a feature scheduled for later.
A record from the first change
Who asked, who approved, what happened — recorded from your first request onward, and exportable.
Questions we would ask in your position.
None of these are unwelcome, and you should not have to work up to them.
- What is genuinely shipped, and what is on a slide?
- What happens to our infrastructure if you go away?
- Who else is using this, and can we talk to them?
- What have you got wrong so far, and what did you change?
- What would make us a bad fit for this?
Two of those, since you'd ask anyway.
If we go away: you keep the infrastructure. What we produce is standard, inspectable code that runs without us, and you can export all of it at any time. You lose the workflow. You do not lose the estate.
What is shipped: AWS, completely. Azure is built but not yet selectable. Google Cloud is not built. We put that on its own page rather than burying it, because that is the answer that decides whether we are worth your time.
The version of us you meet now is the version that will still take your call in a year.
Why design partners work with us earlyHelp decide what this becomes next.
Tell us what you run and what you would want under management first. If we are not a fit yet, we will tell you that instead of selling you a pilot.