Embedded wallets users never have to manage

Email, social, or passkey login spins up a non-custodial wallet in under 100ms — backed by open-source, self-hostable key management. One SDK across EVM and Solana.

No credit card required • Free testnet accounts


1M+
wallets created
10M+
transactions
<200ms
signing speed
99.99%
uptime

Walletconnected

1,250.00 USDC

0x7a3f…E29b

Wallets that live inside your app

No browser extensions or popups. Users sign in with email or social and get a non-custodial wallet instantly—keys managed securely, seed phrases hidden.

Email & social loginPasskeysNo seed phrases
Read the docs

Programmable smart accounts with ERC-4337 & EIP-7702

Every embedded wallet is backed by a smart account. Transaction batching, social recovery, and session keys are built in. Upgrade existing EOAs with EIP-7702 or deploy new smart accounts—same infrastructure, your choice.

ERC-4337 & EIP-7702Batch transactionsSocial recovery
Read the docs

Smart Account

0x7a3f…E29b

ERC-4337EIP-7702
Batched callsSession keysGas sponsorshipSocial recovery

GFAL logo

Openfort has been an instrumental piece of technology for our platform. They helped us from integration to auditing the implementation.

Christian Gascon

CTO @GFAL

Signing Speed Performance

Higher is better (normalized to 100%)

96%
125msOpenfort
94%
175msProvider 1
88%
350msProvider 2
4%
2850msProvider 3
Other AA wallets266,464
With Openfort235,432

*Updated September 2025


From developers that use Openfort

"Game studio reaches 150K players in 3 months"

From launch to 150,000 active players with smooth onboarding and zero infrastructure headaches.

Moonlit Games

Moonlit Games

Read story
"Augmented reality project used Openfort to kickstart their claiming campaign"

Integrated the Openfort React to help onboard users with familiar login methods and connect their existing wallet via a wallet connector.

Particle Ink

Particle Ink

Read story
"Mobile gaming multi-platform based out of Korea"

From concept to mainnet in two weeks with built-in capabilities for their own blockchain working smoothly both on mobile and website via the marketplace.

Kroma

Kroma

Read story

Build a whitelabel experience on top of Openfort, or customize our out-of-the-box components to optimize conversion.

Web and mobile SDKs

Components that work across mobile and web. No more worrying about how to build a mobile wallet connector.

Fine-grained customization

Customize our out-of-the-box components to optimize conversion.

Full whitelabeling

Build a whitelabel experience on top of Openfort, or customize our out-of-the-box components to optimize conversion.



Ship your first wallet in minutes


Frequently Asked Questions

Can't find your answer?

Talk to sales

An embedded wallet is a non-custodial crypto wallet that is created and managed directly inside an app, rather than through a separate browser extension or external app. Users sign in with familiar methods like email, social login, or passkeys and immediately get a wallet that signs transactions without leaving the experience. Embedded wallets remove the friction of seed phrases, extension installs, and pop-up signing — which is why teams choose them over wallets like MetaMask for consumer onboarding. See the deep-dive in our guide on how embedded wallets work and our list of the best embedded wallet providers for 2026.

Custodial wallets hold user keys on a centralized server — fast and simple, but the provider can move user funds and you inherit their compliance posture. MPC wallets split a key across parties using threshold cryptography; signing requires multiple parties to coordinate, which adds latency and operational complexity. Embedded wallets like Openfort use TEE-backed key shares plus smart accounts: keys stay non-custodial, signing is sub-200ms, and you get programmable features (session keys, gas sponsorship, batching) for free. You get the UX of custodial onboarding with the sovereignty of self-custody.

Embedded wallets are created and managed inside your app rather than through a separate browser extension. With Openfort, keys are split and managed via a secure signer (OpenSigner) and smart wallet contracts, so users never see seed phrases but still get non-custodial control. Your app talks to Openfort’s APIs/SDK, which orchestrate wallet creation, session keys, and transaction signing for you.

Browser extension wallets (like MetaMask) live outside your app and require context-switching, pop-ups, and manual connection flows. Embedded wallets live inside your product: users sign up with email or social login and immediately have a wallet ready to use. Openfort also lets you link both worlds—embedded wallets plus external EOAs—so power users can connect an existing wallet while everyone else gets an embedded experience.

Every Openfort embedded wallet is backed by a smart account (ERC-4337 or EIP-7702). This means wallets get programmable features out of the box: transaction batching, social recovery, session keys, and spending limits. Smart accounts also enable gas sponsorship so users never need native tokens, and they support upgradeability so you can add new features without changing wallet addresses.

With account abstraction, you can sponsor gas for users using a Paymaster so they don’t need native tokens just to move assets. Openfort’s Paymaster handles gas sponsorship and can be combined with embedded wallets so users just see “send 10 USDC,” not “approve ETH for gas.” That’s especially useful for stablecoin payments, gaming microtransactions, and consumer apps where on-chain UX needs to feel like a normal fintech app.

They can be—and Openfort is built to be non-custodial by default. Keys are generated client-side and split into shares; recovery is tied to your login and policies rather than seed phrases. Because OpenSigner is self-hostable, you can migrate infra or providers later without forcing users to change wallets, giving you embedded wallet UX without long-term vendor lock-in.