One integration surface
Authentication, wallet state, recovery, and sponsorship share a consistent product-level API.
Choose the wallet model, not just the login modal.
Cavos is device-native and chain-agnostic: one product integration, with an explicit adapter for each blockchain. Compare that model with hosted key networks and traditional wallet extensions. The licensing consequences of holding user keys are cited on the custody page. For the category itself (what an embedded wallet is, and how extension, MPC, and device-native models differ) start with embedded wallets and the embedded wallet SDK. The embedded wallet guide is that page.
| Capability | Cavos | Hosted embedded wallets | Wallet extensions |
|---|---|---|---|
| Signing authority | An account key derived on the user's device from a MasterDEK that only their devices can open | Provider-specific key management or MPC model | A key managed in a separate wallet application |
| Chain strategy | One SDK with chain-native adapters | Network coverage and account model vary by provider | Coverage depends on the wallet and installed networks |
| Current Cavos coverage | Starknet, Solana, and Stellar | Varies by provider | Varies by wallet |
| User experience | Embedded directly in the product; no wallet extension | Embedded directly in the product | Users install, open, and approve in another application |
| Gas sponsorship | Gas Sponsorship in Any Token via chain-specific paymaster and relayer integrations | Varies by provider and network | Usually funded by the user or a separate paymaster |
| Recovery | Device authorization and non-custodial recovery factors | Provider-defined recovery | Seed phrase, passkey, or wallet-specific recovery |
Why the adapter model matters
Native where it counts
Address derivation, signatures, execution, and fees remain explicit and correct for each blockchain.
Built beyond three chains
New adapters can join the same interface without pretending every blockchain has the same account model.
Compare with a specific provider
Each page covers custody, chain support, signing authority, sponsorship, and recovery, including the cases where the other provider is the better choice. Teams comparing replacements can start with Privy alternatives, Turnkey alternatives (a turnkey alternative list of Turnkey embedded wallet competitors) , Dynamic alternatives, Magic alternatives, Para alternatives, Web3Auth alternatives, or Dfns alternatives. For a single pricing, chain, and key-model table of the same vendors, see Best Embedded Wallet Providers 2026: Compared. The product-shape fork (when users should sign in an embedded wallet vs a browser extension) is a separate guide. Platform parts and pricing models are in wallet-as-a-service. The method-level surface is the embedded wallet API.
Cavos vs Privy
Privy is a widely adopted embedded wallet and authentication provider, offering both embedded wallets and external wallet connection. Privy’s chain-support docs list managed send on EVM, Solana, Tempo, and Tron, and sign-only support on chains including Stellar and Starknet. This page is the one-to-one Privy vs Cavos comparison.
Cavos vs Dynamic
Dynamic provides wallet connection, embedded wallets, and authentication tooling with a strong emphasis on multi-wallet login experiences and developer-facing configuration.
Cavos vs Turnkey
Turnkey provides secure key management infrastructure running in hardware-backed secure enclaves, exposed as a low-level API for building wallets and signing systems.
Cavos vs Web3Auth
Web3Auth provides social-login wallets using multi-party computation, splitting key shares across the user’s device, the provider’s network, and recovery factors.
Cavos vs Magic
Magic offers embedded wallets and passwordless authentication, historically known for email magic-link login and a delegated key management model backed by hardware security modules.
Cavos vs Alchemy
Alchemy Account Kit (v4), including its embedded wallets, signer support, and key management, is deprecated. Alchemy now ships Wallet APIs as a signer-agnostic transaction layer and recommends Privy or another provider for login and keys.
Frequently asked
What makes Cavos different from hosted embedded wallets?
Cavos makes the user’s device the signing authority. The device key is non-exportable, Cavos does not reconstruct it with MPC, and each chain adapter uses the chain’s native account and transaction model.
Which blockchains does Cavos support?
Cavos currently ships adapters for Starknet, Solana, and Stellar. The SDK is designed around a chain-adapter interface so additional blockchains can be added without changing the product-level integration model.
Does Cavos use MPC?
No. Cavos does not split or reconstruct a master key with MPC. Signing authority stays with device-bound keys.
Can one application use Cavos across multiple chains?
Yes. Applications use the same Cavos.connect entry point and select a chain and network. The returned wallet is a typed, chain-specific object so native transaction behavior stays explicit.
Build the first wallet on your target chain.
Start with the unified SDK, then follow the native guide for each adapter.