Storyden

Longtime forum enthusiast Barnaby Keene created Storyden to rescue community discussions from the twin traps of decaying bulletin boards and closed chat networks. Built with a Go backend and a Next.js frontend, the platform pairs threaded forums with a structured wiki so knowledge does not vanish in ephemeral streams. That origin gives teams a lean, self-hosted community hub that eliminates legacy maintenance overhead while preserving data ownership.

Why Storyden instead of Circle

Circle organizes around paid memberships, private community spaces, and hosted SaaS infrastructure. That model serves creator courses, but creates friction for agencies and technical teams requiring direct control over data and hosting topology. Circle confines conversations to its cloud, gates custom branding behind expensive plans, and bills per member. Storyden replaces that walled garden with software running on your own infrastructure, bundling threaded forums, a markdown wiki, and curated collections with zero recurring subscription fees.

Operationally, Storyden integrates directly into developer workflows. The Go backend exposes an OpenAPI specification and embeds a Model Context Protocol (MCP) server, allowing AI agents and scripts to query threads and documentation without scraping. It also functions as an OAuth 2.0 and OpenID Connect provider, letting members authenticate into internal applications using forum credentials. You trade Circle's video streaming and native checkout for an open architecture giving ops leads control over data, plugins, and hosting costs.

What it does well

• Unified forum and knowledgebase: Threads link directly to Library wiki pages and collections, preventing duplicate questions and keeping documentation alongside active discussions.
• Low-footprint deployment: Runs as a single container backed by embedded SQLite for small teams or PostgreSQL for high-traffic sites, eliminating mandatory Redis or Elasticsearch clusters.
• Native MCP support: Includes a built-in Model Context Protocol server that allows AI agents to query discussions and documentation via standard interfaces.
• Embedded identity provider: Functions as an OAuth 2.0 authorization server with PKCE and device flows, allowing forum accounts to authenticate internal tools.
• Discord-style permissions: Features granular role management with custom colors and permissions that regulate access across categories and library trees.