Cavos, Privy, Dynamic, Turnkey, and Web3Auth are the five Dfns alternatives compared here for an embedded wallet. Each is a Dfns alternative when you want a finished SDK, or enclave signing infrastructure, instead of Dfns MPC/TSS wallet infrastructure.
The sections below use the same facts as the compare pages. Cavos publishes its own fees on the pricing page; other vendors set theirs independently. There is no Cavos vs Dfns one-to-one. The layer write-up that includes Dfns is Privy vs Turnkey. Replacement shortlists also exist for Privy, Turnkey, Dynamic, Magic, Para, and Web3Auth. Migration is a project, not a config change: wallet addresses are derived differently, so accounts do not transfer automatically.
Dfns is MPC/TSS wallet infrastructure. Official docs: key shares participate in a threshold ceremony and the private key is never reconstructed; delegated wallets keep those shares in the Dfns network, not on the user’s device; embed user wallets is that delegated path. Hybrid and on-premise signer deployments exist. That kit does not turn Dfns into a finished consumer wallet SDK.
A Dfns alternative on this page is a finished embedded wallet SDK, or signing infrastructure at a different layer: login, recovery, and Gas Sponsorship in Any Token already wired, or an enclave signing API. Cavos, Privy, Dynamic, Turnkey, and Web3Auth / MetaMask Embedded Wallets sit there. They are the usual Dfns competitors when you do not want to assemble a wallet on MPC shares. Stay with Dfns when delegated passkey wallets, hybrid signers, or a long named-network table are the product. There is no Cavos vs Dfns one-to-one. The worked layer split with Dfns is Privy vs Turnkey.
Dfns is not the weaker product. It covers ground several of these alternatives do not, especially MPC/TSS infrastructure, delegated passkey wallets, and hybrid or on-prem signers. Teams still shortlist replacements when they want a finished wallet SDK rather than infrastructure they assemble.
Dfns is wallet infrastructure: an API, policies, and MPC/TSS signers you build on. Official embed-user-wallets docs describe a delegated path, not a finished consumer SDK with login, recovery, and sponsorship already wired. Teams that want that finished SDK look past assembling one.
Dfns MPC docs describe a threshold signature scheme: key shares participate in a ceremony and the private key is never reconstructed. In the default cloud, Dfns stores all shares in its geographically distributed datacenters. Delegated wallets keep those shares in the Dfns network; they are not stored on the user’s device. Some reviews want the signing key on the end user’s device, with the vendor holding no share that participates in every signature.
Dfns publishes a long named-network table: Ethereum and many other EVM networks, plus Bitcoin, Solana, Starknet, Stellar, Sui, TON, TRON, Cardano, and Cosmos Hub, among others, with tier-1 and tier-2 feature depth. That breadth is extra surface area when the product only needs native adapters on Starknet, Solana, and Stellar.
Dfns public pricing lists Starter at $800 per year ($200 per quarter) for 10 wallets and one blockchain, Basic at $8,000 per year for 10,000 wallets and three blockchains, and Pro at $35,000 per year for 50,000 wallets. Cavos prices on wallet creates: free up to 1,000 wallets, Essential $59/mo, Complete $139/mo. Those figures are from each vendor’s public pricing page as of November 2026 and can change.
The category has consolidated. Stripe acquired Privy in 2025. Fireblocks acquired Dynamic in 2025. Consensys acquired Web3Auth in 2025 and now ships it as MetaMask Embedded Wallets. In 2026 Payward, the parent of Kraken, acquired Magic Labs wallet infrastructure.
The table below is the same shortlist used on the other alternatives pages: Cavos, Privy, Dynamic, Turnkey, Web3Auth / MetaMask Embedded Wallets, and Magic. Dfns is the incumbent, summarized in the sections that follow. They do not share a key model, the same native chain coverage, or the same pricing. Each name opens the full comparison except Cavos, which links to published fees.
| Provider | Pricing and free tier | Chains | Key model |
|---|---|---|---|
| Cavos | Free up to 1,000 wallets. Essential $59/mo. Complete $139/mo. | Starknet, Solana, and Stellar. | Device-native. One stark key from MasterDEK and app salt. No MPC. Starknet uses an audited OpenZeppelin AccountUpgradeable v3.0.0. |
| Privy | Free (0–499 MAU) with 50K signatures and $1M volume/mo. Core $299/mo. Scale $499/mo. | Broad EVM support plus Solana; coverage and feature parity vary by chain. | User wallets: 2-of-2 Shamir shares reconstituted only in AWS Nitro Enclaves (enclave share + auth share). Key export is supported. Optional custodial wallets via Bridge. |
| Dynamic | $249/mo for up to 5,000 MAUs. Then $0.05 per extra MAU. Sandbox is free. | Multi-chain, with EVM breadth and additional non-EVM support; parity varies by chain. | Embedded wallet keys managed by the provider’s key infrastructure with configurable custody models. |
| Turnkey | Pay as you go: 1,000 wallets and 25 free signatures/mo, then $0.10/signature. Pro $99/mo. | Broad cryptographic curve and chain support at the signing primitive level. | In hardware-backed secure enclaves operated as infrastructure. |
| Web3Auth / MetaMask Embedded Wallets | Free 1,000 monthly active wallets. Growth $69/mo. Scale $399/mo. | Broad multi-chain coverage. | MPC / threshold shares combined to reconstruct a private key. |
| Magic | Free 1,000 monthly active wallets and 50K signatures. $99/mo includes 2,500 MAWs. | EVM-focused with additional chain support. | Delegated key management backed by hardware security modules operated by the provider. |
| Alchemy Account Kit | Free 30M compute units/mo. PAYG $0.525 per million CUs. Gas Manager: 8% admin fee on PAYG; free on testnets. | Many EVM networks plus Solana. Bundler, ERC-20 gas payments, and Bundler Sponsored Operations are documented for those EVM networks, not for Solana. | Bring-your-own signer. Wallet APIs leave login and keys to Privy (recommended), Turnkey, Openfort, or a viem-compatible signer. |
Cavos fees are from this site. Other fees are from each vendor's public pricing page as of October 2026 and can change.
Cavos is a Dfns alternative when you want a finished embedded wallet rather than MPC wallet infrastructure. The wallet is embedded in the application. Signing authority is a non-exportable device key: keys never leave the device in plaintext, signing happens on the device, and Cavos holds no key that can move user funds. Cavos does not reconstruct a master key with MPC and cannot decrypt the MasterDEK. Recovery is a synced passkey or opt-in hardware-isolated restore in an AWS Nitro Enclave.
One SDK ships chain-native adapters for those three networks. On Starknet each wallet is an audited OpenZeppelin account contract (AccountUpgradeable v3.0.0) controlled by one stark key derived from the MasterDEK and app salt. Solana uses a native Ed25519 system account. Stellar uses a classic G-account. Recovery is off-chain: a new device restores the MasterDEK with a passkey or an opt-in hardware-isolated enclave. There is no on-chain device-signer list and no on-chain social recovery.
Cavos is not a drop-in for Dfns. Dfns is stronger when you want TSS/MPC infrastructure, delegated wallets whose shares stay in the Dfns network, or hybrid and on-prem signers. Cavos is login, recovery, and Gas Sponsorship in Any Token (USDC is one example) already wired on Starknet, Solana, and Stellar. The published free tier covers the first 1,000 wallet creates; Essential is $59/mo and Complete is $139/mo.
Embedded Starknet wallet, Embedded Solana wallet, Embedded Stellar wallet, How to Add an Embedded Wallet to a React App, Embedded Wallet API (2026): Auth, Sign, Gas, Non-Custodial Embedded Wallets: What They Are (2026), Best Embedded Wallet Providers 2026: Compared, Wallet as a Service (2026): Providers, Pricing, and Embedded Wallet Cost (2026): Privy, Dynamic.
Privy is a widely adopted embedded wallet and authentication provider focused primarily on EVM chains, offering both embedded wallets and external wallet connection.
Privy manages embedded wallet keys through its key-management infrastructure, with configurable self-custody and recovery options. Chain coverage is broad EVM plus Solana. Gas sponsorship is available through paymaster and bundler integrations, typically on EVM smart accounts. Connecting existing extensions is a core capability Cavos does not offer.
Choose Privy when the product is EVM-first, when you want a single vendor for embedded wallets and WalletConnect or injected wallets, or when you need the largest available ecosystem of integrations. Stripe acquired Privy in 2025. The public Developer free tier is 0–499 MAU with 50K signatures and $1M volume per month; Core is $299/mo and Scale is $499/mo.
Dynamic provides wallet connection, embedded wallets, and authentication tooling with a strong emphasis on multi-wallet login experiences and developer-facing configuration. Connecting existing external wallets is a core capability. Cavos provisions the wallet rather than connecting to one the user already holds. The two models can coexist in one product.
Embedded wallet keys are managed by the provider’s key infrastructure with configurable custody models. Dynamic’s public pricing page lists TSS-MPC key management as a plan feature. Chain coverage is multi-chain, with EVM breadth and additional non-EVM support; parity varies by chain. Gas sponsorship is supported through account abstraction and paymaster integrations, mainly on EVM.
Fireblocks acquired Dynamic in 2025. That is a vendor-risk and custody-stack input, not a reason to treat the products as interchangeable. Dynamic’s public Growth plan is $249/mo for up to 5,000 monthly active users, then $0.05 per extra MAU. A sandbox is available for integration testing before live mode.
Embedded Wallet vs Browser Extension: Where to Sign, and Dynamic alternatives.
Privy vs Turnkey is usually a layer question, not a feature checklist. Privy is a finished embedded wallet and authentication product. Turnkey is secure key-management infrastructure running in hardware-backed secure enclaves, exposed as a low-level API for building wallets and signing systems. You assemble the wallet experience on top of policy-driven signing primitives.
Keys live in remote enclaves, not on the end user’s device. Server-side signing, organizational policy, quorums, and approval workflows are the point of that design. Chain coverage is broad at the cryptographic-curve and signing-primitive level. Recovery is something you design on top of those primitives.
Choose Turnkey when you are building your own wallet or custody product. Choose a finished SDK when you want login, recovery, and sponsorship already wired. Turnkey’s public Pay as you go tier includes 1,000 wallets and 25 free signatures per month, then $0.10 per signature. Pro is $99/mo.
Privy vs Turnkey (2026): SDK vs Infrastructure, and Turnkey alternatives.
Web3Auth (shipped by Consensys as MetaMask Embedded Wallets after the 2025 acquisition) provides social-login wallets using multi-party computation. Key shares are split across the user’s device, the provider’s network, and recovery factors. Signing reconstructs or jointly computes a signature from those shares.
That is the clearest architectural contrast with Cavos. Cavos never reconstructs a signing key: the device derives the account key and signs. MetaMask’s product page states that Embedded Wallets use MPC with threshold signatures and Shamir’s Secret Sharing, and that export is part of the model. The same page lists native support for EVM and Solana, plus additional networks including Bitcoin and StarkNet.
Choose Web3Auth when you need very broad chain coverage from a single social-login wallet layer, or a key you can export and use in other tooling. Public pricing starts at a free Base plan with 1,000 monthly active wallets. Growth is $69/mo. Scale is $399/mo.
Ask whether you are buying a wallet product or signing infrastructure first, then where key shares live, then which chains are native.
Worked one-to-one comparisons live on the compare pages. For the category itself (what an embedded wallet is, and how embedded wallets vs browser extensions, MPC, and device-native models differ), start with embedded wallets and the embedded wallet SDK. The embedded wallet guide is that page.
Dfns is the better pick when you want MPC/TSS wallet infrastructure, delegated passkey wallets, or hybrid and on-prem signers. It is not the weaker product; it covers ground Cavos does not. Stay with Dfns when the following are true.
There is no single best Dfns alternative. The right pick depends on whether you want wallet infrastructure or a finished SDK. Cavos is the alternative when the product is on Starknet, Solana, or Stellar and the review requires a device-native key. Privy is the more mature finished auth and wallet product across EVM. Dynamic is stronger when you must connect wallets users already hold. Turnkey is the closer infrastructure comparison (enclaves rather than MPC). Web3Auth / MetaMask Embedded Wallets fits broad social-login chain coverage. Dfns itself remains the better pick when you want MPC/TSS infrastructure, delegated passkey wallets, or hybrid and on-prem signers.
Yes. Cavos is free for the first 1,000 wallet creates, then Essential at $59/mo and Complete at $139/mo. Web3Auth / MetaMask Embedded Wallets starts free at 1,000 monthly active wallets. Turnkey’s Pay as you go tier includes 1,000 wallets and 25 free signatures per month. Privy’s own Developer free tier is 0–499 MAU. Dfns public Starter pricing is $800 per year for 10 wallets and one blockchain. Those figures are from each vendor’s public pricing page as of November 2026 and can change.
Cavos ships native adapters for all three: an audited OpenZeppelin account contract on Starknet, a native Ed25519 system account on Solana, and a classic G-account on Stellar. The OpenZeppelin audit covers that contract, not Cavos. Dfns names Starknet, Solana, and Stellar on its supported-networks table; feature depth follows that table’s tiers. MetaMask Embedded Wallets lists EVM, Solana, and additional networks including StarkNet; feature parity still varies by chain.
No. They sit at different layers. Dfns is MPC/TSS wallet infrastructure: delegated wallets, policies, and optional hybrid or on-prem signers. Cavos is a finished embedded wallet SDK: auth, a device-native account, passkey or Nitro Enclave sealed restore, and Gas Sponsorship in Any Token. Wallet addresses are derived differently, so accounts do not transfer as a config change.
Infrastructure. Official docs describe threshold signatures, delegated wallets whose shares stay in the Dfns network, and an embed-user-wallets path. That is closer to Turnkey than to Privy. You still assemble auth, approval UI, and chain adapters. Recovery is something you implement; Dfns documents that it cannot restore a wallet if the only passkey is gone.
If you want a finished embedded wallet instead of Dfns MPC infrastructure, the usual shortlist is Cavos, Privy, Dynamic, Turnkey, and Web3Auth / MetaMask Embedded Wallets. Turnkey is the closer infrastructure comparison. Cavos is the comparison when the product is on Starknet, Solana, or Stellar and the review requires a device-native key. There is no Cavos vs Dfns one-to-one page; start at compare, or at Privy vs Turnkey for the three-way with Dfns.
No. Official Dfns MPC docs describe a threshold signature scheme: key shares participate in a ceremony and the private key is never reconstructed. That is not the same as a device-native key. In the default cloud, Dfns stores all shares in its datacenters; delegated wallets are not stored on the user’s device. Cavos also never reconstructs a signing key: the device derives the account key and signs.
Start with the quickstart, or talk to us about a production integration.
We use anonymous analytics to understand how developers use Cavos. No personal data is collected. Privacy Policy
