Skip to content

docs(roadmap): add OpenBB as the reference (🐐) project #27

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
robertoecf merged 2 commits into from
Jun 25, 2026
Merged

docs(roadmap): add OpenBB as the reference (🐐) project #27

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a5325a4
docs(roadmap): add OpenBB as the reference project in lessons learned
claude Jun 25, 2026
9a18ace
docs(roadmap): address review — repo link + neutral heading
claude Jun 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
34 changes: 34 additions & 0 deletions ROADMAP.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -79,6 +79,40 @@ Status: **v0.1.0 — alpha, release-ready for local/self-hosted use.**

## 📚 Lessons from adjacent projects

### From [OpenBB-finance/OpenBB](https://github.com/OpenBB-finance/OpenBB) (Python, global) — the reference 🐐

The closest large-scale analogue to what we're building, and the bar to measure
against. OpenBB's Open Data Platform is a *"connect once, consume everywhere"*
layer that exposes the same standardized data across a Python SDK, a CLI, a
FastAPI REST server, an MCP server for AI agents, Excel, and the OpenBB
Workspace UI. That is precisely our thesis (lib + REST + CLI + MCP over a single
normalized core), validated at scale.

Evaluation:

- ✅ **Single normalized core, many surfaces.** Our `sources/<source>/` feeding
one model that the Python lib, REST, CLI and `/mcp` all reuse mirrors their
architecture — we are directionally correct, keep it that way.
- ✅ **MCP as a first-class surface.** OpenBB ships an MCP server alongside REST;
validates our early bet on `/mcp` instead of treating it as an afterthought.
- 🟡 **Provider/extension system as installable packages.** OpenBB lets third
parties add data sources *without forking core* — separate extension repos,
discovered at runtime. Our `sources/` are in-tree today; a plugin/entry-point
mechanism is the natural path once external contributors want their own
source without a PR to core.
- 🟡 **"Build once, deploy everywhere" templates.** A scaffolding command for a
new source (`findata new-source <name>`) would lower the contribution bar the
way their extension template does.
- 🟡 **Spreadsheet surface.** Their Excel add-in is a reminder that many BR
analysts live in spreadsheets; a thin `=FINDATA(...)` bridge over the REST API
is a cheap, high-leverage future surface.
- ❌ **AGPLv3 + enterprise Workspace/Hub.** OpenBB is AGPLv3 with a hosted
pro tier. We are deliberately MIT and self-host-first — do not import the
account/Hub/proprietary-provider machinery; it cuts against the manifesto.
- ❌ **Global/paid-provider breadth (FMP, Polygon, etc.).** Our scope is BR
public sources with no API keys; chasing global paid providers would dilute
the "if the data is public, the infra should be too" thesis.

### From [Tpessia/dados-findanceiros](https://github.com/Tpessia/dados-financeiros) (TS/NestJS, BR)

Already absorbed:
Expand Down
Loading