Cowrie Research

rotki

3 min read

rotki

  • Name: rotki
  • URL: https://rotki.com/
  • Category: open-source self-hosted crypto portfolio manager / accounting-and-tax reporting tool / privacy-first finance-ops software
  • Summary: rotki is a self-hosted crypto accounting and portfolio workstation. The useful distinction is simple: keys usually stay elsewhere, but the interpretation layer lives on the user’s machine instead of on a SaaS dashboard. That makes decoder coverage, accounting policy, exchange ingest, premium sync, and binary trust the real control surfaces.
  • What it does:
    • Lets users track balances across blockchain accounts, centralized exchanges, and manual balances from a local account encrypted on the user’s device
    • Generates profit/loss and tax-style accounting reports with configurable methods such as FIFO, LIFO, HIFO, and ACB
    • Connects to centralized exchanges via read-only API keys and supports a wide list of exchanges for balances and transaction-history ingestion
    • Tracks blockchain activity across EVM, Bitcoin, Substrate, and Solana account types and decodes historical events
    • Supports importing transaction data from CSV files and editing or supplementing decoded history when needed
    • Offers experimental EVM onchain transaction execution through WalletConnect or a browser-wallet bridge
    • Provides paid premium tiers that unlock expanded analytics, cloud backup and sync, priority support, and premium-only integrations
    • Publishes download-verification guidance using SHA512 checksums and GitHub Artifact Attestations for release binaries
  • Key claims:
    • The docs and README are direct that rotki is open-source, self-hosted, and privacy-first, with user data encrypted and stored locally rather than in a default cloud account
    • PnL and tax-style accounting are first-class product goals, with explicit support for FIFO, LIFO, HIFO, and ACB instead of vague portfolio-only language
    • The exchange-integration docs show that rotki is not just a wallet tracker; it is an ingestion layer for read-only exchange history and balances across a long list of venues
    • The chain-coverage docs make the product meaningfully multichain across EVM, Bitcoin, Substrate, and Solana account types, with event decoding layered on top
    • The premium materials show a real product boundary around sync, backup, analytics, and premium-only integrations, which matters because rotki otherwise presents itself as the local-first alternative to hosted dashboards
    • The onchain-transactions docs show the software is inching from passive accounting toward optional execution, but that path is still experimental and not the core note
    • The binary-verification guidance matters more than usual here because the trust pitch rests on local control; a privacy-first desktop app still needs a believable software-supply story
  • Whitepaper: No canonical standalone rotki whitepaper or litepaper surfaced in this pass. The clearest current sources of truth were the official documentation corpus, llms.txt, the first-party GitHub repository, and premium / verification / integration guides; see ../whitepapers/rotki-primary-sources-2026-04-30.md.
  • Sources:

Internal linkages

  • Best hosted-data contrast: zerion.
  • Best methodology-layer contrast when the question is public market measurement rather than private books and reports: defillama.

Control surface

  • rotki removes a SaaS operator from the default reporting loop, but it does not remove control questions. The leverage sits in decoder quality, chain and exchange coverage, accounting-method defaults, premium sync and backup boundaries, and whether users trust the shipped binaries.

  • That makes it useful as local-first finance-ops software, not as a neutral mirror of chain truth.

  • Last reviewed: 2026-06-14 UTC

Graph View