Scoold

Open-source Q&A for teams, honestly reviewed. No marketing fluff — just what you actually get when you deploy it.

TL;DR

• What it is: Apache-licensed Q&A platform modeled on Stack Overflow, built for internal team knowledge sharing. Supports questions, answers, voting, badges, spaces, and full-text search [README].
• Who it’s for: Engineering teams, support orgs, and ops teams who want an internal knowledge base that works like Stack Overflow — not a wiki, not a chat channel, not Confluence [1][README].
• Cost savings: Stack Overflow for Teams charges per seat every month. Scoold Pro charges €499 once, per instance, forever — no recurring fee, no per-user pricing [website].
• Key strength: Flat perpetual licensing in a market full of monthly per-seat SaaS. Genuinely enterprise-capable: LDAP, SAML, SCIM, OAuth, SSO, Teams/Slack/Mattermost integrations — most of these gated behind Pro but the price makes it defensible [README][4].
• Key weakness: Two-service architecture (Scoold + Para backend) makes deployment meaningfully more complex than single-container tools. Requires Java 21+ and at least 3 GB RAM for a self-hosted setup [1]. The free tier has a hard cap of one admin and ten spaces.

---

What is Scoold

Scoold is a Q&A and knowledge-sharing platform for teams, modeled directly on Stack Overflow. You ask questions, get answers, vote on quality, earn reputation and badges. Each edit is versioned. Similar questions are surfaced before you post. The GitHub README describes it plainly as “The Stack Overflow clone for your team (self-hosted or hosted)” [README].

The project has been around since 2008, open-sourced in 2012, and substantially refactored in 2017. It’s backed by Erudika, a bootstrapped (not VC-funded) company. As of this review it sits at 913 GitHub stars — a modest number for a self-hosted tool, but the project is actively maintained and commercially funded through Scoold Pro sales [README].

The architecture is unusual among self-hosted tools: Scoold itself is a Java Spring Boot application that handles the web layer, while a separate service called Para handles all backend operations — data storage, indexing, search. Para is database-agnostic and can connect to DynamoDB, MongoDB, PostgreSQL, Cassandra, or Elasticsearch depending on your setup. This separation is what makes Scoold “cloud-optimized” in the vendor’s words, but it also means you’re deploying two services, not one [README][1].

There are three versions: Scoold (free, Apache 2.0), Scoold Pro (€499 per instance, EULA), and Scoold Pro + Source Code (€1,999, EULA). A managed cloud option, Scoold Cloud, is also available for teams who don’t want to operate infrastructure [website].

---

Why people choose it

Available third-party review coverage for Scoold is sparse — the product lives in a smaller niche than automation tools or monitoring platforms. What we can synthesize comes from the vendor’s own documentation and integration pages, which are honest about the trade-offs, and from the feature comparison table on the pricing page.

The flat license fee is the main differentiator. The README explicitly calls out: “Are you still paying per seat in 2026? Scoold Pro is the knowledge sharing platform to migrate to!” [README]. This isn’t marketing fluff in context — Stack Overflow for Teams, Guru, Tettra, and Confluence all charge monthly per-seat fees. At 20 people, that compounds quickly. Scoold Pro at €499 per instance with unlimited users is a structurally different pricing model, and for small-to-medium teams it can represent significant annual savings after year one.

It fills a gap that wikis and chat don’t. Teams default to Notion, Confluence, or Slack for knowledge management. None of these have the Stack Overflow interaction model: questions with typed answers, voting to surface quality, accepted answer marking, reputation signals, and full-text search across the question corpus. If your team repeatedly loses answers in Slack threads or buries knowledge in Notion pages nobody finds, the Q&A format is a different tool for a different problem.

The Microsoft Teams and Slack integrations (Pro-only) address the friction of context-switching. Users can ask questions directly from Teams: @Scoold ask How do I...? and the question gets routed to Scoold for permanent indexing. Answers can be submitted from Teams too, and the channel gets real-time notifications [4]. This matters for teams who live in Teams or Slack — forcing everyone to open a separate browser tab for a Q&A platform is where adoption dies.

LDAP is free. Most self-hosted tools gate LDAP/Active Directory authentication behind a paid tier. Scoold includes LDAP and Active Directory support in the Apache-licensed free version, which makes it viable for intranet deployments behind corporate firewalls without any payment [README].

