Per-client minimums
A minimum per tenant makes a fifteen-host client impossible to serve, however much they need it.
For MSPs and MSSPs
Segmenta was built multi-tenant from the start, because it has always run several organisations from one deployment. One console, every client, billed per host across your whole book rather than per contract.
The problem
An MSP with thirty clients averaging fifteen hosts cannot buy enterprise microsegmentation. Every tenant would need its own contract, its own minimum, and its own console. So MSPs sell EDR and backup, and simply do not offer segmentation — even though their clients are exactly the organisations that get destroyed by lateral movement.
Per-client minimums
A minimum per tenant makes a fifteen-host client impossible to serve, however much they need it.
A console per client
Thirty separate tenancies, thirty logins, and no way for your NOC to see across them.
Nothing to hand the client
Segmentation is invisible when it works, which makes it a hard line item to justify at the quarterly review.
What you get
The multi-tenancy is not a feature we bolted on for the channel. It is how the product has always worked.
Each client's flows, hosts and policy live in their own schema — not filtered in application code. A query that forgets its tenant returns nothing, rather than returning another client's fleet.
One operator account, a tenant switcher, and per-tenant permissions. Your NOC works across the book from one place.
Every client is billed at the same per-host price on one monthly invoice, so a fifteen-host client costs you the same per server as your largest, and nothing is priced per contract.
An agent's certificate encodes the tenant it belongs to. A client's host cannot report into, or receive policy from, another client's tenancy.
The commercial shape
Published like everything else. Partners pay 75% of the published price, and that applies on top of the founding rate. No tiers, no deal registration, nothing to negotiate.
How it's counted
Total hosts under management
Across every client tenant, not per contract. One price at every size, so a small client is never priced as if alone.
What you pay
A$11.25 / server / month
25% off the published price. That's A$11.25 a server while a client is on the founding rate, and A$15 after it.
What you sell
Yours · you set the client price
We don't publish a recommended retail price or sell against you into your own accounts.
The wedge
Segmentation is invisible when it works, which makes it a hard line item to defend. A blast-radius review turns it into a conversation: here is what one compromised machine could reach in March, here is what it can reach now.
Questions
What we can commit to today, and what we can't.
Not a separate one. You use the same console with a tenant switcher, which is how the product has always worked for multi-tenant operators. If you need something the switcher doesn't do, tell us.
The console is Segmenta-branded today. Each client's evidence pack exports from their own tenant for the quarterly review: one PDF of protection per host, critical systems, every published rule and the period's approvals. It carries Segmenta's name, not yours. Full white-labelling is not something we can promise, and we would rather say so than string you along.
Not into accounts you manage. If one of your clients approaches us directly we will tell you.
Billing is monthly on hosts under management, so their hosts simply come off your count. You are not holding an annual licence for a client who has gone.
More than any partner book we have run. We will give you a straight answer about the scale we have actually tested rather than a marketing number — ask.
How many clients, roughly how many hosts, and what you sell them now. We'll come back with what your book would cost.