Language
Theme

Persistence & Sync for Web3 Transactions

Quasar tracks transactions on the server and keeps their history on every device. Use the managed cloud, or self-host the open-source Community Edition: the same SDK works with both.

01 / Editions

Quasar CloudQuasar Community Edition

Managed Cloud or Self-Hosted

One engine, two ways to run it. Start on Quasar Cloud in minutes, or deploy the open-source Community Edition on infrastructure you control.

  • 01Managed · Public Beta

    Quasar Cloud

    • TUWA operates the infrastructure, backups and monitoring
    • Developer dashboard with organizations and team access
    • SIWX wallet sign-in, passkeys and email notifications
    • Free during the public beta: 1,000 free quota units for every organization; bring your own RPC provider
    • Portable: an owner can export an organization to a self-hosted node at any time
  • 02Self-Hosted · Apache-2.0

    Quasar Community Edition

    • Same engine: two-phase EVM & Solana tracking, partitioned PostgreSQL 16, signed webhooks
    • Payload admin panel secured with email, password and TOTP 2FA
    • Docker Compose minimal & production profiles, Traefik, optional Cloudflare Tunnel
    • Prometheus, Loki and Grafana dashboards; signed images with SBOM
    • No usage billing — rate limits are yours to set; you pay only for servers and RPC
    • Imports Quasar Cloud organizations with their API keys, webhook secrets and transaction history

    Cloud-only: SIWX sign-in, passkeys, email, multi-tenant portal

    View on GitHub

Run a node locally

bash

$ git clone https://github.com/TuwaIO/quasar-community.git
$ cd quasar-community && cp .env.example .env
$ docker compose --env-file .env -f infra/docker-compose.minimal.yml up -d --build

Point the SDK at your node

@tuwaio/quasar-sdk

const quasar = new Quasar({
  baseUrl: 'https://api.your-node.com',
  secretKey: process.env.QUASAR_SECRET_KEY,
});

Moving from Cloud? Export the organization in the dashboard and import the file in your node's admin panel: the API keys stay the same, so your apps only change the SDK's baseUrl. Migration guide

Live engine health

02 / Live metrics

Quasar Cloud

Quasar Cloud in Numbers

What Quasar Cloud has tracked and delivered so far, counted live.

  • 01Transactions Tracked

    Loading...

    EVM and Solana transactions followed to their final status.

  • 02Webhooks Delivered

    Loading...

    Signed events delivered to the endpoints of apps, with retries and a dead-letter queue.

Figures reflect Quasar Cloud only. Self-hosted Community nodes send no data to TUWA.

03 / Capabilities

EVM & Solana

Quasar Capabilities

Server-side transaction tracking, history and webhooks for self-custodial apps on EVM and Solana, in our cloud or on your own servers.

  • 01Server-side tracking

    Tracking to the Final Status

    Your server sends Quasar the hash of a transaction, and Quasar follows it until it succeeds, fails or is replaced, on EVM (including Safe and ERC-4337) and Solana, even after the user closes the tab.

    NetworksEVM & Solana

  • 02Cross-device sync

    History on Every Device

    Pulsar shows a wallet's transactions in the browser that sent them. Quasar keeps the same history on the server and returns it on any device through @tuwaio/quasar-sdk.

    HistoryEvery Device

  • 03Backend events

    Signed Webhooks

    Every final status reaches your backend as a signed webhook with retries, so your server can credit a deposit, update an order or notify a user without polling the chain.

    DeliverySigned + Retries

  • 04Cloud or self-hosted

    Open Source & Self-Hostable

    Run the same engine on your own infrastructure with the Apache-2.0 Quasar Community Edition. Deploy with Docker Compose, manage it from a Payload admin panel, and keep transaction data on servers you control.

    LicenseApache-2.0

Public beta: Quasar Cloud is free, with 1,000 free quota units for every organization, or self-host the free Community Edition.

04 / FAQ

5 questions

Quasar FAQ

Answers about how Quasar works, what it tracks, how it is protected and what it costs.

  • Your backend or a client app sends Quasar a transaction hash with @tuwaio/quasar-sdk. The engine reads the state of the transaction from a pool of RPC nodes. On EVM it sees a speed-up or a cancel from the nonce of the sender; on Solana it waits for finality. When the transaction reaches its final status, Quasar saves it and sends a signed webhook to your endpoints.

  • Both run the same NestJS engine on the same partitioned PostgreSQL 16 schema. Quasar Cloud is hosted and maintained by TUWA, with a multi-tenant dashboard, passkeys and email notifications. The Community Edition is open source under Apache-2.0: you host it with Docker Compose and manage it from a Payload admin panel.

  • Every status change of a transaction produces an event signed with your webhook secret (HMAC-SHA256, in the x-quasar-signature header). If your endpoint does not answer, Quasar retries with exponential backoff, and a delivery that keeps failing goes to a dead-letter queue.

  • Yes. Export the organization in the Quasar Cloud dashboard and import the encrypted file in the admin panel of your Community Edition node. The API keys, the webhook secrets and the transaction history stay the same; your apps change only the baseUrl of the SDK.

  • No. The client packages (Satellite Connect, Nova UI Kit) talk to the wallet of the user directly, and Quasar receives only public data: transaction hashes and addresses.

Quasar documentation

The API reference, apps and keys, quotas and webhook delivery.