Theme

Verified October 1, 2026·8 products·18 criteria

Why TUWAComparisons & Ecosystem Radar

A verified technical breakdown of how TUWA compares with connect modals, embedded-wallet services and transaction platforms, including where they are the better choice. Every fact links to its source.

Ecosystem Radar

Pick a product to lay it over TUWA. Click an axis to see the criteria behind its score. TUWA is a set of packages, not a wallet provider, so each product faces the TUWA projects that do the same job:

  • Wallet Connection UI→Satellite Connect + Nova Connect
  • Embedded Wallets & Auth→SIWX + Satellite Connect
  • Wallet & Transaction Platforms→Pulsar + Quasar
  • Indexing→Quasar
TUWARainbowKit
255075100Self-CustodyOpennessCost atScaleTx LifecycleOnboardingChainCoverage

Compare TUWA with

RainbowKit ↗MIT

React connect modal for EVM apps, built on wagmi.

Pricing
Free (MIT). WalletConnect needs a free Reown project ID.[10]
TUWA counterpart
Satellite Connect + Nova Connect

Do keys and user records stay with users and with you?

TUWA 100 · RainbowKit 100

Users sign with their own wallets

Extension, mobile and hardware wallets connect through standard protocols.

Yes

TUWA: EIP-6963 wallets through wagmi, Wallet Standard wallets on Solana, WalletConnect and Safe{Wallet}.[1]

Yes

RainbowKit: Wallets connect through wagmi connectors and WalletConnect.[10]

No vendor-run key management

The product creates no wallets whose keys live in the vendor's MPC, TEE or enclave infrastructure.

Yes

TUWA: TUWA creates no wallets and never handles keys.[1]

Yes

RainbowKit: No embedded wallets.[10]

User records stay with you

The vendor keeps no account for each of your users.

Yes

TUWA: Sessions live on your server (siwx-server). Quasar Cloud stores the transactions your app syncs; the Community Edition keeps them on your servers.[2]

Yes

RainbowKit: A client-side library: no user records.[11]

Every Criterion

The 18 criteria behind the radar for all products at once. Hover a mark for the note; the number links to its source.

Comparison criteria of TUWA and eight other products, grouped by radar axis
CriterionTUWARainbowKitConnectKitReown AppKitPrivyDynamicthirdwebAlchemyThe Graph
Self-Custody100100673333333310067
Users sign with their own walletsYes[1]Yes[10]Yes[13]Yes[16]Yes[20]Yes[28]Yes[36]Yes[43]No[50]
No vendor-run key managementYes[1]Yes[10]Partial[14]No[17]No[21]No[29]No[37]Yes[44]Yes[51]
User records stay with youYes[2]Yes[11]Partial[14]No[18]No[22]No[30]No[38]Yes[44]Yes[51]
Openness1005050033333333100
Client under an OSI licenseYes[3]Yes[11]Yes[15]No[19]Yes[23]Yes[31]Yes[39]Yes[45]Yes[52]
Backend open source, or none neededYes[4]Partial[10]Partial[14]No[19]No[21]No[29]No[40]No[43]Yes[51]
Runs without a vendor keyYes[1]No[10]No[13]No[16]No[24]No[32]No[36]No[46]Yes[51]
Cost at Scale100100100333333067100
Free to shipYes[5]Yes[11]Yes[14]Yes[18]Yes[22]Yes[30]No[38]Yes[47]Yes[53]
No per-user billingYes[5]Yes[11]Yes[15]No[19]No[22]No[30]No[38]Yes[47]Yes[53]
Free self-hosted pathYes[4]Yes[11]Yes[15]No[19]No[21]No[29]No[40]No[47]Yes[51]
Tx Lifecycle1005000333350330
Tracks transactions to a final stateYes[6]Partial[12]No[13]No[16]Partial[25]Partial[33]Partial[41]Partial[46]No[50]
Pending transactions survive a reloadYes[6]Yes[12]No[13]No[16]No[21]No[28]No[36]No[43]No[50]
Status webhooksYes[7]No[12]No[13]No[16]Partial[25]Partial[33]Yes[38]Partial[48]No[50]
Onboarding0067100100100100330
Email or social loginNo[1]No[10]Yes[14]Yes[16]Yes[20]Yes[28]Yes[37]No[44]No[50]
Wallets for users without oneNo[1]No[10]Yes[14]Yes[17]Yes[21]Yes[29]Yes[37]No[44]No[50]
Gas sponsorship or on-rampNo[6]No[10]No[14]Yes[16]Yes[26]Yes[34]Yes[38]Yes[43]No[50]
Chain Coverage67333310010010067100100
EVM networksYes[8]Yes[10]Yes[13]Yes[16]Yes[27]Yes[35]Yes[38]Yes[49]Yes[50]
SolanaYes[8]No[10]No[13]Yes[16]Yes[27]Yes[35]Yes[42]Yes[49]Yes[50]
Other chain familiesNo[9]No[10]No[13]Yes[16]Yes[27]Yes[35]No[38]Yes[49]Yes[50]

