Private Deployment: What Banks and Governments Actually Pay For
The figure below is a proposed commercial package, not a final contractual price: Solidus's own pricing draft says so of itself, and this page repeats it rather than bury it. And the concession that matters most on this specific page, stated before anything else: no bank, no government, and no private deployment of any kind exists. Nobody has piloted this package, signed a letter of intent for it, or paid a dollar toward it. What follows is a price on a shelf, not a receipt.
The number and who it's for
Solidus's pricing draft lists a Private Deployment tier at $100K–$500K/year, with the buyer named plainly: "Banks, governments, strategic infrastructure." It sits above the Enterprise tier ($50K–$250K/year, for telcos, fintechs, CASPs, and large platforms) in the same table, priced higher because the buyer and the deployment model are different, not because more has been built for it.
| Plan | Price | Buyer |
|---|---|---|
| Enterprise | $50K–$250K/year | Telcos, fintechs, CASPs, large platforms |
| Private deployment | $100K–$500K/year | Banks, governments, strategic infrastructure |
The draft's own stated rationale for a tier like this existing at all is one of its six pricing principles: "charge enterprises for audit, SLA, private deployment, and compliance support." That's the honest frame: this is a price for a category of buyer with categorically different requirements (data residency, dedicated infrastructure, a compliance posture Solidus doesn't need to build for a startup customer), not a markup on the same product.
What it would include, borrowed, not invented
The source document doesn't itemize a separate feature list for Private Deployment. What it does itemize is the Enterprise package's feature set, and Private Deployment is priced above Enterprise in the same table, so the honest thing to say is that Private Deployment's likely scope draws on the Enterprise list, not that Solidus has a bank/government-specific feature set already defined:
- Dedicated issuer/verifier namespace
- Private endpoints
- Custom schemas
- Security review
- Compliance documentation
- Priority support
Anything beyond this, on-prem validator nodes, HSM-backed key custody, dedicated committee seats, data-residency guarantees, is a plausible future scope for a package at this price point, but it appears nowhere in the current pricing draft, and this page won't invent it to make the tier sound more built-out than it is.
Why nobody can buy this today, regardless of price
No third party has reviewed this codebase. The chain a buyer would be trusting runs on a four-node development committee operated by the project itself, not the 21-of-100 validator set the consensus design specs: a spec and a running deployment are different things, and /status exists partly so that distinction never gets blurred.
The regulatory gap is wider than the engineering one. The regulatory surface Solidus concedes lists it item by item: no Travel Rule product, no AML or sanctions/PEP screening, no eIDAS or QTSP status, no certification of any kind in any jurisdiction.
What would have to be true first
A real private-deployment customer would need, at minimum, an external security audit behind the code it's trusting, a validator committee that isn't run entirely by the project, and a compliance record that answers the gaps 105 lists honestly instead of leaving them open. None of that has a committed date. What this page can say is narrower: the $100K–$500K/year figure is a placeholder for a future package, priced to reflect what a bank or government buyer would eventually need, not a quote either of them could act on this quarter.
For the pricing draft's full shape, the protocol floor, the vertical event pricing, the rest of the SaaS tiers, see How Solidus Prices Identity Verification. For the standing engineering state this page draws its concession from, see /status. For total cost of ownership and vendor lock-in (the two metrics a real enterprise buyer would actually weigh against this price) see the Lexicon.