Cavos

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.

Dynamic is strongest as a unified login and wallet-connection layer covering many wallets and chains. Cavos is narrower and more opinionated: one device-native, self-custodial account model implemented natively per chain, currently Starknet, Solana, and Stellar.

CapabilityCavosDynamic
Primary focusEmbedded, device-native self-custodial accounts.Wallet connection and authentication across many wallets, plus embedded wallets.
Signing authoritySelf-custodial. A non-exportable device key is the signing authority; Cavos holds no key that can move user funds and uses no MPC shares.Embedded wallet keys managed by the provider’s key infrastructure with configurable custody models.
Chain coverageOne SDK with chain-native adapters. Starknet, Solana, and Stellar available today.Multi-chain, with EVM breadth and additional non-EVM support; parity varies by chain.
External wallet connectionNot a goal; Cavos provisions the wallet rather than connecting to existing ones.Core capability with broad wallet coverage.
Gas sponsorshipChain-specific: Starknet paymaster, Solana relayer as fee payer, Stellar sponsored reserves and fee bumps.Supported through account abstraction and paymaster integrations, mainly on EVM.
RecoveryNon-custodial recovery codes on every chain, multi-device passkey approval, and opt-in hardware-isolated social recovery.Provider-defined recovery and export options.

Choose Dynamic when

  • You need to support many external wallets alongside embedded ones in a single login flow.
  • Your users are existing crypto users who already hold wallets you must connect to.
  • You want extensive dashboard-level configuration of the authentication experience.

Choose Cavos when

  • Your users are not crypto-native and should never see a wallet selection screen at all.
  • You need Starknet, Solana, or Stellar accounts with the chain’s native execution model exposed and typed.
  • You require that signing authority is bound to the user’s device and cannot be reconstructed server-side.

Frequently asked

Does Cavos support connecting existing wallets like MetaMask?

No. Cavos provisions and controls an embedded, device-native account for each user. If connecting existing external wallets is a requirement, a connection-focused provider such as Dynamic is the better fit, and the two models can coexist in one product.

Which is better for non-crypto users?

Cavos is designed so a user never selects a wallet: they sign in with an identity you already own and a deterministic self-custodial account is derived. Dynamic can also hide this, but its surface area is broader because it also serves crypto-native connection flows.

Other comparisons

Evaluate it against your own requirements.

Start with the quickstart and reach a sponsored transaction on your target chain.

We use anonymous analytics to understand how developers use Cavos. No personal data is collected. Privacy Policy