When to Choose Them Instead

No toolkit fits every app. Here is where each product is the better pick, and what TUWA does differently in the same job.

Wallet Connection UI

TUWA counterpart: Satellite Connect + Nova Connect

RainbowKit

React connect modal for EVM apps, built on wagmi.

Choose RainbowKit when

Your app is EVM-only and you want a polished, well-known connect modal with the least setup.

How TUWA differs

Satellite Connect keeps the connection in a headless store for EVM and Solana, and Pulsar follows every transaction to Success, Failed or Replaced, not only until the first confirmation.

ConnectKit

React connect modal for EVM apps by Family, built on wagmi, with optional Family Accounts.

Choose ConnectKit when

You want a themeable EVM connect modal and email or phone sign-up through Family Accounts.

How TUWA differs

TUWA never creates accounts for your users, covers Solana as well as EVM, and adds transaction tracking (Pulsar) and a backend you can self-host (Quasar).

Reown AppKit

Connect modal with email and social login, on-ramp and swaps, from the WalletConnect team.

Choose Reown AppKit when

You need email and social login, an on-ramp and Bitcoin from one vendor, and the Reown license terms fit your scale.

How TUWA differs

TUWA is Apache-2.0 with no usage thresholds and no mandatory gateway, and it bills nothing per user.

Embedded Wallets & Auth

TUWA counterpart: SIWX + Satellite Connect

Privy

Embedded wallets and user authentication as a managed service.

Choose Privy when

Most of your users have no wallet, and you want email and social login, embedded wallets, gas sponsorship and many chains, managed for you.

How TUWA differs

TUWA keeps users on their own wallets and your sessions on your server (SIWX, CAIP-122), with no per-user bill and nothing to trust but the chain.

Dynamic

Authentication and MPC embedded wallets as a managed service.

Choose Dynamic when

You need embedded wallets on the widest list of chains, with enterprise policies and delegated access, managed for you.

How TUWA differs

TUWA never holds a key share: users sign with their own wallets, sessions stay on your server, and nothing is billed per user.

Wallet & Transaction Platforms

TUWA counterpart: Pulsar + Quasar

thirdweb

All-in-one platform: in-app wallets, transactions API, RPC, gas sponsorship and contracts.

Choose thirdweb when

You want one vendor for in-app wallets, server wallets, gas sponsorship, RPC and contract deployment, and the subscription fits your budget.

How TUWA differs

Pulsar tracks transactions from any wallet in the browser, and Quasar adds history and webhooks as a cloud or as the Apache-2.0 Community Edition.

Alchemy

RPC and data platform with Wallet APIs for smart wallets and gas sponsorship.

Choose Alchemy when

You already run on Alchemy RPC and need gas sponsorship and smart wallets (EIP-7702) on EVM and Solana.

How TUWA differs

Pulsar follows any transaction, not only the calls sent through one API, keeps pending ones across reloads, and Quasar can run on your own servers.

Indexing

TUWA counterpart: Quasar

The Graph

Decentralized protocol that indexes contract events into GraphQL APIs (subgraphs).

Choose The Graph when

You need to query contract events and state across all users. That is indexing, a different job from tracking what your app sends; many apps use both.

How TUWA differs

Quasar does not index contracts: it follows the transactions your users send from your app and keeps their history per wallet, with webhooks.

Methodology

How the scores are computed, what the marks mean and where every fact comes from.

Scoring

