Choosing one architecture is not a one way street, it is possible to access server generated wallets from the client
side and vice versa.
Server Centric Architecture
Generate and manage wallets using an API key, from your server. Perfect for applications that need to:- Create and manage wallets programmatically via REST API
- Pre-generate wallets without the user present (e.g. for airdrops)
- Create wallets for non-user entities (e.g. internal wallets for your business, or for AI agents)
- Handle transactions server-side without user interaction
- Self-custody: when you want your user to be the sole custodian of their wallet
Client Centric Architecture
Generate and manage wallets linked to a user, secured by user credentials from auth. Ideal for applications that want to:- Embed wallet functionality directly in web or mobile applications
- Deploy wallets for users (i.e. not agents or other internal business wallets)
- Require users to log in
- Allow their users to self custody
- When you want to deploy wallets not tied to a user entity
- Applications that have a heavy need for making wallet actions when the user is not online
AI Agent Architecture
Generate and manage wallets for AI agents, whether you are an agent developer or an infrastructure provider hosting agents for multiple owners.- Deploy agents securely without taking custody of their assets
- Maintain regulatory compliance while scaling
- Give agent owners full control over their agents’ wallets
- Enable autonomous on-chain operations
Comparison
| Feature | Server Side | Client Side |
|---|---|---|
| Integration Type | REST APIs | Client SDKs |
| Key Management | Full control | User-managed |
| Authentication | API Key | User Auth (Passkeys/Email/Social…) |
| Chain Support | All Chains | EVM and Solana |
| Best For | Backend Systems & Automation | Web Apps & User Interaction |
| Transaction Signing | Server-side | Client-side |
| Custody | Business, or Hybrid | User |