Tier 3 — fully managed

Summary

Tier 3 is “someone else runs everything”. You sign in to a hosted Scani instance; the operator runs the api, worker, data-provider, Postgres, Redis, S3, and the SPA on their hardware.

From your perspective:

You have a username + password (or magic-link / OTP).
You connect integrations the normal way.
Your data lives in the operator’s Postgres.
Your encrypted integration credentials live in the operator’s Postgres, encrypted with their ENCRYPTION_KEY.

What this gets you

Zero operational burden.
The operator handles upgrades, backups, monitoring, scaling.
All you do is use the app.

What this costs

You trust the operator with your portfolio data.
You trust the operator’s ENCRYPTION_KEY is well-managed.
You can leave at any time (the operator can provide an export of your data), but it’s a “fork your data” move, not a config flip.

How it’s actually built

Tier 3 is just Tier 2 where the operator is also you. The same codebase, the same binaries, the same data-provider, the same SPA. The cloud-management surface (CLOUD_MANAGEMENT_ENABLED=true on the data-provider) provides:

DB-backed cloud API keys (so the operator can mint per-user keys rather than sharing one).
A Better-Auth cookie session for the management console.
Postgres-backed per-request metering (cloud_usage_events table) so the operator knows what to bill / rate-limit / shut down.

If you’re considering running a Tier-3 deployment for others (rather than using one), the operator-side documentation isn’t part of this OSS docs site yet — the open-source code supports it, but the operational runbook is a separate effort. Open an issue if you’d like to see it.

Switching tiers from a Tier-3 instance

A Tier 3 user can move to Tier 2 by:

Asking the operator for a data export (Scani ships data-export functionality under the user-data-delete job pipeline, which doubles as an export when the delete flag is unset).
Spinning up a self-hosted Tier-2 stack (Tier 2 overview).
Importing the data.

A migration tool to automate this is on the wishlist; the manual path works today.