Quasar Community Edition v0.2.0: Cloud-to-Community Migration with Zero Lock-In from TUWA

Hey Product Hunt community! 👋

We just rolled out Quasar Community Edition v0.2.0, solving one of the biggest dilemmas in Web3 developer tools: vendor lock-in.

Start on Quasar Cloud for convenience, move to your own self-hosted server whenever you want — without losing data, transaction history, or breaking your live apps.

Here is how the Cloud → Community Edition migration works:

📦 Cloud Export & Encryption

• Organizations export directly from their settings page, confirmed via password + 2FA.

• End-to-end encrypted (AES-256-GCM) in 64 KiB frames using a one-time ephemeral import key, so massive histories never sit in memory.

• Reads a consistent live database snapshot with zero downtime while Cloud tracking remains uninterrupted.

• Audit emails sent automatically to all organization owners upon export.

📥 Community Node Import

• One-click import in your node’s admin panel with pre-flight dry-run validation.

• Live progress tracking and a comprehensive final report.

• Resumable delta sync: re-run the export later to pull only new transactions and status changes without duplicates.

• Secrets are safely re-encrypted using your node-local keys.

🔄 Seamless Workspace Migration

• One-line configuration switch: just update your app’s baseUrl. Webhook receivers change nothing.

• Full preservation of App IDs, API keys, and webhook signing secrets.

• Transports full historical transaction ledgers, 30-day delivery logs, and payment records.

• In-flight pending transactions keep tracking automatically on your local node.

---

🔭 Next on the roadmap:

Native crypto payments in Quasar — non-custodial, direct wallet-to-wallet rails for EVM & Solana with live tracking

via @tuwaio/nova-payments.

Migration Guide: https://docs.tuwa.io/quasar/migrate-to-community

GitHub Repository (Apache-2.0): https://github.com/TuwaIO/quasar-community

Let us know your thoughts or feedback on self-hosting and data sovereignty!