Scani tRPC gateway: object storage, mail, OG, token search. github.com/MGrin/scani-oss
8.9K
The shared-service tRPC gateway for Scani — the self-hostable, open-source portfolio tracker for crypto and traditional assets.
The local Tier 1 stack uses this service for token lookup and metadata. Scani
runs the hosted service for Tier 2: versioned processing.v1 endpoints provide
AI, pricing and supported public-wallet requests using Scani's provider keys.
Customer API keys also reach token lookup and constrained authentication email.
Tier 2 customers run their UI, API, worker, database, Redis and S3 themselves.
They supply one Scani Cloud key and do not run a local data-provider. Durable
files stay in customer-owned S3; processing inputs travel to Scani Cloud.
storage.* and arbitrary email.send are restricted to Scani's internal keys.
Personal exchange and broker credentials remain on the customer's instance.
latest — highest semver release tag1.2.3 / 1.2 / 1 — semver release tagsBundled into the reference
docker-compose.prod.yml
in the OSS repo:
git clone https://github.com/MGrin/scani-oss.git
cd scani-oss
./scripts/self-host.sh
| Variable | Purpose |
|---|---|
DATA_PROVIDER_API_KEY | Bearer token the api + worker present to reach this service (must match SCANI_CLOUD_API_KEY on api/worker) |
DATABASE_URL | Postgres — used for upstream-call audit log + cache |
Platform keys belong on Tier 1 services or on the Scani-managed cloud service, not on a Tier 2 customer installation:
COINGECKO_API_KEY, FINNHUB_API_KEY — pricingOPENAI_API_KEY — AIETHERSCAN_API_KEY — EVM wallet balances (one key covers all EVM chains)HELIUS_API_KEY — SolanaFASTMAIL_API_TOKEN, or SMTP_URL / SMTP_FROM — magic-link email deliveryFull annotated list: .env.example.
Full source, architecture, and contribution guidelines: https://github.com/MGrin/scani-oss
MIT licensed.
Content type
Image
Digest
sha256:7887e7547…
Size
69.5 MB
Last updated
3 days ago
docker pull scani/data-provider