Hosting & deployment
The dashboard is a static React app that reads a single data.json at runtime — serve it locally, or export it and deploy it to any static host.
Serve locally
The quickest way. atlas serve analyzes, caches under ~/.atlas/, and serves at a
local link.
atlas serve # http://localhost:4321
atlas serve --port 8080
atlas serve --no-open # print the link, don't open a browser
atlas serve --reanalyze # force a fresh scanExport a static bundle
atlas export produces a self-contained folder: the dashboard assets plus a
data.json snapshot. The app fetches ./data.json at runtime, so the bundle is fully static — no
server logic required.
atlas export --out-dir ~/atlas-site~/atlas-site/
├─ index.html
├─ assets/ # JS/CSS bundles
└─ data.json # the analysis snapshotPreview it locally with any static server:
npx serve ~/atlas-siteDeploy it
Because the bundle is static and uses hash-based routing, it works on any static host with no SPA-rewrite configuration.
netlify deploy --dir ~/atlas-site --prodAny container or CI works too: the bundle is just static files — serve them with npx serve,
python -m http.server, Caddy, or copy them into any web server's root.
Keeping it fresh
data.json is a point-in-time snapshot. To update a deployed site, re-run
atlas export --reanalyze and redeploy the folder — for example as a CI step on merge to main.
Where data lives
| Location | Written by | Commit it? |
|---|---|---|
.atlas/ in your repo | analyze | Optional — these are JSON reports. |
~/.atlas/cache/<hash>/ | serve, export | No — per-user cache outside the repo. |
<out-dir>/ from export | export | This is your deployable artifact. |
serve and export never write into the scanned project. Only analyze does.