Openfort vs Pimlico
ERC-4337 infrastructure plus the wallet around it. Under one SDK.
No credit card required • Free testnet accounts
Why developers choose Openfort over a standalone bundler
More than a bundler and a paymaster
Pimlico provides bundler and paymaster infrastructure for ERC-4337. You still need to source an embedded wallet, an auth layer, a signer, and orchestration glue. Openfort bundles all of that — and keeps you bundler-agnostic if you want to keep using Pimlico underneath.
ERC-4337 and EIP-7702 in one SDK
Openfort smart accounts ship with native ERC-4337 and EIP-7702 support, built-in paymasters for gasless transactions, session keys, batched operations, and a policy engine. Sub-100ms wallet creation. Public benchmarks at openfort.io/benchmarks.
OpenSigner: audit it, fork it, self-host it
The signer is the most sensitive part of the wallet stack. Openfort’s key management, OpenSigner (opensigner.dev), is open-source and self-hostable. Your compliance team can audit it. Your engineering team can run it inside your own infrastructure.
“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 + EIP-7702 smart accounts with paymasters, 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?
Pimlico provides ERC-4337 infrastructure — bundlers and paymasters — that you stitch into your own wallet stack. Openfort delivers the entire wallet stack: embedded wallets, auth orchestration, smart accounts, paymasters, session keys, and open-source key management via OpenSigner. With Pimlico you assemble the wallet yourself. With Openfort you ship.
Yes. Openfort ships built-in paymasters for gasless transactions and is bundler-agnostic. You can use Openfort’s defaults or point it at any bundler, including Pimlico, Stackup, or self-hosted.
Both support ERC-4337. Openfort also natively supports EIP-7702 so you can upgrade existing EOAs to smart accounts without changing addresses. All of this is available through the Openfort SDK.
Yes — Pimlico is infrastructure (bundler + paymaster), not an end-to-end wallet. Teams typically combine it with a separate embedded wallet provider, an auth provider, and a signer. Openfort gives you all of that in one SDK.
Openfort uses transparent usage-based pricing per operation (wallet creation or transaction), bundling wallets, paymasters, and signing under a single meter. Pimlico bills per UserOp on infra you wire together yourself.
OpenSigner — Openfort’s key management — is fully open-source and self-hostable at opensigner.dev. You can audit it, fork it, or run it inside your own infrastructure.
Openfort ships agent wallets out of the box: session keys, policy-based spending limits, x402 for HTTP-native payments, and TEE backend signing for server-side agents. Pimlico provides the AA primitives — you build the agent wallet on top.