Open Support Ticket
24/7 customer support
Open Support Ticket Chat with our AVAHOST expert
English Flag English
Login
info@ava-host.com
Sign Up Login

Wiki.js Hosting

Create a modern team wiki with powerful editing, search, permissions, and authentication.

Order now No setup fees
  • One click deploy
  • 1 GB RAM Memory needed
  • 15 GB Disk Space Needed
  • From 2 € Price

Official links

Wiki.js’s official links and original website

Related apps

See All

Tech

Docker image
ghcr.io/requarks/wiki:2
Default port
3000
Database
postgres

How Wiki.js works

Wiki.js stores pages and user data in PostgreSQL, then presents the content through a browser-based wiki. Authors can choose editors suited to different workflows, including Markdown-oriented writing, while navigation and search help readers move through the knowledge base. Administrators control authentication, groups, permissions, rendering, search, and storage integrations from the administration area.

Pages can be organised into a hierarchy and exposed to different audiences through group permissions. Authentication modules connect the wiki to selected identity systems, and search or storage modules can extend the installation. Those integrations are configurable options rather than evidence that every external service is bundled with the hosting plan.

Key Wiki.js features

Fine-grained permissions define what groups may read, create, edit, manage, or delete across parts of the wiki. The guest group can be adjusted for public content, while private departments can receive narrower access. This makes one installation suitable for a mixture of public guides and protected internal documentation.

Multiple editor choices let authors work in a format appropriate to the team. Authentication, rendering, logging, search, and storage modules provide extension points for organisations with existing systems. Each integration should be configured and tested individually rather than listed as included by default.

Wiki.js vs Confluence

Wiki.js is a self-hosted wiki with configurable editors, permissions, authentication, and integrations. Confluence is a commercial collaboration and knowledge workspace within the Atlassian ecosystem, extending documentation into a broader team environment.

Confluence may suit organisations that prioritise Atlassian-hosted cloud plans, Jira integration, and a large Marketplace integration ecosystem. Wiki.js is more appropriate when the team wants to control its wiki installation and select its own authentication, storage, and integration approach.

Who uses Wiki.js

Engineering teams document systems and development practices, support groups maintain troubleshooting references, and internal departments publish policies or onboarding material. Communities can also create public documentation while keeping moderation and administration areas restricted.

It is less suited to teams seeking a visual project board, relational database, or complete office suite. Wiki.js centres on organised knowledge pages, so adjacent collaboration needs may require separate applications.

Self-hosting Wiki.js: requirements and cost

Resource use grows with page count, search activity, concurrent readers and editors, authentication traffic, and enabled integrations. PostgreSQL stores content, users, permissions, and configuration, so the complete stack needs more headroom than the application-only RAM figure. External search, identity, or storage services can add their own requirements if connected later.

The software itself is free to run, and AvaHost maps Wiki.js to Plan 2 at €5 for the application and PostgreSQL stack. One-click deployment provisions Wiki.js and PostgreSQL, but the database remains unmanaged by AvaHost. Wiki.js hosting includes automatic application updates, scheduled backups, custom-domain support, and automated HTTPS. A large public wiki or integration-heavy installation may require a larger plan.

F.A.Q

  • Wiki.js starts at €5 on Plan 2 for the wiki application and PostgreSQL stack. The accompanying PostgreSQL container is included without AvaHost management. Page volume, search traffic, concurrent users, attachments, authentication, and integrations can increase demand, while external identity, search, or storage services remain separate.

  • The one-click deployment provisions PostgreSQL and connects it to Wiki.js automatically. Pages, users, permissions, and configuration depend on that database. PostgreSQL is included but remains unmanaged by AvaHost, so administrators should consider database records and any persistent application data together when reviewing changes, integrations, or recovery requirements.

  • A custom documentation domain with automated HTTPS can give readers and editors a consistent branded address. Authentication callbacks and integrations may depend on that URL, so it should be final before connecting external services. Administrators should test sign-in, search, editing, permissions, and public access after the domain becomes active.

  • AvaHost applies Wiki.js updates automatically while persistent application data and PostgreSQL remain attached to the deployment. Scheduled backups are included. Administrators should still review major release notes and verify authentication, storage, search, and other integrations after an update is applied to the hosted wiki.