Skip to main content
Beta: Wallet-as-a-Service is currently in beta. The SDK’s methods and structure can change quickly, and breaking changes are communicated to customers on an as-needed basis. WaaS is available on paid plans only — contact the Helius team to get started.
Helius Wallet-as-a-Service (WaaS) adds non-custodial embedded wallets to your app. Your users sign up with a passkey, email, or an existing Solana wallet — no seed phrases — and get an embedded Solana wallet they fully control. You integrate it with one React provider and one hook from the helius-wallet-kit npm package.
Signing in with an existing wallet (e.g. Phantom) is a sign-in method — it authenticates the user into their embedded Helius wallet; signing always uses the embedded wallet, not the external one. Social login (Google, Apple, Discord, X) is coming soon.
Each user’s wallet is secured by Turnkey infrastructure under a Helius-managed organization. Keys never leave Turnkey’s secure enclaves, and signing happens client-side.

​
Why Helius WaaS

  • One integration. Embedded wallets, client-side signing, RPC, and optimized transaction sending come from a single SDK — one provider, one hook. No separate wallet vendor.
  • One bill. Wallets and signing are billed through the Helius credits you already have — a flat 200 credits ($0.001) per signature, no separate subscription and no per-monthly-active-user fee. Wallet count doesn’t change your bill; only signatures do.
  • Enterprise rates at startup cost. WaaS runs on the same Helius infrastructure your app already uses, and at a flat 200 credits ($0.001) per signature it’s priced to compete with enterprise-tier embedded-wallet plans — no separate subscription, no per-seat fees. Transactions send through key-less Secure RPC by default, or Helius Sender for optimized landing.

​
How it works

  • Each end user gets a dedicated embedded wallet (i.e., a Turnkey sub-organization), created on first sign-in.
  • Signing happens client-side — transactions and messages are signed directly against Turnkey from the user’s browser. Your server never holds keys.
  • Transactions route through Helius — directly to your project’s key-less Secure RPC URL by default, or via Helius Sender when you add the server route handler.
  • Usage bills through your existing Helius credits — see Pricing.

​
Prerequisites

  • A paid Helius plan — WaaS is available on any paid plan. Sign up.
  • A Helius API key — create one in your dashboard.
  • A React 18+ app on Node.js 18+. The provider and hook are framework-agnostic; Next.js 14+ is needed only if you add the optional route handler.

​
Pricing

WaaS bills through your existing Helius credits — there is no separate subscription. Each signature costs 200 credits ($0.001 at the standard credit rate), which covers the embedded wallet and signing. Failed signatures are not billed.
Every signing operation is one signature: signMessage, signTransaction, and signAndSendTransaction each produce one. WaaS is available on any paid plan.
Track wallets, signatures, and credits spent on the dashboard in WaaS → Analytics.

​
Next steps

Quickstart

Install the SDK and wire up the provider.

Configuration

Config options and dashboard sign-in methods.

Using the wallet

Read auth state, sign, send, and read history.

API reference

The useHeliusWallet() hook and imports.