---

Features

Based on the README and website feature comparison [README][website]:

Core Q&A engine (free):

• Questions, answers, comments, voting, accepted answers
• Reputation system with built-in badges
• Custom badges with user-defined text, icon, and color
• Revision history on every edit
• Similar question suggestions before posting (duplicate prevention)
• Full-text search via Para + Elasticsearch
• Spaces (Teams) — up to 10 in free tier; isolated groups of users and questions
• Geolocation tagging and “near me” filtering on questions
• Email notifications for question threads and answer replies
• GFM Markdown with syntax highlighting (basic), tables, task lists, emoji support
• Import from Stack Overflow for Teams
• RESTful API with OpenAPI 3.0 spec
• Webhooks with signature signing
• Zapier integration
• Social login (Google, GitHub, LinkedIn, Microsoft, Slack, Facebook, Amazon, Twitter)
• 2FA with TOTP apps (Google Authenticator, etc.)
• LDAP and Active Directory authentication
• OAuth 2.0 support
• mTLS (mutual TLS) support
• i18n with RTL language support
• GDPR/CCPA cookie consent
• Backup and restore
• Akismet anti-spam
• SEO-optimized (server-rendered HTML) [website]
• Docker and Docker Compose deployment
• Responsive layout

Pro-only (€499 one-time):

• Slack, Mattermost, and Microsoft Teams integrations [4]
• SAML 2.0 authentication
• Custom authentication
• SCIM 2.0 for automatic user provisioning
• Mentions with notifications
• File uploads (local storage, AWS S3, Azure Blob)
• Account suspension / permanent bans
• Anonymous posts
• Unlimited spaces (vs. 10 in free)
• Multiple admins (vs. 1 in free)
• Multiple whitelisted identity domains (vs. 1 in free)
• Sticky and favorite posts
• Advanced syntax highlighting
• Email digest of recent questions
• Security notifications
• Wiki-style answers
• MathJax support [website][README]

The free tier is functional for a small team. The hard limits that bite first are the single-admin restriction and the ten-space cap — once you outgrow those, you’re looking at Pro.

---

Pricing: SaaS vs self-hosted math

Scoold tiers:

• Free (Apache 2.0): no cost, one admin, 10 spaces, no Teams/Slack integration [website]
• Scoold Pro: €499 per instance, one-time perpetual license [website]
• Scoold Pro + Source Code: €1,999 per instance, one-time perpetual license [website]
• Scoold Cloud: managed hosting, pricing not publicly listed — contact sales [website]

The key number is per instance, not per user. A single Scoold Pro instance handles an unlimited number of users for €499 paid once.

Stack Overflow for Teams comparison (from public pricing):

• Basic tier: $6.50/user/month
• Business tier: $13.25/user/month

For a 25-person team on the Basic tier: $6.50 × 25 = $162.50/month, or $1,950/year. After year one, Scoold Pro at €499 (roughly $550 at current exchange rates) has paid for itself and the recurring bill is zero.

For a 50-person team: $6.50 × 50 = $325/month, $3,900/year. Scoold Pro is still €499 flat.

Self-hosted operating cost:

• Scoold + Para require a minimum of 3 GB RAM on a single host [1]
• A Hetzner CX21 (3 GB RAM, 2 vCPU) runs about €5.77/month
• Total year-one cost for a 25-person team: €499 (license) + ~€70 (VPS) = ~€569, plus setup time
• Year two onward: ~€70/year

Concrete savings at 25 users: Stack Overflow for Teams ≈ $1,950/year. Scoold Pro self-hosted year two ≈ €70/year. That’s roughly $1,800/year saved — every year after the first.

The math only works if you can deploy and maintain it. If you can’t, Scoold Cloud removes that cost but adds back a recurring fee at undisclosed pricing.

---

Deployment reality check

Scoold is not a single Docker container. It’s two services: the Scoold application and the Para backend. This is the first thing to understand before you attempt deployment [1].

Option 1: Docker Compose (recommended for most). A single docker compose command against the project’s compose file brings up both services. The documentation calls this “Easy” difficulty [1]. On a fresh VPS with Docker installed, a working instance is plausible in 30–60 minutes for a technical user.

