/dashboard/ · a preview Designed
A look at the dashboard, before it has anywhere to run.
A picture, not a page. Every screen is here and the sample data is made up; none of the controls do anything — there is no account to log into and nothing hosted behind any of it. The same eleven screens are listed as text further down. We are showing it because a screen is easier to argue with than a paragraph, and because we would rather you knew exactly how much of it is real.
How to read it. Three states, and every screen says which it is at the top — the same three the rest of the site uses. Shipping, on this page, means in the harness, not hosted: the screen and the layer behind it are code in the public harness, and the work happens today — from your terminal. A screen greyed out is Designed: specified in a public issue, with nothing you can use yet. Six of the eleven are drawn normally; the other five are greyed, with the issue that specifies it linked where there is one, and the command you would use in the meantime.
Drawn for this page. Every name, count and hash in it is made up, except the crate and test counts, which are the real ones. No screenshot of a running system exists, because there is no running system.
The same thing, as a list
All eleven, at a glance.
Six of these you can do today, yourself, from a terminal — in the harness, not hosted. The other five are designed: specified in public issues, linked where there is one. Nothing here is a promise about a date.
| Panel | Status | What you do today |
|---|---|---|
| Overview | Designed | You look at the Cloudflare dashboard, or run wrangler deployments list. Issue. |
| Backends | Shipping | The list and the wizard that creates one are written. Today you write one composition file and deploy it with wrangler. Hosting is the issue that is left. |
| Database | Shipping | You reach it with wrangler d1 execute, or any Postgres client if you self-host. |
| Data browser | Shipping | The schema half is written — tables, columns, keys, relations, row counts. Rows, a SQL console and CSV export are not. Today you write the SQL. The issue that specifies the rest. |
| Deploys | Designed | You run the build on your own machine and deploy with wrangler. Issue. |
| Domains | Shipping | You add the custom domain in Cloudflare yourself. Issue. |
| Logs | Designed | You use wrangler tail, which shows the live stream and keeps nothing. |
| Secrets | Shipping | The layer ships and the screen that lists what is held is written too. Today you set them with wrangler secret put. Hosting is the issue that is left. |
| Environments | Designed | You deploy a second backend and wire it up yourself. Issue. |
| Backups | Shipping | You export with fz data export and keep the file. Issue. |
| Billing | Designed | Nothing: there is nothing to pay for yet. Issue. |
Shipping, Designed and Planned are the statuses the rest of the site uses, from the same place: the capability table. Here Shipping carries a qualifier — in the harness, not hosted: the screens and the layers behind them are code in the public harness, and the work happens today from a terminal, but nothing is hosted for you. The hosted service these screens picture is still Planned, and this site never describes it as running. A greyed row is Designed — specified in a public issue, with nothing to use yet — and links the issue that specifies it, where one exists.
Managed · Planned
Tell us to build it.
The waitlist is how we decide what to build first, and it is where every control on this page leads — the mock’s buttons included, since none of them can do their own job yet.
Open source · Shipping
Or skip the dashboard.
Everything the dashboard would run for you is already written and published. You can build it on your own machine and put it wherever you like, today, without us.