# KUN Visual Novel Forum: A Monorepo for Community-Driven Galgame Cataloging > KUN Visual Novel Forum is a Nuxt 4 and Go Fiber monorepo that runs a full galgame community, from catalog editing to moderation. It is a serious architecture for niche communities, but its AGPL license and shared-service dependencies demand careful evaluation. **KunMoe/kun-galgame-forum** — The CUTEST visual novel / galgame forum! Built with Nuxt 4, Go Fiber and PostgreSQL. Kun Visual Novel forum, 6th generation - open-source, free, zero-barrier, the most advanced Galgame forum community! - Repository: https://github.com/KunMoe/kun-galgame-forum - Website: https://kungal.com - Stars: 2,163 · Forks: 79 - Language: Go - License: AGPL-3.0 - Published: 2026-08-22 · Updated: 2026-08-22 · Language: en - Canonical page: https://hysenlabs.com/projects/kunmoe-kun-galgame-forum ## What This Forum Actually Solves The repository is a pnpm workspace monorepo with two main packages: apps/api, a Go Fiber v3 BFF and REST API, and apps/web, a Nuxt 4 SSR frontend. The API owns forum data and interactions, enriches responses, and runs scheduled synchronization jobs. The frontend handles Vue pages, components, Pinia state, validation, SEO, and browser interaction, with Nitro serving feeds, sitemap data, and legacy redirects. The data flow starts with the user on the Nuxt frontend, which makes requests to the Go API. The API then talks to PostgreSQL for forum-specific data like topics, replies, and messages. But it also calls out to shared services in the kun-galgame-infra hub for identity, authentication, image storage, and community threads. For example, user authentication uses an opaque kungal_session cookie backed by Redis, and OAuth tokens never live in browser storage. Visual novel metadata is sourced from the Catalog registry, and newly submitted works adopt the registry-issued work ID as their forum gid. This means the forum is not self-contained; it depends on a larger ecosystem. ## The Monorepo Layout and Shared Services Dependency The architecture is explicitly a downstream application of kun-galgame-infra, which is the identity and shared-service hub. The README provides a table that lists which capabilities are owned by the forum and which are single-sourced in infra. The forum owns topics, replies, messages, resources, ratings, quizzes, collections, toolsets, local counters, and its PostgreSQL schema. Shared capabilities like identity, browser authentication, Moemoepoint balance, visual novel metadata, avatars, comment threads, reports, and toolset archives all live in external services. This is a strong separation of concerns, but it means you cannot run the forum alone. You must also deploy or connect to the infra services, including OAuth, Redis, image_service, Community, Trust, and Artifact. The README mentions that the retired Galgame Wiki family is not a contract for new work, but some compatibility reads and notification surfaces remain temporarily while the catalog cutover finishes. This is a transitional state that adds complexity. For a potential adopter, this dependency graph is the first thing to map out. The documentation does not provide a full deployment guide in the cleaned README, so you would need to inspect the repo and the infra project for setup details. ## Getting It Running: Commands and Configuration The README does not include explicit setup commands, but it states that the repository is a pnpm workspace monorepo. That implies you start by installing dependencies with pnpm install at the root. The tech stack table lists Go 1.26 and Fiber v3 for the API, and Nuxt 4 with Nitro for the frontend. You would likely need to run the API and web apps separately, using commands like pnpm --filter apps/api run dev and pnpm --filter apps/web run dev, but those exact commands are not in the material. The configuration keys are not documented in the cleaned README either. You would need to set up PostgreSQL, Redis, and Meilisearch, as those are named in the features and tech stack. The README mentions that Moemoepoint's authoritative balance and ledger are owned by OAuth, so you need that service running. The kungal_session cookie is backed by Redis, so Redis is mandatory. Without a setup guide, the barrier to entry is higher than a typical open-source forum. The documentation site at soft.moe/kun-visualnovel-docs/kun-forum.html is referenced, so that is the place to look for actual commands and environment variables. ## Where It Falls Short: Limitations and Wrong Use Cases The most obvious limitation is the tight coupling to the KUN ecosystem's shared services. If you want a standalone forum for a different community, you cannot just fork and run it. You must either deploy the entire infra stack or rewrite parts of the API to use your own auth, image storage, and metadata services. The README also indicates that the catalog cutover is not complete, with some compatibility reads and notification surfaces remaining. That means the codebase is in a transitional state, and you may encounter stale code paths. Another limitation is the AGPL-3.0 license. This is a strong copyleft license, which means if you modify the code and host it as a network service, you may be required to release your modifications under the same license. That could be a problem for commercial or closed-source projects. The project is also heavily tailored to galgame content, with features like visual novel ratings, tags, and release calendars. If your community is not about visual novels, much of the catalog and resource-sharing machinery would be unused overhead. The documentation is sparse in the README, so you are dependent on external docs that may be incomplete or outdated. ## Alternative Approaches: Comparing to a General Forum or Wiki A real alternative is to use a general-purpose forum like Discourse or Flarum, combined with a separate wiki engine like MediaWiki for cataloging. Discourse is a mature, self-contained forum that handles topics, replies, polls, and moderation out of the box. It uses Ruby on Rails and PostgreSQL, and it has a plugin ecosystem. The key difference is that Discourse does not have built-in support for visual novel metadata, resource sharing with provider tracking, or a contribution score like Moemoepoint. You would need to build those as custom plugins or separate applications. KUN Visual Novel Forum, on the other hand, integrates these features natively, but it forces you into the KUN ecosystem. Another alternative is to use a headless CMS like Strapi for the catalog and a separate forum package, but that would require significant integration work. The trade-off is clear: KUN gives you a complete, tailored solution but with high coupling; a general forum gives you flexibility but requires you to assemble the pieces yourself. The choice depends on whether you want to maintain a custom platform or compose existing tools. ## Maintenance and Upgrade Cost The README reveals that the project has used LLM-assisted development tools since version 5.1.0, including Codex and Claude Code. All code through version 5.0.70 was written entirely by hand. This is a notable maintenance signal. LLM-assisted code can introduce inconsistent patterns or hidden complexity, and it may be harder to review for security. The project is on its 6th generation, which suggests a long history, but the last push date is unknown and there are no recent releases listed. That makes it hard to assess how actively it is maintained. The monorepo structure with multiple packages and shared services means upgrades are not trivial. A change in the infra services could break the forum, and you must track those dependencies. The AGPL-3.0 license also has implications for maintenance: if you modify the code, you must keep it open under the same license. That is a legal constraint, not just a technical one. The documentation is partly in Japanese and Chinese, with an English README, so language barriers may add to maintenance overhead for non-English speakers. Before adopting, you should check the commit history and the status of the catalog cutover to gauge the project's stability. ## Conclusion Adopt KUN Visual Novel Forum if you need a complete, self-hostable forum and catalog system for a visual novel or similar niche community, and you are comfortable with AGPL-3.0 and the complexity of a pnpm monorepo. Do not adopt it if you want a simple blog or a standalone forum without external dependencies like OAuth and Redis. Before committing, verify the current state of the catalog cutover and the compatibility reads, and confirm that your deployment can support the full stack including Meilisearch and the shared services. This project is not a drop-in solution; it is a specific architecture for a specific ecosystem. ## FAQ ### What is kun-galgame-forum? An AGPL-3.0 forum for visual novel fans, built as a Go Fiber v3 API and a Nuxt 4 server-rendered frontend in a pnpm workspace monorepo, with PostgreSQL through GORM. It is a downstream application of the nextmoe-infra project, which owns identity and the shared services. ### Which database does kun-galgame-forum use? PostgreSQL through GORM, with explicit raw-SQL migrations. The Compose file deliberately does not define Postgres or Redis, because both are owned by the nextmoe-infra stack, which has to be running first since bringing it up is what creates the shared network. ### How do you run the checks in kun-galgame-forum? There is no single combined command. Lint and typecheck target only the web app, vet and the API test target only the API, and format is the only script that spans both. Production runs through PM2 with shell scripts for deploy, start, stop and restart. ### How does kun-galgame-forum disclose AI-assisted code? The readme states that development has used LLM-assisted tools, naming Codex and Claude Code, since version 5.1.0, that all code through version 5.0.70 was written by hand, and links the exact commit for the last fully hand-written revision so the boundary can be checked. ### What does kun-galgame-forum own, and what does it borrow? It owns topics, replies, messages, resources, ratings, quizzes, collections, toolsets, local counters and its own database schema. Identity, browser sessions, contribution balances, visual novel metadata, avatars and content images, comment threads, moderation and toolset archives all live in shared services. ### Can I run kun-galgame-forum on my own machine? The Compose file covers the API and web pair only and expects the shared infrastructure to be up first. The documented order is build, then run the migration job as a one-off container, then start api and web, and the services are given prefixed names to avoid a DNS collision with another repository that also calls its service api. ## Sources - [Official documentation](https://kungal.com) - [Official README](https://github.com/KunMoe/kun-galgame-forum#readme) - [Project repository](https://github.com/KunMoe/kun-galgame-forum) --- Hysen Labs editorial analysis, written from the project's own repository and release notes. Cite the canonical page: https://hysenlabs.com/projects/kunmoe-kun-galgame-forum