Core

Stack Overflow is built with .NET Core (削除) uses a WISC stack (削除ここまで) (削除) via BizSpark (削除ここまで) (we graduated!):

• Host Google Kubernetes Engine
• Database SQL Server 2022
• Language C#

Software Development Tools

• IDE Visual Studio 2022, JetBrains Rider, VS Code
• Framework Microsoft .NET 8.0
• Web Framework ASP.NET Core 8.0 with MiniProfiler
• View Engine Razor
• Design Framework Stacks
• UI Framework Svelte
• Browser Framework jQuery 3.7.1
• Data Access Layer Entity Framework Core and Dapper
• Cache / Additional Data Redis via Memorystore, StackExchange.Redis, with serialization via protobuf-net
• Source Control Git using a GitHub Enterprise instance hosted by GitHub (previously self-hosted GitHub, Mercurial from 2010–2014, Subversion from 2008–2010)
• Compare Tool Beyond Compare 4

External Bits

Code used in Stack Overflow that is not included as part of the development tools:

• reCAPTCHA
• WMD - Now developed as open source in the project (削除) PageDown (削除ここまで) Stacks Editor
• Highlight.js (was Prettify)
• Google Analytics
• MarkDig
• Azure Event Hub
• Octopus Deploy
• LESS (source)
• MathJax
• Elasticsearch (source)

Miscellaneous

• WebSocket (for real time updates; custom C# implementation)
• Bandwidth used by Stack Exchange sites
• jQuery Isotope plugin (for the grid-style site list) ^_(Source)

Content

• License Creative Commons Attribution-Share Alike 4.0 for content contributed on or after 2018年05月02日 (UTC); Creative Commons Attribution-Share Alike 3.0 for content contributed between 2011年04月08日 and 2018年05月01日 (UTC); Creative Commons Attribution-Share Alike 2.5 for content contributed before 2011年04月08日 (UTC) (source)
• Standards OpenSearch, Atom
• Host: Google Cloud Platform
  • formerly hosted at QTS (technically in Jersey City, NJ), Internap and PEER 1 in NYC, and in an unknown data center Denver (also formerly hosted at FORTRUST).

Sources:

1. Stack Overflow's New York Data Center (Server Fault Blog)
2. Designing for Scalability of Management and Fault Tolerance (Server Fault Blog)
3. What Was Stack Overflow Built With?
4. Stack Overflow Server Glamour Shots
5. Technology and SEO profile for stackoverflow.com
6. Stack Overflow and DVCS
7. Stack Overflow Network Configuration
8. https://stackexchange.com/performance
9. Moving the public Stack Overflow sites to the cloud: Part 1

• 43
  Hmmm, the list seems incomplete. I don't see Unicornify in there...

  Lunatik

  – Lunatik

  2010年05月06日 07:10:39 +00:00

  Commented May 6, 2010 at 7:10
• 1
  Probably should include this one as well meta.stackexchange.com/questions/216324/…

  Templar

  – Templar

  2014年07月03日 18:00:02 +00:00

  Commented Jul 3, 2014 at 18:00
• 12
  I have to say I was surprised to see this level of technical detail made public. I'm not sure how common this is, but my gut tells me that security pedants wouldn't be overjoyed by it. That is, purely theoretically, a malicious party might be able to narrow the space of attack options based on the level of details here. Just my two cents.

  sammy34

  – sammy34

  2015年05月30日 14:48:59 +00:00

  Commented May 30, 2015 at 14:48
• 1
  Is api.stackexchange.com included here?

  Some Helpful Commenter

  – Some Helpful Commenter

  2016年02月04日 22:00:12 +00:00

  Commented Feb 4, 2016 at 22:00
• 3
  This answer needs two updates: 1. We're switching to CommonMark, but they still use MarkdownSharp and PageDown to some extent for special features; don’t know how much into detail this post should go. 2. An Update On Creative Commons Licensing; they don’t use CC BY-SA 4.0 for all the content. They use 2.5, 3.0, and 4.0.

  Sebastian Simon

  – Sebastian Simon

  2020年06月25日 02:02:21 +00:00

  Commented Jun 25, 2020 at 2:02

• support
• faq
• technology