# ADR-0001: Deploy target is Coolify (SIAX Cloud fleet), not Vercel - **Status:** Accepted (config declares it; migration not yet executed) - **Date decided:** 2026-08-09 (commit `ad042d8`, "fix(deploy): declare Coolify as the deploy target, not Vercel") - **Date of this record:** 2026-08-11 (BACKLOG P1-2 — this ADR documents an already-made decision retroactively; it does not introduce a new one) ## Context 0pt was originally scaffolded and deployed on Vercel (Hobby/free tier, project `0pt`, scope *Simon Axelsson's projects*). SIAX Cloud's platform mandate is to replace paid SaaS with self-hosted fleet infrastructure (Hetzner + Coolify), matching every other SIAX Cloud OS repo (`n0d`, `st0re`, `aud0`, ...). ## Decision `siax.config.json`'s `deploy.target` is `"coolify"`, not `"vercel"`. A Dockerfile written for Coolify (multi-stage, non-root `node` user, `HEALTHCHECK` against `/api/health`) and `.gitea/workflows/cd.yml` (POSTs a restart to a Coolify app UUID on push to `main`) both exist and are committed. ## Consequences - **This is a config-and-tooling change, not a traffic cutover.** As of this record, no Coolify application has been provisioned for this repo — `cd.yml`'s `COOLIFY_APP_ID` is a literal placeholder that fails the job loudly on purpose (see the guard step) rather than posting to a bogus endpoint. The live instance of `0pt.app` is still served by Vercel. > **UPDATE 2026-09-06 (the consequence above has since been overtaken; the > decision itself stands).** **CORRECTED 2026-09-06 — this is no longer true.** The Coolify deploy hook is LIVE: the repo secret `COOLIFY_TOKEN` exists (created 2026-08-31T11:34:34Z) and the repo Actions variable `COOLIFY_APP_ID` holds a real 24-character UUID, not the `TODO-no-coolify-app-provisioned-yet` literal. Both guard conditions in `.gitea/workflows/cd.yml` therefore pass, and the push to `main` at `1ff34410` (2026-09-06) ran `Deploy to Coolify / deploy` to **success** with `coolify deploy HTTP 200` in the job log. **Every merge into `main` now fires a real redeploy against cloud.siax.io.** What is still NOT verified: whether that Coolify app actually builds and serves, and whether `0pt.app` DNS points at it or still at Vercel — nobody has probed the running site. > > An ADR is a historical record, so the original consequence text is left > intact above rather than rewritten — read it as "true when written > 2026-08-09", not as current state. - Flipping the config was deliberately decoupled from the actual cutover: it states intent (BACKLOG P0-2 / P3-1 own the "provision the Coolify app, cut DNS, decommission Vercel" work, gated on a dump-before-write blocker per the standard's "safe to run now" classification). - Until the cutover happens, docs describing Vercel as *where 0pt actually runs today* are accurate; docs prescribing Vercel as *the plan going forward* are stale (see BACKLOG P2-5 — `docs/02-architecture.md`'s "Hosting" section is marked SUPERSEDED for exactly this reason). ## See also - `docs/architecture/ARCHITECTURE.md` §6 "Deploy", §9 "Öppna frågor" - `README.md` "Deploy" section (kept current with the live/target split) - `docs/compliance/BACKLOG.md` P0-2, P1-17, P3-1