Finance and accounting decision
Bolsai
Keep paying — reproducing decades of adjusted prices, reconciled TTM fundamentals across hundreds of tickers plus enterprise-grade reliability is a multi-week, data-engineering effort unlikely to be practical for one developer to mirror.
Visit website↗Not priced
No pricing page we fetched carried a figure, so there is nothing to compare against. The build side is still real.
$100one-off180 h to build
$150/mo12 h/mo upkeep
No published price to break even against.
The code exists. It is not what you are paying for.
This project is real, published, and does the core job — and this page still says keep paying. What the subscription buys is product polish and ongoing maintenance, and none of that ships in a repository. Fork it anyway if you want to. Go in knowing what it does not carry. What stays hard ↓ · All Bolsai alternatives, with the arithmetic →
What a replacement has to do
- Provide normalized Brazilian market data via an authenticated REST API
What it still won’t have
- 40+ years of fully adjusted price history and long-running data quality work
- Precomputed TTM fundamentals across many tickers and reconciled accounting choices
- Coverage breadth (350+ equities, 400+ FIIs) and FIIs-specific fields (NAV, vacancy, tenants)
- Enterprise features: SLA, dedicated onboarding, bulk exports and contract-based guarantees
- Polish: consistent field names, CSV export options, and integrations with Claude/ChatGPT via documented patterns
What remains hard
- Product polish and ongoing maintenance
First-year cost
No published price
Bolsai does not publish a price we could read, so there is nothing to compare against. What building costs is below.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted Brazilian market-data API using Python, FastAPI, Postgres, Redis, and Airflow. In scope: (1) ingest B3 price feeds and CVM filings into raw tables, (2) ETL jobs that compute adjusted OHLCV (applying corporate events) and compute TTM fundamentals for each ticker, (3) REST endpoints /fundamentals/{ticker}, /stocks/{ticker}/history, /screener with API-key header auth, rate-limiting via Redis, and a /keys dashboard to create/rotate/revoke keys, (4) daily scheduled updates, health checks, and basic Prometheus metrics. Out of scope: enterprise SLA contracts, paid billing integration, nationwide coverage of FIIs beyond a small test set, and advanced NLP/LLM integrations. Include error handling, retries for failed ingests, unit tests for ETL transforms, and integration tests for the API endpoints.How we checked
How the score was reached
- Pay verdict base20
- An open-source build was found+5
- 3 cited sources+3
- Evidence score28
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 3
Every page the run actually retrieved.
- official productbolsai — API de Dados Financeiros do Brasil
- official docsbolsai — Documentação da API
- open sourceFinMind/FinMind
Integrity checks
What held up, and what did not.
