Static Build or Dev Server: Choosing the Cheapest Option for Low‑Traffic Storybook

Goal

Determine the most cost‑efficient way to host Storybook for a project that receives fewer than 100 page views per day.

Constraints

The solution must keep documentation up‑to‑date for developers while minimizing compute and bandwidth costs. Core Storybook features such as component previews should remain available, but live editing may be sacrificed to reduce operational expenses.

Unresolved Decision

Should the team publish a static build of Storybook (generated by storybook build) to a cheap static hosting platform, or keep a lightweight Node.js dev server (started by storybook dev) that offers full interactive addons but incurs a small monthly compute cost?

Questions

• What is the monthly cost difference between hosting a static Storybook build on a free tier and running a minimal Node.js dev server for < 100 visits/day?
• How does disabling live editing and WebSocket‑based addons in a static build impact the usability of the documentation for contributors?
• Is the incremental compute cost of a small VPS or serverless function justified by the convenience of live authoring for a low‑traffic audience?