Option 2: JAR + Para Cloud (simpler backend). You run Scoold as a JAR locally and point it to Para Cloud (Erudika’s managed Para backend, separate service with its own signup). This removes the need to operate Para yourself. The documentation rates this “Easy” [1]. Downside: you’re now dependent on an external managed service for your data layer, which somewhat defeats the point of self-hosting.

Option 3: Full self-hosted JAR (moderate complexity). Both Scoold and Para run as JAR executables. Para manages its own configuration and database connection. You configure Scoold to point at your Para instance. The documentation rates this “Moderate” [1].

Option 4: Native executable (advanced, requires GraalVM + Maven). Build a native binary from source. Not recommended unless you have a specific reason [1].

What you actually need for Option 1:

• Linux VPS, minimum 3 GB RAM (Scoold + Para together) [1]
• Docker and docker-compose
• A domain name and reverse proxy (Caddy or nginx) for HTTPS
• SMTP provider for transactional email (email notifications, user invites) [2]
• Optional: Elasticsearch for production-grade search (Para can run without it, but search quality degrades)

Configuration: Scoold is configured via scoold-application.conf, a HOCON file. Environment variable overrides are supported. The basic config is straightforward — app name, port, Para endpoint URL, access key, admin email [2]. SMTP setup is recommended early so email notifications work [2].

What can go wrong:

• The two-service architecture means two points of failure, two sets of logs to watch, two things to restart when something breaks.
• Para’s database connectivity needs to be right before Scoold will start correctly — Scoold retries the Para connection 10 times by default with 10-second intervals [2]. If Para isn’t ready, Scoold silently fails to persist settings.
• Java 21+ is required. If your server runs an older Java version, you’ll need to upgrade or install it in parallel [1].
• Teams/Slack integration requires Pro license and additional app registration in the respective developer portals — it’s not plug-and-play [4].

Realistic time estimates: a technical user who has deployed Java apps before can have Scoold running in under an hour. Someone new to Linux servers or Java deployments should budget half a day, including debugging.

---

Pros and cons

Pros

• Flat perpetual licensing. €499 per instance, unlimited users, forever. The math against per-seat SaaS is decisive once your team has more than 10–15 people [website].
• LDAP is free. Active Directory / LDAP authentication is included in the Apache-licensed tier, not gated behind Pro. Uncommon in this category [README].
• Full Q&A interaction model. Reputation, voting, accepted answers, revision history — this is the Stack Overflow model, which wikis and Notion pages can’t replicate [README].
• RESTful API with OpenAPI spec. Programmatic access is documented and available in the free tier [README].
• Import from Stack Overflow for Teams. If you’re migrating off the incumbent, there’s a data path [README][website].
• GDPR-aware by default. Cookie consent baked in. Server-rendered HTML means no data is sent to analytics CDNs by default [website].
• Webhook + Zapier integration. Automatable without Pro [README].
• Bootstrapped company. Erudika is independently funded — no VC pressure to pivot the pricing model or sell to an acquirer. The README says so explicitly [README].

Cons

• Two-service deployment. Scoold requires Para to function. This adds setup complexity, operational surface area, and a dependency on a less well-known secondary project [1].
• Java 21+ requirement. Java runtime isn’t installed by default on most VPS images. It’s not a dealbreaker, but it’s an extra step compared to a Go binary or a Node Docker image [1].
• 913 GitHub stars. This is a small community for a tool asking you to bet your team’s knowledge infrastructure on it. Compare to 100K+ for n8n or 21K for Activepieces. Fewer community-contributed plugins, less StackOverflow help when something breaks.
• Single admin in free tier. A hard limit that makes multi-admin governance impossible without paying [website]. For a team of any meaningful size, this is a real constraint.
• Ten spaces in free tier. If you need more than ten isolated groups, you’re paying for Pro [website].
• Teams/Slack integrations are Pro-only. If Teams or Slack integration is your primary reason for considering Scoold, the free version won’t help you [4][README].
• No public third-party reviews. The tool doesn’t have a Trustpilot presence, G2 profile, or meaningful Reddit coverage that this review could synthesize. You’re largely trusting the vendor’s own documentation and the feature table — both of which are honest about the split between free and Pro features, which is something.
• Para is an additional moving part. Para has its own release cycle, its own configuration, and its own potential failure modes. Running two services is always more operational work than running one.

