This page is the shape of how KeyFlux is priced. The numbers come from a conversation, because a national identity programme and a DevOps team landing REMIT Cloud are not the same purchase. The shape does not change between them.
Three dimensions: tier, modules, volume.
Talk to us about pricingNothing else moves the number. If a quote ever contains a line you cannot map onto one of these three, ask us to explain it.
Your integration surface.
What you connect, and at what scale. A national issuance programme and a bank deriving credentials from a state ID integrate differently, so they sit at different tiers. Tier is about the surface you take on, not about which features get withheld.
Optional capability on top.
Base tiers do not include everything. A module earns a line only if you would genuinely decline it and it costs real money to deliver. If you would never turn it off, it belongs in the tier and we put it there.
Multiplies.
You pay in proportion to the decisions you make. Credentials issued, eligibility decisions returned, authorisations granted. Usage that costs us nothing costs you nothing.
These are the capabilities priced on top of a base tier. The test is simple: a module earns a line only if a customer would decline it.
Cross-border and cross-issuer trust routing.
Signing and the secure file vault for signed documents, on the holder side of the wallet.
The customer-facing identity surface over a derived credential.
Kubernetes is in the base. Each further target class is priced as a module, because each one is real integration work.
The first rail is in the base. Each further rail adapter is priced as a module.
Eligibility over a verified credential is not an add-on to the product. It is the product. Nobody buys an eligibility engine and then pays extra for the eligibility decision.
These are not policies we would quietly drop in a large deal. They are part of what the product is.
Your team size is not our business model. Adding a reviewer, an engineer or an analyst does not change what our software does, so it should not change what you pay. Per-seat pricing quietly punishes you for giving more people visibility into your own trust decisions, which is the opposite of what we want.
REMIT is not a rail. It authorises, it does not settle, and it never takes custody. Transact is priced as a platform fee plus authorised transactions, flat. The moment an authority layer prices like a payment network it starts optimising for the wrong thing, and it invites a licensing question nobody asked for.
Self-hosted means the software runs in your own tenancy or your own data centre. SaaS means we run it. REMIT Transact is a hybrid of the two by design: a self-hosted authority plane with a hosted mediation and receipt service, sold as one product, because the authorisation leg has to be mediated for the receipt to be worth anything.
Sovereignty is a separate claim from deployment. It is about who holds jurisdiction over the keys and the data, and we only make the claim where it is actually true.
Cloud is hosted SaaS scoped to CI/CD integration for DevOps pipelines. The community tier is a real tier, not a trial with a timer on it. Start with one pipeline, on your own, without a procurement cycle.
Cloud imports the spine core rather than reimplementing it, so what you enforce on the free tier is the same engine that runs self-hosted in a cluster. Nothing has to be rebuilt when the rest of the organisation catches up.
Four things. It takes one call, and you will leave it with a number rather than a brochure.
We will walk you through it live, then price it against the shape on this page.