A Metabase alternative for live markets rather than a warehouse
A Metabase alternative is the right question when the data is a live market rather than a warehouse: Metabase queries a database you maintain and caches the result, and this generates dashboards that read public market endpoints at render, where a figure a few minutes old is already wrong.
Metabase is a good way to let people ask questions of a warehouse without writing SQL, and for business intelligence over data you already collect it is a sensible default.
Start from a working app
HyperBoard: Crypto Market Dashboard
prices, funding rates, open interest and liquidity across crypto perpetual markets, in three live tabs.
Open the template
A warehouse is a record, a market is a state
Business intelligence assumes the data is history: rows that were written and will not change. A market is the opposite, a number that is only true for a moment. Tools built for the first assumption cache aggressively, which is exactly wrong for the second.
Caching is the difference that matters
A dashboard refreshed every hour is fine for yesterday's revenue and useless for a spread. Where the whole point of a figure is that it moves, the question becomes how old the number is, and a page that does not say is worse than no page.
What is different here
The generated app reads public endpoints at the moment someone loads it, states when it read them, and says so plainly when a venue does not answer rather than serving something stale. Every number below carries the moment it was read, which is the habit this whole argument is about.
Who should not switch
If your question is about data you have collected, in a database you run, answered for colleagues who do not write SQL, use business intelligence software. Metabase is a good one and this is not a substitute.
Live, right now, on this page
| Market | Price | Funding | 24h volume |
|---|---|---|---|
| BTC | $83,703.50 | 0.0013% | $344,447,532 |
| ETH | $2,687.35 | 0.0013% | $274,277,015 |
| SOL | $119.18 | 0.0007% | $84,823,612 |
| HYPE | $86.76 | 0.0013% | $3,054,440 |
Live market data, read at render from a keyless public endpoint. The same one a generated app here would call. Read at 2026-09-30 11:12 UTC; accurate as of that time and not afterwards.
Start from a working app
Open, change it, publish your own
OddsBoard
a live visualiser of Polymarket and Kalshi prediction markets, in six views.
Open the template
Working templates built around what this page covers. Open one, change it, and publish your own.
- HyperBoard: Crypto Market Dashboard
prices, funding rates, open interest and liquidity across crypto perpetual markets, in three live tabs.
- Helix
a live trading terminal with a candlestick chart, a watchlist, an order ticket and open positions with live PnL.
- OddsBoard
a live visualiser of Polymarket and Kalshi prediction markets, in six views.
Common questions
Can this query my database?
No. It builds apps that read live public market endpoints, not a warehouse. If your question is about data you have collected and stored, business intelligence software is the right category and this is not in it.
Why does caching matter for market data?
Because a figure whose whole purpose is that it moves is wrong as soon as it is stale. A dashboard refreshed on a schedule is fine for last month's revenue and misleading for a spread, so a live page has to say when it read the number.
What does the generated dashboard show?
Whatever public market endpoints you point it at: prices, order books, funding rates, yields and prediction market odds, read when the page loads, with the read time stated and an honest message when a venue does not answer.
Related reading
All guides · Live market pages · Components · Make Mithril a preferred source in Google