Huijiwiki

Huijiwiki is a hosted wiki farm for communities that want to build a reference site around a defined subject or interest. It fits operators who value MediaWiki compatibility, structured data, and the freedom to customize their presentation without running servers. The public, application-based model is a poor match for confidential notes or projects requiring fine-grained access control.

Overview

Founded in 2015, Huijiwiki lets users apply to create topic-specific wikis. Hosting is handled through its Huijiwiki-developed DragonPit architecture, so a community can concentrate on content and administration rather than infrastructure. Applications are not guaranteed to be approved, an important consideration for anyone with a fixed launch schedule.

The service is built for shared knowledge: revision history, media uploads, role permissions, and API access support an active editorial community. It is not positioned as a private knowledge base. Huijiwiki explicitly does not provide private deployment or access-permission features and advises against using it for personal notes.

Key features

MediaWiki provides the familiar wiki foundation, while Semantic MediaWiki support and MongoDB-based structured-data deployment add ways to model, query, and maintain information beyond ordinary page text. That combination is particularly useful for catalogs, game references, and other projects where consistent fields and relationships matter.

Operators can write their own site styles and scripts to extend functionality. This gives technically capable communities meaningful control over a wiki’s appearance and behavior, but it also makes Huijiwiki a better fit for teams willing to maintain customizations than for groups seeking a completely managed, unchanging template.

Migration support covers Wikia, Gamepedia, and other MediaWiki-based sites, reducing the friction of moving an existing community. The MediaWiki API is supported alongside additional Huijiwiki interfaces, which helps integrations and custom tools. Sites using Huijiwiki’s WeChat public-platform integration can return lookup results when readers send a target term, a focused advantage for audiences that use WeChat. The maker says both reading and editing functions respond to mobile screens.

Security measures described by the maker include SSL, encrypted storage of privacy information, and data-center access controls. However, the version 2.0-and-later Doghead app does not provide registration, login, or authentication functions, so those controls do not turn Huijiwiki into a private collaboration system.

Pricing

Huijiwiki offers one published plan:

There are no paid tiers, seat charges, or stated quotas in the published plan. The trade-off is that access depends on the application process, and the service’s lack of private deployment and access permissions may matter more than price for organizations handling restricted material.

Platforms

Huijiwiki is delivered on the web. Responsive display supports reading and editing on mobile devices, but it is not presented as a separate native mobile application.

Who it's for

Choose Huijiwiki for a public-facing team or interest community building a structured reference wiki, especially when MediaWiki compatibility, migration from another MediaWiki host, or custom scripts are priorities. Semantic and MongoDB-backed data features suit projects that need organized, queryable information.

Look elsewhere for personal notes, confidential documentation, or a deployment that must remain inside your own infrastructure. The application requirement also makes it unsuitable when guaranteed acceptance and immediate provisioning are essential.

Pros and cons

Pros

• Structured-data options: Semantic MediaWiki and MongoDB support can turn a collection of pages into a more organized reference system.
• MediaWiki compatibility: Revision history, media uploads, role permissions, and API access provide core community-wiki tools.
• Migration assistance: Imports from Wikia, Gamepedia, and other MediaWiki sites can preserve an established project’s momentum.
• Customization: Site-owned styles and scripts allow a focused community to tailor its wiki.
• No software charge: The published hosting plan costs nothing.

Cons

• No private deployment or access permissions: Sensitive or personal material is a poor fit.
• Application uncertainty: A free site-creation request is not guaranteed approval.
• Customization requires upkeep: Teams without someone able to write and maintain styles or scripts may not benefit fully.
• Authentication limitation: The Doghead app version 2.0 and later does not provide registration, login, or authentication functions.

Alternatives

• Game Wiki Software is a useful directory when you want to compare a broader set of game-wiki products.
• Campfire is the better choice for a broader writing and worldbuilding workspace across Android, iOS, macOS, web, and Windows, with a free trial plan that limits access to writing and worldbuilding modules.
• AnvilWiki suits users who want an open-source MIT template deployable on their own setup, with free Cloudflare Pages bandwidth.
• Fandom is preferable when you want free wiki hosting with no limit to wiki size and broad Android, iOS, and web access.
• RPG Story Toolkit fits smaller RPG projects that prefer an open-source web or macOS tool with a free tier capped at three documents and three image uploads.
• Wikily is an option for free-forever wiki creation and free reading across iOS, web, and Windows.
• Kanka is better for campaign management, offering unlimited entries and campaigns on its free Kobold plan, with paid expansion available.
• LegendKeeper suits collaborative project work where a free Basic plan supports viewing and exporting all projects, with a paid annual Pro tier.
• Miraheze is another free web-hosting option, with 300-plus extensions and skins and open-source code.

Verdict

Huijiwiki is a strong choice for a public interest wiki that needs MediaWiki foundations, structured data, migration support, and room for custom code at no software cost. Choose it when community publishing matters more than control over deployment and permissions. Look elsewhere when privacy, guaranteed provisioning, or authenticated restricted access is a core requirement.