Your capacity. Their shortlist. One integration.
Sencai customers choose where each workload runs - from inside the product, in the same step where they provision it. Eleven providers are in that list today. If yours isn't, you're not losing the comparison; you're not in it.
The decision happens inside the product
Teams don't pick a provider from a comparison article. They pick one from a list, in the same step where they're already provisioning, with regions and options side by side. Being in that list means being considered. Being outside it means the evaluation ends before your name comes up.
European buyers - and where we are today
Sencai is built for European companies working under NIS2, GDPR and sector rules that push workloads into EU jurisdiction, and sometimes rule out US hyperscalers entirely. Those buyers want a European option they can name and defend to a reviewer - and they choose it at the moment they provision, from the list in front of them. A provider in that catalog is in the evaluation; a provider outside it never enters the comparison at all.
You keep the account and the customer
Sencai runs on a bring-your-own-cloud model: the customer signs up with you, keeps their own account, and holds the billing relationship directly. We store their credentials encrypted and act on their behalf. We also discover what a customer already runs with you and let them bring it under management as it stands - so an integration reaches your existing customers, not only new ones.
The customer's controls extend over your infrastructure
Whatever a customer has set up in Sencai applies the moment they add your cloud: roles and organisation boundaries, a tamper-evident audit trail of every action, cost tracking with spend caps, and the evidence their compliance reviewers ask for. For the operations Sencai covers, you don't need to ship an enterprise access model or an audit log of your own to be evaluated alongside a hyperscaler.
What integration involves, and what it costs
We build and maintain the integration against your public API: provisioning and the instance lifecycle, discovery of what a customer already runs with you, and - where your API supports it - networks, firewalls and DNS. From you we need API documentation, a test account and one technical contact; the engineering is ours, the review is yours. It's a paid partnership covering integration work and ongoing maintenance, not an advertising slot, and terms depend on how much of your API we cover - so it starts with a technical conversation, not a price list.
Get your cloud into the catalog
Tell us where you operate and what your API exposes. We'll come back with integration scope and partnership terms.