About the stack

Less machinery. More certainty.

Stack #1 is for websites that should look excellent, load quickly, and survive repeated deployments without persistence worries.

Why it suits our process

GitHub pushes trigger Coolify builds. Astro produces static assets. Nginx serves them. There is no live application server to babysit and no database to preserve. The result is a site that is easy to inspect, easy to edit, and easy to redeploy.

When a project needs stored data or login behavior, it graduates to Stack #2. Until then, this static stack keeps things lean.