Must have
Hard prerequisites
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.
- A supported database and persistent storage.
Application hosting
Hosting Wiki.js
A self-hosted wiki for team documentation and knowledge bases. Wiki.js runs on Node.js and stores content in a database; PostgreSQL is the recommended choice for a new installation.
- Min vCPU
- 1
- Min memory
- Depends on workload
- Min storage
- Depends on workload
Recommended
Documented guidance
No further general recommendations are published for this version.
Published starting requirements
Official Linux guidance specifies at least 1 GB RAM and recommends at least 1 GB dedicated storage. Two or more CPU cores are recommended for background workers. GB values are retained as published rather than treated as exact GiB values.
We only compare what providers publish. A RAM figure alone can't confirm compatibility or production capacity.
Deploy with
Supported paths
The host must provide
Runtime
- Node.js
- 22.0+ or 24.0+ for the documented 2.x releases
- PostgreSQL
- Recommended database; select a maintained release
Storage
Persistent data
Allow room for the database and uploaded assets. Back up both content and configuration. Other database engines supported in 2.x are not supported in the planned 3.x release.
Step by step
Plan a Wiki.js installation
-
Prepare the database
Create a dedicated database and service account; enable pg_trgm when using PostgreSQL search.
Official instructions -
Select the image
Use ghcr.io/requarks/wiki with an explicit major or minor version tag instead of latest. Configure the documented database environment variables.
Official instructions
Security
Before you go public
- Keep database credentials outside the public document root.
- Control wiki access and serve the dedicated hostname over HTTPS.
Cost
Beyond the server price
- Account for database storage and backups alongside application hosting.
Matching plans
Plans with published evidence
DigitalOcean
CPU-Optimized Regular Droplet · 2 vCPU / 4 GiB
2vCPU
4 GiBRAM
25 GiBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
DigitalOcean
General Purpose Droplet · 2 Dedicated vCPU / 8 GB
2vCPU
8 GBRAM
25 GBStorage
4 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Hetzner Cloud
Hetzner Cloud CCX53 (Germany and Finland)
32vCPU
128 GBRAM
600 GBStorage
50 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Hetzner Cloud
Hetzner Cloud CCX63 (Germany and Finland)
48vCPU
192 GBRAM
960 GBStorage
60 TBTransfer
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Compatibility unclear from published plan data
Meeting documented runtime prerequisites does not prove production capacity. Traffic, workloads, software configuration, and shared host limits are not measured here.
- A dedicated domain or subdomain; deployment below a URL subfolder is unsupported.This prerequisite has no comparable published plan field.
- Node.js 22.0+ or 24.0+ for a native installation; the container bundles Node.js.This prerequisite has no comparable published plan field.
- A supported database and persistent storage.This prerequisite has no comparable published plan field.
Want the full monthly bill? Use the hosting cost calculator. It keeps unknown charges visible.