When static hosting is enough
Static hosting serves files that are already built, such as HTML, stylesheets, images, and browser scripts. It works well for documentation, marketing pages, and other sites whose content can be generated before deployment. The host delivers the files without running your application code for each visit.
Because no per-request application code runs, static hosting cannot perform server-side work that depends on the incoming request. If a page needs private credentials, live database access, or request-specific computation, those tasks need a separate supported service or an edge runtime. Do not put private secrets into public files just to make them available to a static page.
When to use an edge host
An edge host runs code when a request arrives, so it can handle dynamic responses and server-side logic. IaGenify counts requests handled by this runtime as edge request usage. Select it when the deployed application actually needs that execution model, and review the framework and runtime settings required by the host.
Before choosing, list which routes are static and which require computation or protected data. A mostly static site may use static hosting for its public pages and a separate edge endpoint for dynamic operations, if that architecture is supported. After deployment, test the public routes and confirm that the host type matches the work each route performs.