Wag3s vs Rotki: Privacy/Control vs Convenience/Coverage

This is the rare comparison where the other tool's headline strength is real and hard to match on its own terms. Rotki is open-source, self-hosted, and privacy-first, with your data kept locally rather than on someone else's server, and it does genuine accounting and tax work, not just dashboard tracking. So the honest axis here is not category at all, the way it is for a pure tracker. It is privacy and control against convenience and coverage. Below is that trade-off laid out plainly, including where Rotki's local, open-source model is clearly the right call and where hosted jurisdiction depth wins.

The trade-off in brief

• Rotki is open-source (AGPLv3), self-hosted, and privacy-first: local encrypted data that never sits on a third-party server, with tracking, analytics, and accounting.
• Wag3s is a hosted tax-and-accounting tool with jurisdiction depth (per-country cost-basis methods, the French FEC, B2B accounting via Ledger) and no self-hosting or maintenance.
• The real axis is self-sovereign privacy and control versus hosted convenience and jurisdiction/B2B coverage, not better versus worse.
• Rotki genuinely does accounting, so this is not a tracker-vs-tax category gap.
• Decide by what you must not compromise.

What Rotki is genuinely good at

Rotki is the privacy-first, open-source (AGPLv3), self-hosted option. Financial data, API keys, and wallet addresses are kept encrypted and stored locally, never handed to a third-party server, while still providing portfolio tracking, analytics, and accounting under the user's own control. If self-sovereign data handling is a hard requirement, Rotki's local-first, open-source design is a genuine and distinctive strength that a hosted tool, by definition, cannot replicate. We state that plainly.

The AGPLv3 open-source license is also worth unpacking for technically sophisticated users. It means the full source code is publicly auditable — you can verify exactly what Rotki does with your data and how its calculations work. For users who distrust black-box financial software or work in privacy-sensitive contexts (security researchers, high-net-worth individuals, or users in jurisdictions with high financial surveillance risk), this auditability is a substantive advantage, not a marketing claim.

The local-encrypted storage model means your wallet addresses, API keys for exchanges, and complete transaction history are stored on your own machine, encrypted. Even if Rotki's servers were compromised (there are no Rotki servers holding your data), your financial history remains private. This is a genuinely different threat model from any hosted tool.

Where Wag3s is different

Wag3s is a hosted tax-and-accounting layer optimised on different priorities:

• jurisdiction depth: per-country cost-basis methods (US per-wallet, UK pooling, FR 150 VH bis) and the French FEC;
• B2B accounting: company books and FEC via Ledger, plus the audit trail;
• operational convenience: no self-hosting, setup, or maintenance.

Rotki optimises for self-sovereign privacy and control; Wag3s optimises for hosted convenience and jurisdiction/B2B coverage. That is a trade, not a ranking.

This is not a category gap

Unlike a pure dashboard, Rotki does accounting and tax. So this comparison sits honestly on the privacy-vs-convenience and coverage axes, not a "they can't do tax" gap. The real differentiators to weigh are:

• the data model: self-hosted local (Rotki) versus hosted (Wag3s);
• the jurisdiction breadth of tax handling;
• B2B and FEC depth.

Weigh those, not a feature-count headline.

The self-hosting trade-off

Rotki's local-first design maximises privacy and control. By common account it also asks more of the user: setup and maintenance effort, and performance considerations on very large datasets. A hosted tool removes that operational burden at the cost of trusting a provider's data handling (the privacy trade-offs generalised). Neither is universally right.

Practically, self-hosting Rotki means: installing and updating the application locally, managing database backups (if your local storage fails, your Rotki data fails with it unless you have backups), and accepting that new exchange integrations or protocol support may lag behind hosted tools. For a privacy-first individual who is comfortable with this operational profile, these are manageable costs. For a company finance team that needs reliable uptime and minimal operational overhead, the hosted model is lower friction.

When to use which

Some users even reconcile a self-hosted record against a hosted computation. Decide by what you must not compromise.

