# Runtime placement decision

Choose the smallest sufficient runtime.

## Recommendation

- Decision: `local_or_managed_preview`.
- Reason: V1 is a static-first brand/portfolio site with local content files, no database, no background jobs, no accounts, no payments and no always-on internal service.
- What would make this decision change:
  - a CMS/admin workflow with real users;
  - background processing or social/media ingestion;
  - private database or document store;
  - staging API;
  - client-data separation or special isolation requirements.

## Local / managed preview

Use for simple sites, demos, static-first apps, Vercel previews and projects
without always-on internal services.

Project-specific note: local dev is enough for initial implementation and QA. A private Vercel/managed preview is useful only after Marius separately approves the provider/project scope.

## Proxmox LXC container

Use only when the project needs a small always-on internal service, background
worker, staging API, self-hosted preview, local service dependency or repeatable
sandbox without full OS isolation.

Required before action:

- read-only Proxmox health check;
- CPU/RAM/disk estimate;
- passing capacity gate;
- backup/rollback note;
- Marius approval only if the capacity gate blocks, health is unclear, public
  exposure is needed or existing guests are changed.

Project-specific note: not recommended for V1.

## Proxmox VM

Use only when the project needs strong isolation, different OS/kernel services,
risky dependencies, multi-service lab work, client-data separation or a clear
snapshot/rollback boundary.

Required before action:

- read-only Proxmox health check;
- CPU/RAM/disk estimate;
- network exposure review;
- passing capacity gate;
- backup/snapshot/rollback plan;
- Marius approval only if the capacity gate blocks, health is unclear, public
  exposure is needed or existing guests are changed.

Project-specific note: not recommended for V1.