# Meta is moving to the Cloud :cloud\_with\_lightning:

**URL:** https://meta.discourse.org/t/meta-is-moving-to-the-cloud/72819
**Category:** Self-hosting
**Tags:** hosting
**Created:** [26. Oktober 2017 um 03:49 UTC](https://meta.discourse.org/t/meta-is-moving-to-the-cloud/72819 "2017-10-26T03:49:38Z")
**Posts on this page:** 1
**Showing post:** 41

<div class="post-metadata">

### Author: ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [27. Januar 2019 um 19:05 UTC](https://meta.discourse.org/t/meta-is-moving-to-the-cloud/72819/41 "2019-01-27T19:05:19Z")

</div>

Meta is hosted in the same setup we use for our Enterprise customers, so it certainly doesn’t fit the free tier. See this previous post:

> [@Meta is moving to the Cloud cloud\_with\_lightning](https://meta.discourse.org/t/meta-is-moving-to-the-cloud-cloud-with-lightning/72819/34):
>
> Not really, I think you nailed it. Note we do have 1 year reserved instances for a few of our EC2 VMs so the cost is probably closer to the $1300 a month once amortized. We can probably reduce cost a bit by moving Redis to a EC2 instance and rolling our own vs using ElasticCache which is a bit of a premium. Overall, we have been very happy with our AWS experience, but it is certainly a bit pricey compared to our bare metal setup. We also squeeze a tiny bit more performance out of our bare met…

Only change so far is moving away from Elasticache since the service had some rough edges. We run Redis ourselves.

---

_[View the full topic](https://meta.discourse.org/t/meta-is-moving-to-the-cloud/72819)._