Solidus Plans: Developer, Team, Business, Enterprise
These are proposed commercial packages, not final contractual prices: that is the source draft's own status line, stated here first because every plan name and price band below should be read that way. No organization is subscribed to any plan described here. This is packaging detail for an offer design, not a case study.
The plan ladder
Above the per-event pricing worked through on the economics hub, Solidus's SaaS layer is drafted as five bands:
| Plan | Price | Buyer |
|---|---|---|
| Developer | Free–$99/month | Builders, testing, hackathons |
| Team | $299–$999/month | Startups and small vendors |
| Business | $2,500–$5,000/month | SaaS vendors, marketplaces, multi-location operators |
| Enterprise | $50K–$250K/year | Telcos, fintechs, CASPs, large platforms |
| Private deployment | $100K–$500K/year | Banks, governments, strategic infrastructure |
Each row is a band, not a list price: Enterprise spans $50K to $250K/year and Private deployment $100K to $500K/year because the actual figure is meant to depend on deal-specific scope (namespace isolation, endpoint count, audit requirements), not a fixed menu item. Collapsing either into a single number would overstate how settled this draft is. A sixth line, the one-time integration sprint ($5K–$75K), sits alongside these plans rather than inside them, it prices a pilot's setup work, not ongoing access.
What the two worked packaging examples actually include
The source draft sketches two of the five bands in feature-level detail, under names that don't map one-to-one onto the price table above:
Startup package, $99/month. Sandbox plus a live verifier, 10,000 proof events included, standard proof templates, email support.
Growth package, $499/month. 100,000 proof events included, webhooks, a business console, audit export, and a vendor revenue-share dashboard.
Two things worth being exact about. First, "Startup" and "Growth" are the source's own packaging-example names: they are not identical to "Developer" and "Team" in the plan table above, even though the prices land in similar ranges. Second, and this is the caveat that matters most on this page: the free-tier proof-event quota is not a settled number. The Layer 3 plan table states Developer as "Free–$99/month" with no quota attached at all; the separate Startup package example attaches "10K proof events included" to a $99/month tier under a different name. This page is not going to paper over that gap by quietly presenting 10,000 as "the free tier's limit." It is the source draft's own figure, attached to its own named package, and the question of what a genuinely free tier includes, 100, 1,000, or 10,000 events, is an open packaging decision, not a fact this page is entitled to settle on the drafters' behalf.
The Business and Enterprise bands add custom proof templates, an SLA, team roles, compliance exports, dedicated issuer/verifier namespaces, private endpoints, custom schemas, a security review, and priority support as the price climbs: the pattern is that higher tiers buy operational guarantees (SLA, dedicated namespace, security review) more than they buy additional per-event volume, which is priced separately.
Two adjacent things this page is not
This is a packaging page, not a pricing-mechanism page for two related ideas that live elsewhere. Vendor revenue share (the 10–50% cut a distribution partner such as a POS, PMS, or telco billing system can take for carrying Solidus inside its own workflow) is a distribution deal, not a plan tier, and it has its own page at 114. Private deployment, listed above as a price band, gets the deployment-shape detail (what banks and governments are actually paying for) at 117.
What this page is not
Not a rate card in force, not a quote, not evidence that any team is running production volume on any of these plans. The plan names, the price bands, and the packaging-example feature lists are exactly what the source draft says and no more, no invented quota, no rounded single price where the source gives a range, no plan represented as sold. For the multi-check arithmetic that makes reuse worth paying for at all, see 111 and the total-cost-of-ownership Lexicon entry; for why portability rather than vendor lock-in is the point of buying any of these plans in the first place, see credential portability and verification reuse.