Getting started with Varuno
Varuno is currently in TestFlight internal testing on iOS (15.5 or later). This guide takes you from a fresh install to a working setup.
1. Install and create your account
Install the build through TestFlight, open Varuno and choose Create account. You’ll need an email address and password, and you must confirm the verification email on the same phone — the link opens the app directly. Details: Creating your account.
2. Complete onboarding
Onboarding is nine short steps: welcome, privacy, experience mode, region, income, universe, wallets, notifications and done. Two things worth knowing:
- The privacy step shows you where your data lives before you enter anything. Varuno enumerates what does leave your device, not just what doesn’t.
- Nothing commits until the final step — until then it is a draft, so you can safely go back.
The experience mode step lets you choose how much of the app you want: expense tracking only, wealth tracking, or the complete feature set. This is a view, not a commitment — switching modes later never deletes anything.
3. Your first wallet and transaction
Create a wallet under Wallets → +, then record an expense with + → Expense. The full walkthrough — including credit cards, retirement wallets and why transfers are not spending — is in Your first wallet and transaction.
4. Make it yours
- Budgets — monthly limits per category or overall, with optional rollover.
- Goals — savings targets funded by transfers.
- Bills — recurring obligations with reminders, shown on the dashboard.
- Salary — record your salary history and let Varuno estimate take-home pay and CPF contributions. Estimates only — not payroll advice.
- App lock — set a passcode and Face ID under Settings → Security. See Face ID and passcode lock.
5. Protect your data
There is no cloud backup by design — your finances stay on your device. Export a backup file early (Settings → Data → Create Backup) and store it somewhere you trust: Exporting your data explains why the file itself is readable and how to handle it.
If something breaks
You are using a test build; some rough edges are expected — the currently known ones are listed at Known issues. Reporting what you hit, via Report a bug, is the most useful thing a TestFlight user can do.