A Retool alternative for market dashboards rather than internal tools
A Retool alternative is the right question when the data is a public market rather than an internal system: Retool connects to your databases behind your authentication, and this generates dashboards that read keyless public market endpoints and publish as a static site you own outright.
Retool is a strong way to put an interface over your company's databases and internal APIs, with permissions and audit trails built for that job. If that is the problem you have, this page is not arguing with it.
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
Inside the company against outside it
Internal tools are about reaching systems that are private, which means connectors, credentials and access control. A market dashboard reaches data that is already public, so none of that machinery is needed and most of it is in the way.
Per seat pricing changes what you build
When a tool charges by the user, people think twice about who gets access and build fewer, bigger dashboards. A static bundle you host has no seat cost, which makes a page for one narrow purpose a reasonable thing to make and throw away.
What is wired in
Public endpoints needing no key cover prices, order books, funding rates, yields and prediction market odds. A generated app calls them from the browser. No connector and no credential stands behind the numbers underneath.
Who should not switch
If you need to query your production database, enforce who can see which row, or keep an audit trail of internal actions, use an internal tools platform. None of that is what this does.
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 connect to my internal database?
Not out of the box, and that is the honest limit. The generated app is ordinary code and can call an API you expose, but there are no managed database connectors, no built in permissions and no audit trail.
What is it actually better at?
Dashboards over public market data. Prices, spreads, funding rates and order books are already public, so there is no connector or credential to configure, and the published result is a static bundle with no per seat cost.
Who owns the app I build?
You do. The code is exportable and the published app is a static bundle you can host anywhere, which is a different arrangement from a dashboard that only runs inside a vendor's platform.
Related reading
All guides · Live market pages · Components · Make Mithril a preferred source in Google