Short version
Local first today. Hosted preview stays labeled.
Local stays calm and usable without sign-in. Free and Pro describe the hosted preview lane honestly, and self-hosting stays a separate operator deployment path.
Plan comparison
qardo has three simple plan lanes to understand. Local is the calm stable wallet today. Free and Pro describe the hosted preview lane with explicit rollout labels, draft pricing stays labeled until billing readiness is validated, and self-hosting stays a separate operator path instead of being hidden inside everyday wallet pricing copy.
Short version
Local stays calm and usable without sign-in. Free and Pro describe the hosted preview lane honestly, and self-hosting stays a separate operator deployment path.
Operator / self-hosting
This pricing page covers everyday wallet lanes. If you need self-hosting, start in the operator docs map and then use the self-hosting baseline instead of treating the wallet app or hosted preview plans as your deployment entry point.
Tier summary
The top row is meant for fast comparison. It tells you what each tier is for before you dig into the deeper matrix below.
Detailed comparison
Ready-now claims stay visible everywhere. Account-only details and billing-readiness truth stay hidden on the production brochure unless the surface can label them honestly, so this page does not quietly over-promise.
| Feature | Local | Free | Pro |
|---|
Lane summary
The pricing table covers everyday wallet plans. qardo also keeps a separate self-hosted operator path visible so nobody mistakes deployment control for a default end-user promise.
Stable production
No account required, no default sync promise, and a calmer device-local wallet for carrying cards today.
Hosted preview
Signup, recovery, hosted preview sync, and any paid checkout belong to the hosted preview or beta lane only when the deployment enables them and billing readiness has been validated.
Self-hosted operator
Operators can run qardo on their own stack and choose rollout policy, infrastructure, and providers without changing the stable local-first story for everyday users. Start from the operator docs map, then use the self-hosting baseline for the current deployment contract.