dash-b · Features · Self-hosting
Take the whole thing.
Not an export of your data — an export of the designer, running on your server, with your work already in it.
Why this exists
Every tool promises you can export
What you usually get is a JSON file and a wish of luck.
Here you get the application: the same designer, the same widgets, the same designs, on a server you control.
What that actually means
Four things worth knowing before you rely on it
It never needed a plan
Exporting is not a Team feature and never has been. If you stop paying, your designs stay yours and they keep working. This is the answer to the question everyone is too polite to ask.
No build step
Static files. Nothing to compile, no package manager to satisfy, no version of Node to get wrong — the app has no runtime dependencies at all. Put it behind any web server you already run.
Some things need a server, and they say so
Anything that talks to a service — publishing, the AI, live collaboration — degrades visibly rather than failing silently. You always know which half of the product you are looking at.
Two sizes of the same idea
Export one design as a standalone page when you only need the result. Export the designer when you want the person on the other end to be able to change it.
Who does this
Handover, and clients who cannot use a hosted tool
Two common reasons. The first is delivery: the work is finished, the client owns it, and nobody wants an ongoing dependency on a supplier. The second is policy — a clinic, a school, a public body, anyone whose rules say the application lives inside their own boundary. Both stop being reasons to turn down the job.
Try it hosted first. The door out is not going anywhere.
Designing is free forever with no account, and the export has no plan attached to it.