<?xml version="1.0" encoding="UTF-8"?><oembed><type>video</type><version>1.0</version><html>&lt;iframe src=&quot;https://www.loom.com/embed/56f4f72073bb4d3fa858098a35a2a4b3&quot; frameborder=&quot;0&quot; width=&quot;1280&quot; height=&quot;960&quot; webkitallowfullscreen mozallowfullscreen allowfullscreen&gt;&lt;/iframe&gt;</html><height>960</height><width>1280</width><provider_name>Loom</provider_name><provider_url>https://www.loom.com</provider_url><thumbnail_height>960</thumbnail_height><thumbnail_width>1280</thumbnail_width><thumbnail_url>https://cdn.loom.com/sessions/thumbnails/56f4f72073bb4d3fa858098a35a2a4b3-c552a2b4bd2c7665.gif</thumbnail_url><duration>300.635</duration><title>Sovereign Stack One Command Client Deployments</title><description>This Loom demonstrates a one-command “Sovereign Stack” for automated client onboarding and deployment. It replaces manual setup steps like provisioning a server, wiring DNS, generating SSL certificates, creating secrets, installing services, and hardening the box by using a single YAML configuration that defines server specs, domain, and self-hosted software such as monitoring, n8n, BaseRow, and Docuseal. The process includes a pre-flight check and a dry run, then a live deployment that takes about 15 minutes, provisioning a new Hetzner server, setting Cloudflare DNS, issuing Let’s Encrypt certificates via traffic, hardening the server, and storing per-environment secrets in Bitwarden. The author emphasizes that the same configuration produces the same repeatable and auditable stack every time.</description></oembed>