Pricing comparison

Rotki is free and open-source for self-hosting (AGPLv3). A Rotki Premium subscription is available for users who want cloud sync (encrypted), premium data sources, and priority support. The premium tier is priced accessibly for individual investors, well below most hosted crypto tax tools.

Wag3s Folio and Ledger are priced as a Finance OS for teams, with per-module and per-transaction pricing that scales with team size and volume. For a privacy-first individual who is comfortable self-hosting, Rotki's free tier is the most cost-efficient option. For a team that needs B2B accounting, French FEC, and payroll alongside tax, Wag3s's modular scope is not replicated by Rotki at any tier.

The cost comparison is somewhat misleading in isolation: the real cost of self-hosting includes the time to set up, maintain, and back up the installation. For a technical individual who values that control, it's worthwhile. For a company finance team, the operational cost of self-hosting outweighs the subscription savings.

Migration path: Rotki to Wag3s

For users who have been using Rotki and want to add Wag3s for B2B accounting or deeper jurisdiction tax:

1. Export Rotki's accounting data. Rotki provides CSV and other export formats for transaction history, PnL reports, and accounting entries. Export the full history for the periods you want to bring into Wag3s.
2. Import into Wag3s Folio. Use the exported transaction history as the starting dataset. Folio will recalculate cost basis using the jurisdiction's method.
3. Validate cost-basis calculations. Compare Folio's output for the last closed tax year against Rotki's PnL report for the same period. Small differences may arise from minor categorization differences in fee treatment or DeFi event decomposition.
4. Activate Wag3s Ledger for B2B accounting. If entity books are the primary reason for moving (Rotki does accounting, but B2B FEC depth is the differentiator), Ledger ingests the same transaction set from Folio.
5. Consider a dual-system approach. Some users retain Rotki for the self-hosted privacy model while using Wag3s for specific jurisdiction tax outputs or B2B accounting that Rotki's coverage does not yet match. This keeps self-sovereign records while covering gaps.

Practical guidance

1. Identify your hard requirement: self-sovereignty and privacy, or convenience and coverage.
2. If privacy and open-source are non-negotiable, Rotki's design is the natural fit.
3. If you need jurisdiction depth, B2B/FEC, and hosted convenience, Wag3s fits.
4. Weigh the data model and coverage, not a feature count.
5. Confirm the tax position per jurisdiction with an adviser, whichever you choose.

How vendor tools compare

Rotki is the open-source, self-hosted, privacy-first benchmark and does accounting; Koinly and CoinTracker are hosted and tax-leaning. The honest framing is that this is a priority decision (privacy and control versus convenience and coverage), not a quality ranking. Match it to what you cannot compromise.

Where Wag3s fits in

Wag3s Folio and Wag3s Ledger provide hosted, jurisdiction-deep tax and B2B accounting (per-country cost basis, FEC, audit trail) for users who prioritise coverage and convenience. At the same time, we openly acknowledge Rotki's self-hosted, open-source privacy as the right call when self-sovereignty is the hard requirement. See the Folio and Ledger pages.

Further reading

• Crypto Portfolio Tracker vs Tax Software
• Crypto Portfolio Privacy & Watch-Only Trade-offs
• Wag3s vs CoinTracker
• Best Crypto Portfolio Tracker 2026
• Crypto Cost Basis Methods 2026
• The FEC for Crypto in France

Sources

• Rotki — publicly stated positioning: open-source (AGPLv3), self-hosted, privacy-first; data/API keys/addresses encrypted and stored locally, never on a third-party server; tracking + analytics + accounting — rotki.com
• Self-hosting trade-off: maximal privacy/control vs more setup/maintenance and large-dataset performance considerations (common account); hosted = convenience vs provider-trust
• Wag3s positioning: hosted, jurisdiction-deep tax + B2B accounting/FEC — a priority trade vs Rotki's self-sovereign design (positioning as of 2026, subject to change)