Openfort vs Turnkey
The complete wallet stack. Open-source and production-ready.
No credit card required • Free testnet accounts
50+ teams use Openfort.10M+ transactions sent by 50+ teams.
Read their storiesSEE WHY TEAMS love Openfort→
Why developers are switching from Turnkey to Openfort
Open-source embedded wallets, secure backend wallets
Turnkey provides TEE-based key infrastructure, but you are dependent on their proprietary signing service. Openfort offers Opensigner, an open-source and self-hostable embedded wallet solution that guarantees you always own your users' keys and data. For server-side use cases, Openfort also provides TEE backend wallets that securely store private keys and enable automatic transactions with granular permissions, ideal for backend automation, AI agents, and any workflow that requires server-side signing without exposing keys.
Smart accounts and gasless transactions, included
With Turnkey, you only get gas sponsorship at enterprise tier. Openfort treats smart accounts as first-class citizens with native support and includes built-in gasless transactions at free tier. With session keys, batched transactions, and a policy engine, Openfort delivers the complete account abstraction stack so you can ship without assembling it yourself.
The complete wallet stack
Turnkey excels at low-level key infrastructure with policy engines and attestations around the TEE, making it a strong choice for projects that need full traceability and compliance around key management. Openfort complements this by providing the rest of the stack that Turnkey leaves to you: transaction orchestration with paymaster-powered gas sponsorship, authentication orchestration with any identity provider, and production-ready UI components. For the majority of use cases, Openfort lets you ship a complete wallet experience with familiar developer tools instead of building each layer from scratch.
Higher is better (normalized to 100%)
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 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?
Openfort is a complete wallet stack that includes smart accounts, paymasters for gasless transactions, and UI orchestration, whereas Turnkey is primarily low-level key infrastructure with TEE-based signing. Turnkey gives you fast signing latency but requires you to build smart accounts, gas sponsorship, and the user-facing wallet experience yourself. Openfort provides all of this out of the box, including Opensigner for embedded wallets and TEE backend wallets for secure server-side key storage with automatic transaction capabilities.
Turnkey delivers sub-100ms signing latency with high uptime, which is excellent for raw key operations. However, signing speed is only one piece of the puzzle. You still need to build smart accounts, gas sponsorship through paymasters, session key management, and a complete UI on top. Openfort provides all of these as native features, so you can focus on your product instead of assembling wallet infrastructure from scratch.
Yes! You can start for free with our developer tier. No credit card required to start building and testing on testnets. Openfort uses usage-based pricing where you only pay per operation (creating a wallet or sending a transaction), so costs scale predictably with your actual usage.
Openfort is platform agnostic with SDKs for React, React Native, Unity, Unreal, and raw JavaScript/TypeScript. We support all EVM chains. Unlike Turnkey, which focuses on key infrastructure, Openfort provides the full stack including authentication orchestration, so you can plug in any identity provider and get a complete wallet experience.
Openfort offers multiple approaches depending on your use case. For client-side embedded wallets, Opensigner provides open-source, self-hostable key management. For server-side operations, TEE backend wallets store private keys securely and enable automatic transactions with granular permissions. You can also orchestrate keys from other providers like Turnkey or Fireblocks, meaning you can use Turnkey as a signer while gaining Openfort's smart account features and paymaster infrastructure.
Yes. You can keep using Turnkey as the underlying signer and layer Openfort's smart account infrastructure on top to get gas sponsorship through paymasters and session keys. Alternatively, you can migrate fully to Opensigner for complete open-source sovereignty with self-hosting capabilities.
Openfort uses transparent, usage-based pricing where each operation is either creating a wallet or sending a transaction. You pay for what you actually use, which makes costs predictable and fair as your application scales. There are no per-seat fees or monthly active user charges that can create unexpected costs.
We offer dedicated support channels for customers, along with comprehensive documentation and a community Telegram group.