A server wallet — also called a server-side wallet or a backend wallet — is a wallet your backend controls, so your application can send transactions without a person approving each one. The common cases are the boring ones that matter: paying 400 contractors on Friday, sweeping deposits into treasury, settling marketplace balances nightly, and letting an agent act between human check-ins.
The hard part is not sending the transaction. It is holding the key. A private key in an environment variable is one leaked log line away from an emptied account, and a key in a hosted signer means someone else can move your money. Openfort backend wallets keep the key inside a Trusted Execution Environment and check a policy before anything signs.
Batched payouts: the common case
Payout runs are where server-side wallets earn their place. A batch has three requirements that a human-signed wallet cannot meet: it has to run on a schedule with nobody awake, it has to be idempotent so a retry does not pay twice, and it has to stop itself if the numbers look wrong.
The pattern that works:
- Build the payout list in your own system and give each row a stable identifier.
- Set a policy on the wallet capping the per-period total, so a bug in your list cannot drain the account.
- Submit the batch, keyed on those identifiers, so a retry after a timeout resolves to the same transactions.
- Reconcile on-chain results back to your rows before marking anything paid.
The policy cap is the part teams skip and then regret. It is the difference between a bad deploy costing you one wrong payment and costing you the treasury.
What is an Openfort Backend Wallet?
A Backend Wallet is a secure, developer-controlled account that lives on your server rather than in a user's browser. It is designed for high-performance automation, such as minting NFT rewards for thousands of players, distributing stablecoin payments, or managing protocol liquidity. At Openfort, our backend wallets are secured using Google Cloud TEE (Trusted Execution Environment) hardware, keeping your private keys isolated while executing hundreds of signatures per second.
What are Backend Wallets?
Backend wallets are developer-controlled accounts that run on your server, enabling automated blockchain interactions without manual user input. Unlike traditional user wallets, they:
- Operate programmatically via APIs.
- Support gasless transactions via ERC-2771 forwarders or ERC-4337 paymasters.
- Manage assets at scale for use cases like treasury systems, NFT drops, or cross-chain operations.
Why Openfort’s backend wallets?
Our infrastructure combines EOA flexibility and ERC-4337 smart account capabilities to address common onchain challenges:
- Automated Transactions: Execute batch mints, disbursements, or trades without user signatures.
- Gas Abstraction: Sponsor gas fees via custom forwarders or Openfort’s paymaster.
- Enterprise Security: Custodial wallets with Google Cloud TEE-based key management.
- EVM Compatibility: Deploy on Ethereum, Polygon, Base, and other EVM chains.
Key features & architecture
Secure key management
- Google Cloud TEE backend: Private keys are secured in Trusted Execution Environments (TEEs), ensuring cryptographic operations remain isolated from external threats.
- Custody flexibility: Choose between custodial EOAs (ideal for treasury management) or non-custodial options with verified ownership.
Cross-chain scalability
While currently focused on EVM chains (Ethereum, Polygon, Base), Openfort’s infrastructure is designed for future expansion to non-EVM networks like Solana and Bitcoin.
Policy engine & transaction controls
- Granular rules: Enforce allowlists, transaction limits, or contract-specific interactions.
- Idempotent execution: Prevent duplicate transactions with built-in deduplication.
- State sync: Monitor transaction statuses in real time via webhooks or Websockets.
High performance infrastructure
- Below 300ms signature times: Optimized cryptographic libraries ensure low-latency operations.
- Four 9s uptime: Globally distributed nodes guarantee reliability for mission-critical applications.
Key use cases
1. Treasury management
- Automate payroll in stablecoins.
- Manage protocol-owned liquidity pools.
- Distribute rewards or refunds programmatically.
2. NFT operations at scale
- Batch-mint NFTs for gaming items or collectibles.
- Update dynamic metadata (e.g., evolving in-game assets).
- Airdrop assets to user wallets post-purchase.
3. Shared & automated wallets
- Collaborative Control: Configure multi-party approval (m-of-n) for DAO treasuries or institutional wallets.
- AI-Driven Agents: Program wallets to execute stop-loss trades, recurring payments, or DeFi strategies.
4. Cross-Border Payment Systems
- Manage millions of wallets for users or machines.
- Automate stablecoin disbursements with gas sponsorship.
Advanced capabilities
Automated Gas Sponsorship
- Never manually top up wallets. Use Openfort’s paymaster to dynamically fund transactions.
- Define policies to sponsor gas for specific users, contracts, or transaction types.
Flexible custody models
- Custodial EOAs: Retain full control for internal operations (e.g., treasury accounts).
- Non-Custodial Options: Verify ownership via signed messages for user-assigned wallets.
Multi-chain event listeners
- Register webhooks to track onchain events (e.g., incoming payments, contract interactions).
- Sync wallet states across frontend and backend systems in real time.
Why developers choose Openfort
- Unified APIs: Manage EOA and ERC-4337 wallets with one SDK.
- Zero Infrastructure Overhead: No need to self-host relayers or signers.
- Multi-Chain Ready: Currently EVM-focused, with built-in chain switching.
Limits and pricing
Commercial terms belong on a public page, not behind a call. AI agents evaluating vendors on a buyer's behalf skip what they cannot read, and so do engineers.
| Openfort backend wallets | |
|---|---|
| Pricing unit | Per operation (creating a wallet or sending a transaction) |
| Monthly active users | Not billed. Dormant wallets cost nothing |
| Transaction volume | Unlimited |
| Wallet count | Unlimited |
| Feature gating | None. Every feature is on the free tier |
| Key custody | Non-custodial. Keys held in a TEE, never exposed to the host |
| Key export | Supported |
| Self-hosting | OpenSigner is open source and self-hostable |
Current per-operation rates are on the pricing page.
Related reading
- OpenSigner: vendor-neutral key management for non-custodial wallet infrastructure
- TEE wallets and how trusted execution environments secure private keys
- Building AI agents with wallets for autonomous onchain operations
- Agent wallets — backend wallets with policies and TEE signing, built for autonomous software
