# How are you hosting Discourse?

**URL:** <https://meta.discourse.org/t/how-are-you-hosting-discourse/30218>\
**Category:** Self-hosting\
**Tags:** hosting\
**Created:** [June 19, 2015, 6:55pm UTC](https://meta.discourse.org/t/how-are-you-hosting-discourse/30218 "2015-06-19T18:55:02Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![pl3bs](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pl3bs/32/37266_2.png) [@pl3bs](https://meta.discourse.org/u/pl3bs)\
**Post date:** [June 19, 2015, 8:38pm UTC](https://meta.discourse.org/t/how-are-you-hosting-discourse/30218/4 "2015-06-19T20:38:43Z")

</div>

No worries. To address the dedicated bit, I’d assume funds would be the main limiting factor, and then if you’re referring to self-hosting, the potential traffic/bandwidth issue. There’s fairly cheap dedi’s from OVH’s kimsufi. I had a KS-3 for a few months that worked out okay. You’d also be dealing with the potential for major downtime. I’ve heard horror stories for kimsufi failures, like a full week before getting back up.

To have a dedicated with everything you need and get from a cloud, like daily backup, and host redundancy… that would be a bit expensive. It just depends on what level you’d like to invest in, I guess. I’ve seen some setups where people have many hosts on various amazon packages and attempt to reach full fault tolerance (only to find some sort of failure come about in the end), and am certain it’s pricey.

Personally I’ve got 8 dual socket hexacore xeons hosting Discourse in Docker containers, two which are setup for primary and secondary backup.

---

_[View the full topic](https://meta.discourse.org/t/how-are-you-hosting-discourse/30218)._
