Scani vs rotki

If you self-host, yes: you run the whole stack, database and object storage included. Tier 1 uses your provider keys. Tier 2 keeps your UI, API, worker, database and SeaweedFS S3 on your infrastructure and uses one Scani Cloud key for AI, pricing, token lookup and supported wallet requests. Processing inputs leave your server; durable files and records stay local. Personal exchange and broker credentials remain local. There is also a managed tier, where the data is hosted for you. Both are the same codebase.

That is the main difference. Alongside exchanges and on-chain wallets, Scani connects to broker and bank APIs (Interactive Brokers, Wise, Airwallex), so cash, equities and crypto reconcile into one total. It also computes time-weighted and money-weighted (XIRR) returns across the whole portfolio rather than per asset class.

Yes. From an empty directory, `curl -fsSL https://raw.githubusercontent.com/MGrin/scani-oss/main/scripts/self-host.sh | bash` generates its own secrets, applies migrations and brings the stack up on localhost:8080. Every tagged release publishes pre-built multi-arch images for the five services. Bring your own Postgres, Redis and S3-compatible storage, or let the bundled containers handle them. Tier 1 uses your provider keys. Tier 2 keeps your UI, API, worker, database and SeaweedFS S3 on your infrastructure and uses one Scani Cloud key for AI, pricing, token lookup and supported wallet requests. Processing inputs leave your server; durable files and records stay local. Personal exchange and broker credentials remain local.

Every tier is free during the beta. There is also a live read-only demo at demo.scani.xyz with no account, no email and no credential, if you want to look before connecting anything.