Know what you're paying for. And what you aren't.
There is no markup on your cloud bill here, and there is no per-seat tax. You pay once to get connected, a predictable subscription to stay governed, and your own cloud costs — passed through, untouched.
Three parts, not one number you have to trust.
Every quote breaks down into what it cost to get you connected, what it costs to stay governed, and what your cloud vendor was always going to charge you anyway.
Onboarding, once
Your cloud accounts connected, your rules configured, your first services brought under management, your team set up. Paid once and finished — it does not reappear on later invoices as “implementation”.
Subscription, recurring
Sized to what you actually bring under management and what you actually turn on. It tracks your footprint, not your headcount — so growing the team does not grow the bill.
Cloud costs, at cost
Your cloud bill is your cloud bill. We pass vendor spend through untouched. We do not mark it up, and we do not resell it back to you.
Per-seat pricing punishes the thing we want you to do.
The whole point is that infrastructure requests stop being funnelled through two senior people. Charging you for every additional person who can ask would put our incentives directly against yours.
The same logic rules out reselling your cloud spend. If we made money on your bill going up, you could never fully trust a recommendation about cost — and cost is one of the things we are checking on your behalf.
So the bill tracks what you have under management. Nothing else.
You already pay your cloud vendor. You should not also pay us to mark it up.
Intentric pricing philosophySized to what you actually run.
There is no public price list yet, because pricing an early platform from a table would mean quoting you something that does not fit. These are the things a quote is built from.
| Factor | What it means |
|---|---|
| Footprint | How much infrastructure you bring under management — the primary driver, and the one you control. |
| What you turn on | Ongoing drift checking, proposed corrections, and the depth of record-keeping you need. |
| Environments | How many separate environments carry separate rules and separate stakes. |
| Organizational needs | Single sign-on, automated user provisioning and role structure for larger teams. |
| Support | What response you need, and whether you want us in the room during your rollout. |
| Team size | Nothing. It is not a factor, and we are not going to make it one later. |
Things worth asking before a quote.
Why isn't there a price on this page?
Because we would have to make it up. We are early and pricing against real environments rather than a table we invented. You will get a specific number, with its parts broken out, after a short conversation about what you run.
What does the onboarding fee actually buy?
Getting you genuinely running: accounts connected, your rules configured to match how your organization already approves things, your first services under management, and your people set up with the right access. It is finite work and it is billed once.
Will the subscription move if our footprint grows?
Yes — that is the point of tracking footprint. It moves with what you bring under management, predictably and in a direction you can see coming, rather than by surprise at renewal.
Are there early-partner terms?
Yes. Working with us this early means real influence over what gets built, and the commercial terms reflect that. We would rather discuss it directly than publish something that ages badly — see the design partner program.
What happens if we leave?
You export your infrastructure code and keep running it. It is standard and it does not need us. You stop paying the subscription; you do not lose the estate.
Get a quote sized to your environment.
Tell us roughly what you run and what you would bring under management first. We reply within one business day with the parts broken out.