Each axis has 3 yes-or-no criteria, listed in the table above. A product scores (met + ½ · partial) ÷ 3 × 100 on the axis. Nothing is weighted or adjusted by hand: the page computes every score from the facts.

  • YesMet: the vendor documents it for the product as a whole.
  • PartialPartial: only for some of its wallets, transactions or plans, or only with an optional feature turned off.
  • NoNot met: missing, outside the product's job, or not documented (we found no mention in the vendor's documentation on the check date).

What we compare

A product is scored as its vendor offers it by default, optional features included. TUWA is a set of packages, so each competitor faces the TUWA projects that do the same job; the radar shows the whole stack. Two axes, Onboarding and Chain Coverage, favor hosted platforms by design, and we keep them so the picture stays honest.

Transparency note

TUWA wrote this page. Every fact was verified on October 1, 2026 against primary sources: vendor documentation, licenses on GitHub and npm, and pricing pages. We recheck it every quarter. The data lives in one typed file; if something is outdated or wrong, open an issue and we will fix it.

Sources

  1. [1]satellite.docs.tuwa.io
  2. [2]siwx.docs.tuwa.io
  3. [3]github.com/TuwaIO
  4. [4]docs.tuwa.io/quasar/self-hosting
  5. [5]tuwa.io/pricing
  6. [6]pulsar.docs.tuwa.io
  7. [7]docs.tuwa.io/quasar/webhooks
  8. [8]docs.tuwa.io
  9. [9]tuwa.io
  10. [10]rainbowkit.com/docs/installation
  11. [11]github.com/rainbow-me/rainbowkit
  12. [12]rainbowkit.com/docs/recent-transactions
  13. [13]family.co/docs/connectkit/getting-started
  14. [14]family.co/docs/connectkit/family-accounts
  15. [15]github.com/family/connectkit
  16. [16]docs.reown.com/appkit/overview
  17. [17]docs.reown.com/appkit/authentication/socials
  18. [18]reown.com/pricing
  19. [19]github.com/reown-com/appkit/blob/main/LICENSE.md
  20. [20]docs.privy.io/authentication/overview
  21. [21]docs.privy.io/wallets/overview
  22. [22]privy.io/pricing
  23. [23]npmjs.com/package/@privy-io/react-auth
  24. [24]docs.privy.io/basics/react/setup
  25. [25]docs.privy.io/api-reference/webhooks/transaction/confirmed
  26. [26]docs.privy.io/wallets/gas-and-asset-management/gas/setup
  27. [27]docs.privy.io/wallets/overview/chains
  28. [28]dynamic.xyz/docs/react-sdk/quickstart
  29. [29]dynamic.xyz/docs/embedded-wallets/mpc/how-shares-work
  30. [30]dynamic.xyz/pricing
  31. [31]npmjs.com/package/@dynamic-labs/sdk-react-core
  32. [32]dynamic.xyz/docs/react/reference/providers/dynamiccontextprovider
  33. [33]dynamic.xyz/docs/embedded-wallets/on-chain-events
  34. [34]dynamic.xyz/docs/embedded-wallets/gas-sponsorship
  35. [35]dynamic.xyz/docs/embedded-wallets/chains/overview
  36. [36]portal.thirdweb.com/typescript/v5/getting-started
  37. [37]portal.thirdweb.com/connect/in-app-wallet/security
  38. [38]thirdweb.com/pricing
  39. [39]github.com/thirdweb-dev/js
  40. [40]github.com/thirdweb-dev/engine
  41. [41]portal.thirdweb.com/engine
  42. [42]portal.thirdweb.com/wallets/solana
  43. [43]alchemy.com/docs/wallets
  44. [44]alchemy.com/docs/wallets/account-kit-deprecated
  45. [45]github.com/alchemyplatform/aa-sdk
  46. [46]alchemy.com/docs/wallets/api-reference/smart-wallets/wallet-api-endpoints/wallet-api-endpoints/wallet-get-calls-status
  47. [47]alchemy.com/pricing
  48. [48]alchemy.com/docs/reference/notify-api-quickstart
  49. [49]alchemy.com/docs/reference/node-supported-chains
  50. [50]thegraph.com/docs/en/supported-networks/
  51. [51]github.com/graphprotocol/graph-node
  52. [52]github.com/graphprotocol/graph-tooling
  53. [53]thegraph.com/studio-pricing/

Ready to try it?

Start From a Template →Full-Stack Guide