# Does my Local Install Communicate With Discourse Servers?

**URL:** <https://meta.discourse.org/t/does-my-local-install-communicate-with-discourse-servers/57630>\
**Category:** Product Support\
**Created:** [February 19, 2017, 11:48am UTC](https://meta.discourse.org/t/does-my-local-install-communicate-with-discourse-servers/57630 "2017-02-19T11:48:00Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![mpalmer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/mpalmer/32/45740_2.png) [@mpalmer](https://meta.discourse.org/u/mpalmer)\
**Post date:** [February 19, 2017, 6:49pm UTC](https://meta.discourse.org/t/does-my-local-install-communicate-with-discourse-servers/57630/5 "2017-02-19T18:49:35Z")

</div>

> [@regnatarajan](#):
>
> if the Discourse company died, would my forum still work?

Yes, Discourse-the-software can outlive Discourse-the-company. Nothing in the Discourse codebase _requires_ talking to Discourse servers, although as others have said, there are some things that are enabled by default that communicate externally. The version check failing won’t have any impact on operation; the thing that’ll cause the most visible problems is the avatars service, but even that’s just some missing avatar images (same as if gravatar went on the blink).

The most important resiliency feature of Discourse, though, is the fact that it is **open source**. Even if there were some sort of “phone home to get approval to run” code buried in Discourse somewhere, because you have the full source code _and_ the legal right to redistribute modified versions, you (or anyone) could rip that code out with impunity, _and_ give everyone else your fixed version.

---

_[View the full topic](https://meta.discourse.org/t/does-my-local-install-communicate-with-discourse-servers/57630)._
