# Deployment with kamal

**URL:** https://meta.discourse.org/t/deployment-with-kamal/410153
**Category:** Self-hosting
**Created:** [August 16, 2026, 2:41pm UTC](https://meta.discourse.org/t/deployment-with-kamal/410153 "2026-08-16T14:41:20Z")
**Posts on this page:** 1
**Showing post:** 1

<div class="post-metadata">

### Author: ![sigmike](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sigmike/32/117797_2.png) [@sigmike](https://meta.discourse.org/u/sigmike)
#### Post date: [August 16, 2026, 2:41pm UTC](https://meta.discourse.org/t/deployment-with-kamal/410153/1 "2026-08-16T14:41:20Z")

</div>

Has anyone deployed Discourse with [Kamal](https://kamal-deploy.org/)?

I guess it could work either by using the [standalone template](https://github.com/discourse/discourse_docker#single-container-vs-multiple-containers) or by writing a deploy.yml with all dependency containers as accessories.

The doc says the standalone template has the disadvantage of longer downtimes when upgrading, but that would not be the case with kamal thanks to its zero-downtime deploys (it keeps the old container and only switches the reverse proxy to the new one when it responds with an HTTP 200).

---

_[View the full topic](https://meta.discourse.org/t/deployment-with-kamal/410153)._