Cheapest embedded wallet provider for each app size, from published prices

13 embedded wallet vendors, three usage profiles and three app sizes, plus a calculator over any size from 100 to 1,000,000 monthly active users. For each combination the harness applies the vendor's own billing rules: what it meters (active users, signatures, wallet operations, credits), what each plan includes, its graduated overage, its caps and where its published price stops. It reports the monthly bill on the cheapest plan that can serve the app, and says so when none can. Pricing is read by a human from each vendor's own page, not scraped: half of these pages render their billing FAQ only in JavaScript. Every figure records the page and the date, and the harness re-hashes the pricing lines of all thirteen pages each hour, and a change that holds for six hours raises an alert for a maintainer to re-read the page. The calculator reads a curve the same harness emits, with a point at every plan boundary, and a second implementation in another language re-prices it at 1,170,000 random app sizes; `pnpm validate` re-runs it on a 78,000-size sample on every change.

• ·Cohort. Thirteen vendors with a self-serve price on a public page: Privy, Dynamic, Turnkey, Web3Auth, Magic, Para, Coinbase CDP, thirdweb, Openfort, Circle, Reown, ZeroDev and Crossmint. Alchemy, Portal, Dfns, Fireblocks, Sequence and Particle Network are listed below with the reason they cannot be priced.
• ·Profiles. A consumer app whose users send 5 transactions a month and 20% of whom are new each month, an active app at 25 and 10%, a trading app at 100 and 5%. One wallet per user. A transaction is one signature followed by one broadcast; sign-in signatures are not counted, and Magic says they are not billed.
• ·Units. Each vendor's own meter is written as a linear function of the app: Privy and Magic bill active users plus signatures, Turnkey signatures, Coinbase CDP and Openfort wallet operations (1 per new wallet, 2 per transaction, from their own tables), ZeroDev credits (10 per signature, 20 per UserOp, so 30 per transaction), and the rest active users or active wallets.
• ·An active user is not one thing. Privy counts a user with a session in the last 30 days, Dynamic a login or a wallet created that month, Web3Auth and thirdweb a login, Magic a wallet accessed through its SDK, Para a user authenticated or created, Circle a wallet that made an on-chain transaction. Every user in these profiles transacts, so all of them count everyone.
• ·Plans. Each plan's fee, what it includes and its overage are applied as published. Graduated rates (Circle, thirdweb) bill each band at its own rate. A plan that stops at a size (Para's free 1,200 users, Reown's free 500, Turnkey's 2,000 wallets) cannot serve above it. Turnkey's limit counts every wallet an organisation holds while this model counts one month's users, so a growing app reaches it sooner than the calculator shows. A size past the last published price is a quote and is not ranked.
• ·Readings. Where a page can be read two ways the catalogue says which reading is priced and the calculator badges the plan. Privy's $2,000 pay-as-you-go base is priced alone, though its $499 Scale fee may also apply, and at exactly 10,000 users Privy is priced on Scale ($499) because pay-as-you-go starts above 10,000, though its Scale card reads 2,500 to 9,999; the other reading is $2,000. Turnkey's $99 Pro fee is priced as a floor the per-signature charges count against.
• ·Openfort's operation table gives 1 per wallet created and 2 per transaction, but its own simulator also adds 2 per active user; on that reading its bill is higher and it can drop a place, as the findings spell out for the 10,000-user consumer view. ZeroDev's 30 credits a transaction assumes each transaction is one signature and one UserOp. thirdweb's bands above 100,000 users are priced band by band.
• ·Vendors' own exclusions are honoured. Reown says exchanges, custodians, payments, gaming and merchant platforms need a custom plan, so its self-serve price is not offered on the trading profile.
• ·Left out. Gas and gas-sponsorship surcharges (thirdweb 2.5% on mainnet, Openfort 10% or 5%, ZeroDev 8%), SMS fees, extra seats, annual discounts, Circle's USDC rebate, and Privy's $1M monthly transaction volume threshold. Features a production app may need are not priced: removing thirdweb branding needs its $499 Scale plan, and custom domains are Enterprise-only at several vendors.
• ·Any size, not only three. The table prices 1,000, 10,000 and 100,000 users because a metric needs a fixed label. The calculator prices any size from 100 to 1,000,000 from a curve the same harness emits, with a point at every tier boundary, cap, quote threshold and plan crossover. Between two points every bill is a straight line, so the slider is exact, not smoothed.
• ·Verification. A second implementation, written in another language from the catalogue's prose rather than the harness code, re-prices every curve point and 1,170,000 random app sizes, and agrees on the bill to the cent and on the plan in every case. `pnpm validate` re-runs it on a 78,000-size sample on every change, and refuses a curve built from a different catalogue.
• ·Freshness. Six of the thirteen pages return a new body on every request while their prices stand still, so the harness hashes only the visible lines that carry a dollar figure or a number beside a billing word. A change that holds for six hours raises an alert, and a maintainer re-reads the page and corrects the catalogue. The page shows the catalogue date.