BreezeWiki Hosting

How BreezeWiki works

BreezeWiki accepts a Fandom wiki and page path, requests the content through MediaWiki and Fandom endpoints, transforms the returned HTML, and displays a simplified reader page. Links are rewritten so navigation stays within the alternative frontend, images can be made visible without relying on the original JavaScript, and wide tables are adapted for practical reading.

Readers can replace the Fandom hostname in a familiar URL or use a redirection tool. The instance is still a proxying frontend rather than the source wiki. If Fandom changes an endpoint, blocks a request, alters a page, or removes content, the BreezeWiki result can fail or become incomplete until the project adapts.

Key BreezeWiki features

The project removes advertising, autoplay video, suggested material, and other surrounding clutter from supported wiki pages. A lightweight presentation reduces data use and improves readability, while transformed links and images preserve ordinary browsing across a wiki. The service can also point readers toward independent community wikis when suitable information is available.

BreezeWiki does not provide editing, contributor accounts, discussion tools, moderation, or ownership of the underlying articles. Templates, interactive elements, captchas, unusual media, or newly changed Fandom features may not render exactly as they do on the source site.

Who uses BreezeWiki

Readers can open game, entertainment, and hobby references through a cleaner interface, communities can publish an alternative link pattern, and administrators can provide an internal preferred reader. It is especially useful where users need article content but not the original platform’s surrounding features.

The frontend is not a replacement for an independent community wiki, an editorial archive, or a source of permission to copy article content. Contributors must use the appropriate source wiki or independent project when they need to edit or govern information.

Self-hosting BreezeWiki: requirements and cost

Resource demand depends on visitors, page size, images, tables, upstream response time, cache behaviour, transformed HTML, and concurrent requests. BreezeWiki’s catalogue row contains no PostgreSQL or MariaDB service. The mapping treats it as storage-driven, so 50 GB on Plan 3 is a realistic starting point for growing cache or retained assets, while 100 GB on Plan 4 better suits a larger public reader.

AvaHost maps BreezeWiki to Plan 1 at €2. The package includes one-click provisioning, a custom HTTPS hostname, automatic application updates, and scheduled backups. The plan does not include Fandom accounts, editing, article ownership, independent-wiki hosting, or assurance that every template and upstream route will remain compatible. Readers should verify consequential information with the responsible wiki community.