Wiki.js

What you can use it for

• Maintain internal documentation, runbooks and onboarding guides for a team.
• Publish a knowledge base edited in Markdown or a visual editor.

What this template creates

Configuration to review

This template has no additional declared inputs. Review the generated variables, endpoints and resource settings in the deployment form.

How to deploy

1. Select Configure deployment and sign in or create an account.
2. Choose a new or existing project and select an available region.
3. Review services, required inputs, storage and compatibility warnings. Submit the deployment only when the configuration is ready.
4. Inspect deployment logs, complete the application's setup and test its endpoints before production use.

Operating this application

• Open the generated domain right after deployment and finish the setup wizard, which creates the administrator account and sets the site URL; until then, anyone who reaches the page can complete it.
• Back up the PostgreSQL database, for example with pg_dump, and test a restore, because the Wiki.js service has no volume and relies on the database for pages, uploads and settings.
• The wiki:2 tag can move to a newer 2.x release, while upgrading PostgreSQL beyond version 16 needs a dump and restore rather than a tag change.

Hosting costs

CPU, memory, storage and network usage contribute to your bill. The selected region affects resource prices. A multi-service template incurs usage for each service; external APIs and software licenses are separate.

Source and validation

This deployment configuration comes from Coolify's Apache-2.0 licensed open template collection and is adapted through Polyer's compose importer.

Static compatibility analysis is not a live application verification. Test your chosen configuration and recovery workflow before using it for production.

Editorial content reviewed: 2026-10-10

Upstream documentation ↗Template source and license ↗