Openfort vs Alchemy
Already on Alchemy RPC? Add embedded wallets and smart accounts without ripping out your stack.
No credit card required • Free testnet accounts
Add embedded wallets to your Alchemy stack with Openfort
No signer sunset risk, ever
Alchemy is sunsetting its in-house Account Kit signer. When the provider that holds your keys deprecates its own infrastructure, you are forced to migrate. Openfort uses OpenSigner (opensigner.dev), an open-source, self-hostable signer you can audit, fork, or run yourself. The most sensitive part of the stack stays under your control — no black box, no forced migrations.
Built for wallets, not bolted onto RPC
Alchemy is an RPC and node provider that added wallets through Account Kit. Openfort is wallet-native from day one: embedded wallets, native ERC-4337 and EIP-7702 smart accounts, built-in paymasters for gasless transactions, session keys, and a contract/function-level policy engine — all under a single SDK. Keep Alchemy for raw node access if you like; Openfort owns the wallet experience.
Swap Account Kit without rewriting your app
Migrating is a near drop-in swap. Replace @account-kit/react with @openfort/react, and because the Openfort smart account is bonded to the wagmi connector, your existing useSendTransaction, useSignMessage, and useAccount calls keep working. Auth hooks map one-to-one, and EIP-7702 is supported via use7702Authorization. Read the migration guide.
“Openfort has been an instrumental piece of technology for our platform. They helped us from integration to auditing the implementation.”
Christian Gascon
CTO @GFAL
Higher is better (normalized to 100%)
*Updated September 2025
Explore other features at Openfort
Find out more about how teams are using Openfort
Embedded wallets
Non-custodial embedded wallets powered by OpenSigner, with full key export and self-hosting options. Read more
Account abstraction
Native ERC-4337 smart accounts with paymasters for gasless transactions, session keys, and batched operations. Read more
Wallet automations
TEE backend wallets for server-side key storage with permissions and automatic transaction execution. Read more
Frequently Asked Questions
Can't find your answer?
Alchemy started as RPC and node infrastructure and later added Account Kit for smart wallets. Openfort is wallet-native from the ground up: embedded wallets, native smart accounts, paymasters, session keys, and a policy engine under one SDK. Critically, Openfort’s key management (OpenSigner) is open-source and self-hostable, so the most sensitive part of your stack is never a black box you depend on a single vendor to keep running.
Openfort uses OpenSigner, an open-source, self-hostable signer. Because you can audit, fork, or host it yourself, there is no "signer sunset" risk — you are never forced to migrate because a provider deprecated its key management. For teams leaving Account Kit, we maintain a step-by-step migration guide that keeps your React + wagmi developer experience intact.
It is a drop-in swap for most React apps. You replace @account-kit/react with @openfort/react and its layered provider, then switch Account Kit hooks (useAuthenticate, useSendUserOperation) to Openfort’s headless hooks plus standard wagmi hooks. The Openfort smart account is bonded to the wagmi connector, so your existing useSendTransaction, useSignMessage, and useAccount calls keep working. See the full migration guide on our blog.
Yes. Both ERC-4337 and EIP-7702 are native. Openfort ships built-in paymasters for gasless transactions, session keys (useGrantPermissions), batched operations, and a contract/function-level policy engine. You can run new smart accounts or upgrade existing EOAs with EIP-7702 via use7702Authorization.
Openfort is bundler- and RPC-agnostic. You can keep Alchemy (or any provider) for raw node access and reads while using Openfort for the entire wallet experience — embedded wallets, smart accounts, gas sponsorship, and signing. The two are complementary; Openfort focuses on the wallet layer Alchemy is stepping back from.
Openfort uses transparent, usage-based pricing where an operation is creating a wallet or sending a transaction. That keeps wallet costs predictable as you scale, instead of being bundled with compute-unit RPC billing.