Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Possible Duplicate:
Stack Exchange for in-house use
Is the Stack Exchange engine available?
Creating an internal Stack Exchange for proprietary questions?

Stack Overflow is great. I see there are Stack Exchange sites that cover other domains.

Is there a Stack Overflow that a company could run internally?

share|improve this question

migrated from May 24 '10 at 19:31

This question came from our site for professional and enthusiast programmers.

marked as duplicate by kiamlaluno, Al E., Pops, Kevin Vermeer, Chris Frederick Oct 28 '11 at 4:37

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

Oops, looks like that blog post got renamed, user27414's answer does link to it, but with the url ending in "stack-exchange-2-0". Popular Demand's answer is fairly good, and a dupe of these answers, but it doesn't add anything that's not yet been said. Merge not required. – Kevin Vermeer Oct 27 '11 at 13:48
Actually, @KevinVermeer, I think my answer to Creating an internal Stack Exchange for proprietary questions? is even better. – Pops Oct 27 '11 at 15:04

As already mentioned, it's not available to run internally. On top of that I'd like to add that it's probably not suited for that situation anyway. Stack Overflow needs a fairly large active community to really work, and it's doubtful most places would be able to create such a community. Even if you have enough employees, driving adoption is not as easy as it sounds.

That said, if you want to try it anyway there are a number of clones you can look at:
Stack Exchange clones

Also, a clone is probably a better fit for your situation, because you can take the code and apply tweaks to do things like use your company's single sign on system or facilitate more discussion and social features. I could see code access + SSO as incredibly powerful for allowing things like only allowing certain users the ability to create tags, or view or create questions using certain tags, to allow additional sub communities within teams in your organization, while still only having one site to maintain.

share|improve this answer


Although Stack Exchange version 1 was available for local installation, version 2 is not.

From the Stack Exchange blog:

Q: I am interested in licensing the Stack Overflow source code.

As a part of our new focus on serving large, internet-sized communities, we are no longer offering the Stack Overflow software.

Q: I am interested in creating a private, internal Stack Exchange inside my organization.

We no longer offer such a product.

share|improve this answer

protected by ChrisF Oct 27 '11 at 10:36

Thank you for your interest in this question. Because it has attracted low-quality or spam answers that had to be removed, posting an answer now requires 10 reputation on this site (the association bonus does not count).

Would you like to answer one of these unanswered questions instead?