---

Who should use this / who shouldn’t

Use Scoold if:

• Your team is losing answers in Slack threads or burying knowledge in Notion pages that nobody searches.
• You have 20+ users and the math on per-seat SaaS alternatives is starting to hurt.
• You’re comfortable deploying Java apps or have someone who is.
• Your company uses Active Directory/LDAP and you need SSO without paying extra for it.
• You want server-rendered, privacy-respecting infrastructure that doesn’t phone home to analytics providers.

Use Scoold Pro specifically if:

• You need Teams or Slack integration to drive adoption — that’s the most common adoption blocker for any internal tool.
• You need multiple admins or more than ten spaces.
• You need SAML or SCIM for enterprise SSO provisioning.
• You need file uploads attached to answers.

Skip it (stick with Stack Overflow for Teams) if:

• Your company has a procurement relationship with Stack Overflow that makes the per-seat fee a non-issue.
• You need world-class search quality with years of tuning and you’re unwilling to maintain Elasticsearch yourself.
• You need official enterprise SLAs, compliance certifications, and a vendor relationship with named contacts.

Skip it (try Discourse) if:

• You want a forum rather than strict Q&A — threaded discussions rather than question/answer/vote.
• You want a larger community, more plugins, and significantly more third-party documentation.

Skip it entirely if:

• Nobody on your team has deployed a Java application before and there’s no budget for managed hosting.
• Your team is under 10 people — the free tier of a competitor or a simple shared Notion database is probably enough.

---

Alternatives worth considering

• Stack Overflow for Teams — the incumbent, polished, per-seat pricing, fully managed. Use it if you can afford the per-seat fee and want zero operational work.
• Discourse — forum-style rather than Q&A, but significantly larger community, more plugins, better search, and a more battle-tested deployment path. Apache 2.0.
• Outline — wiki-style knowledge base, not Q&A. Better for documentation than questions. MIT-licensed, single Docker container.
• BookStack — wiki platform, simpler to deploy than Scoold. Not Q&A focused.
• Answer — newer open-source Q&A platform, Apache 2.0, more active GitHub (6,000+ stars), single-service Go binary. Fewer features than Scoold Pro but much simpler deployment.
• Tettra — SaaS knowledge base with Slack-first design. Per-seat pricing, no self-hosting option.

For a team escaping Stack Overflow for Teams bills and willing to self-host, the realistic shortlist is Scoold Pro vs Answer. Scoold wins on feature depth and enterprise auth options; Answer wins on deployment simplicity and community size.

---

Bottom line

Scoold is a niche but competent tool for a specific problem: internal Q&A that works like Stack Overflow. It’s not trying to be a wiki, a forum, or a chat product. For teams that have already felt the pain of knowledge disappearing into Slack threads or Notion pages that nobody maintains, the Q&A interaction model is a different category of tool.

The pricing model is the headline. €499 per instance, once, forever, unlimited users — in a market where every competitor charges per seat per month — is a structural advantage for teams of 20 or more. The trade-off is operational complexity: Java runtime, two services, and a backend (Para) that most people have never heard of. If your team has someone who can handle a Java deployment, Scoold Pro is a legitimately good deal. If you don’t, either budget for a deployment service or evaluate the managed Scoold Cloud option.

The tool’s main risk isn’t quality — it’s obscurity. With 913 GitHub stars, a small community, and limited independent review coverage, you’re making a moderate infrastructure bet on a vendor that, to their credit, has been around since 2008 and is transparently bootstrapped. That’s not nothing, but it’s worth weighing against options with larger communities and simpler deployment paths.

---

Sources

1. Installation | Scoold Documentation — scoold.com. https://scoold.com/documentation/getting-started/installation/
2. Basic Configuration | Scoold Documentation — scoold.com. https://scoold.com/documentation/getting-started/configuration/
3. Scoold + Microsoft Teams Integration — scoold.com. https://scoold.com/integration-with/microsoft-teams/

Primary sources:

• GitHub repository and README: https://github.com/erudika/scoold (913 stars, Apache-2.0 license)
• Official website and feature comparison: https://scoold.com
• Pricing page: https://scoold.com/pricing/