Learn how Apache Answer and Discourse differ in their key features, development activity, technology stack and community adoption, so you can decide which of these community building platforms is best for you.
Stars
Forks
Last commit
Repository age
License
Self-hosted
Auto-fetched .

Auto-fetched .

Discourse appears to have several advantages over Apache Answer, particularly in popularity and maturity. Consider your specific needs regarding popularity, activity, technology, maturity, licensing and features when making your decision.
Discourse significantly outpaces Apache Answer in community adoption with 46,873 stars compared to 15,477 stars on GitHub. This 3.0x difference suggests Discourse has a much larger and more active community. In terms of developer contributions, Discourse has 8,882 forks, indicating strong developer engagement.
Both projects show recent activity, with Apache Answer last updated 6 days ago and Discourse 5 hours ago.
Both tools share common technology foundations, being built with JavaScript, CSS, Typescript, SCSS. However, they differ in their additional technology choices: Apache Answer uses Bash, JSX, Golang while Discourse leverages Ruby.
Discourse has been in development longer, starting 13 years ago, compared to Apache Answer which began 4 years ago. This 9.9-year head start suggests Discourse may have more mature features and established processes.
The projects use different licenses: Apache Answer is licensed under Apache-2.0 while Discourse uses GPL-2.0. Consider the licensing requirements when choosing for your project.
Both tools serve similar use cases in Community Building Platforms. However, they also have distinct specializations: Apache Answer also focuses on Q&A Platforms while Discourse extends into Forum Software.
Both Apache Answer and Discourse offer self-hosting capabilities, giving you full control over your data and infrastructure.