Hobbyists
Free to startRun everything on one machine. Chart live ticks, build dashboards from OpenBB-compatible widgets, and keep your own history instead of renting it.
- Starts with
- A laptop and free data keys
- Adds
- Your own tick history and studies
We call it vibe integration: take the specialist for each job (OpenBB (now OpenBQ) for a platform, kdb+ for ticks, Delta Lake for history, DuckDB for research, Lightweight Charts for drawing), join them through tested contracts, and let an AI agent install and maintain the result while you approve each change. Built for hobbyists, academics and small investors, from one laptop to a whole lab.
One stack. Each layer is useful alone and better together.
The tools trading desks rely on (tick caches, versioned history, reproducible queries) usually come bundled with enterprise contracts. We package the same habits as open-source tools you can run yourself.
Run everything on one machine. Chart live ticks, build dashboards from OpenBB-compatible widgets, and keep your own history instead of renting it.
Answer the referee’s question: what did the data say on that date? TemporalDB is designed to separate when a fact applied, when it was published and when you received it, and to record a receipt for every query run.
Keep the OpenBB backends you already use. BDOBB reads them, then adds pivots, calendar-aware time math, pinned and locked widgets, and multi-dashboard workspaces.
Status chips say what exists today. Shipping means released code. Preview means built and running in our stack, but not yet packaged on its own. In design means an approved architecture with no deployment yet.
A desktop and browser dashboard that reads the same OpenBB backends as OpenBB Workspace and Workspace Lite, then adds the analysis desk around them.
A database for research and investing that keeps every captured response, every revision and every query receipt, so a backtest sees only what was knowable at the time.
A full technical charting package on an open rendering canvas: live ticks, studies computed on the server, drawings that survive resizes, and layouts you can save.
Integrated suites are convenient but shallow. Specialist tools are deep but take work to join. An AI agent following a runbook you approve makes the second option practical: it inventories your machine, proposes a plan, previews every change, brings services up one at a time and proves they work.
The companion Substack series, Adventures in OpenBQ, explains how we got here and gives the instructions for each step. Run them by hand, or hand them to an AI agent like Claude Code or Codex. Each installment includes the gotchas, so you don’t waste time debugging. More about the series
Each step keeps the same dashboards, queries and charts. You change where things run and which free or paid licence you use, not how you work.
Hobby projects, coursework, a personal portfolio.
Always-on capture, several devices, a family or a study group.
Shared research, many users, audited replays.
Our code is Apache-2.0. The building blocks underneath are open source too, with one clearly marked exception.
| Component | Role | Licence |
|---|---|---|
| BDOBB and its openbb-docker backend | Dashboard client; data, tick and study services | Apache-2.0 |
| DuckDB | Query engine for TemporalDB | MIT |
| DuckLake | Catalog and table format for TemporalDB | MIT |
| Delta Lake | Tick vault history for Art’s Charts | Apache-2.0 |
| TradingView Lightweight Charts | Chart rendering canvas | Apache-2.0 |
| kdb+ / KDB-X from KX | Live tick cache | Proprietary, free tiers |
DuckDB is MIT-licensed per the DuckDB FAQ; the DuckLake specification and extension are MIT per ducklake.select; Lightweight Charts is Apache-2.0 per its GitHub repository.
Small, careful habits (keep the evidence, record what you knew, chart what actually traded) add up. Start with one tool and add the next when you need it.