Wiki.js VPS plans currently listed

ProviderPlanvCPURAMDiskRegionsBillingPrice
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesFixed price$5.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAmsterdam, NetherlandsFixed price$5.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAmsterdam, NetherlandsFixed price$9.00/mo
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesFixed price$9.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAmsterdam, NetherlandsFixed price$16.00/mo
EnzonixShared Compute - General Compute48 GB160 GBAshburn, United StatesFixed price$16.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAmsterdam, NetherlandsFixed price$32.00/mo
EnzonixShared Compute - General Compute816 GB320 GBAshburn, United StatesFixed price$32.00/mo
EnzonixShared Compute - General Compute11 GB20 GBAshburn, United StatesHourly$0.007/hr
EnzonixShared Compute - General Compute12 GB40 GBAshburn, United StatesHourly$0.01/hr
EnzonixShared Compute - General Compute24 GB80 GBAshburn, United StatesHourly$0.015/hr

Wiki.js Instant App

Self-hosted Wiki.js VPS hosting

Wiki.js is an open-source documentation wiki with markdown editing, access control and a modern admin. Compare live VPS prices, CPU, RAM, disk and regions, launch Wiki.js on the plan you choose, and keep root access so your docs stay on your server.

Wiki.js

Instant App on marketplace VPS

Live marketplace offers

Compare Wiki.js VPS plans

Choose billing and size, compare providers side by side, pick a location, then launch.

Enzonix

Shared Compute - General Compute

$5.00/mo

1 vCPU · 1 GB · 20 GB

Choose location

Ashburn, United States

1 provider

Inside Wiki.js

Wiki.js is a self-hosted documentation wiki for team handbooks, runbooks and knowledge bases. Use it instead of paying for Notion or Confluence. Sign in as admin after boot, create pages, and invite teammates. No Instant App form fields are required at create time.

  • Wiki.js home after Instant App setup

    Admin ready after login

    Open Wiki.js and sign in with the prepared admin account instead of walking an empty setup wizard.

  • Wiki.js page editor with sample content

    Markdown documentation

    Write docs with a modern editor, page tree and search. Keep the handbook on hardware you control.

  • Wiki.js users list in administration

    Users and access control

    Manage groups and permissions from the admin UI. Grow from a personal wiki to a team knowledge base.

  • Wiki.js administration dashboard

    Administration dashboard

    Sites, groups, users and system health in one place. Keep operations on your VPS instead of a SaaS tenant.

Why use the NodeRings marketplace?

Compare live Wiki.js VPS plans from independent providers, then self-host a documentation wiki on the offer you pick. Use it instead of paying for Notion or Confluence.

  • Compare Wiki.js VPS offers in one place

    See live prices, regions and plan sizes before you buy. Shop wiki hosts across independent providers, including 2 GB boxes that fit Wiki.js with Postgres.

  • Self-host Wiki.js without a manual install

    Pick a plan and Wiki.js is prepared on that VPS for you, including the admin account. You still get root access.

  • Put the wiki in a region you choose

    Compatible offers list cities and countries. Keep latency low for your team or keep data in a place that matches policy.

  • Own the knowledge base

    Pages, assets and users live on your VPS volume. You control SSH, DNS and who can open the wiki.

Wiki.js hosting as a marketplace, not a single hoster

Most Wiki.js VPS pages sell one company's servers. NodeRings lists Compute Instance plans from independent providers so you can compare self-hosted wiki offers by price, size and region, then launch on the one that fits.

Wiki.js Instant App prepares Wiki.js on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.

Single-provider Wiki.js hosting

  • One company catalogue and renewal pricing
  • One set of regions and support paths
  • One vendor panel for that host only

NodeRings marketplace

  • Wiki.js VPS offers from independent providers
  • Compare resources, prices and regions side by side
  • Deploy Wiki.js on the plan you pick

How it works

Compare plans, pick a provider offer, and launch Wiki.js on that server.

  1. 01

    Compare Wiki.js VPS plans

    Browse live offers below. A 2 GB plan is a solid start for Wiki.js with Postgres. Sort by provider, size, price and region.

  2. 02

    Pick the offer that fits

    Choose the provider plan and region. There are no Instant App form fields to fill for Wiki.js.

  3. 03

    Deploy and sign in

    Confirm checkout and wait for the server. Then open the site URL and sign in with the admin email and password from your server notes. You keep root SSH.

On the VPS after Wiki.js deploys

NodeRings Instant App brings Wiki.js up with Docker Compose and prepares first-boot access for you. Use the sections below to reach the UI, find passwords, and operate the stack.

Open the web UI

  • In a browser, go to http://YOUR_SERVER_IP/ using the IPv4 from your order.
  • Sign in with wikijs_admin_email and wikijs_admin_pass from the credentials file.

Where the password is

Credentials are written on first boot to:

/root/.noderings_password

Read them over SSH:

cat /root/.noderings_password
  • Keys in that file include wikijs_admin_email, wikijs_admin_pass and site_url.
  • SSH in as root with the create-flow password or key, then run the command above.
  • Change the Wiki.js admin password after you first sign in.

Where files live

Compose project directory

/opt/noderings/wikijs
/opt/noderings/wikijs/docker-compose.yml
/opt/noderings/wikijs/.env

Working directory for compose, the stack file, and generated secrets.

Credentials file

/root/.noderings_password

Written once on first boot.

Boot unit

/etc/systemd/system/noderings-wikijs.service

Brings compose up after Docker is ready.

What runs in Docker

Compose runs Wiki.js with Postgres. The UI is on HTTP port 80.

  • wiki

    Wiki.js UI on HTTP port 80.

  • db

    Postgres database for Wiki.js.

Container status

cd /opt/noderings/wikijs && docker compose ps

Live logs

cd /opt/noderings/wikijs && docker compose logs -f

Restart containers

cd /opt/noderings/wikijs && docker compose restart

systemd unit status

systemctl status noderings-wikijs

Add HTTPS with Cloudflare

Your Wiki.js site starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.

  1. Add your domain

    Sign up at Cloudflare and add the domain you want to use.

  2. Point it at your VPS

    Create an A record to your server IP and leave the orange cloud on.

  3. Open the https site

    Visit https://your-domain and sign in with the admin credentials from your server notes.

  4. Only allow Cloudflare

    Optional. With SSH (port 22) already allowed and everything else blocked by default, open only Cloudflare to ports 80 and 443:

    curl -s https://www.cloudflare.com/ips-v4 | while read ip; do sudo ufw allow from "$ip" to any port 80,443 proto tcp; done

That is enough for a first secure visit. You can tighten SSL in Cloudflare later if you need it. Keep port 22 allowed for SSH; leave other ports denied except this Cloudflare allow for 80 and 443.

More detail

  • NodeRings does not sell Wiki.js as a product and is not the Wiki.js project.

Wiki.js VPS requirements and sizing

Wiki.js runs with Postgres. A quiet lab install fits in a modest RAM budget, but concurrent editors and uploads need headroom. These are starting points, not guarantees.

Illustrative starting points for Wiki.js VPS sizing
WorkloadIllustrative starting pointNote
Personal or small team wiki1 vCPU / 2 GB RAM / 20+ GB diskSuggested Instant App floor for Wiki.js plus Postgres.
Active documentation team2 vCPU / 4 GB RAMMore headroom when many editors and assets are in use at once.
Large librariesDisk sized to page history and filesUploads and history grow on the VPS volume. Keep backups off-box.
SMTP invitesSame size as the app; mail elsewhereOptional SMTP is configured in Wiki.js after deploy if you send invites by email.

These are starting points, not guarantees. Needs depend on team size, upload volume and how long you keep page history.

Root access and who does what

This is self-hosted Wiki.js on a provider VPS, not a managed Notion SaaS. You pick the plan. Wiki.js is prepared on that server. Day-to-day care stays with you.

  • What you get ready

    Wiki.js is prepared on the VPS with no Instant App form variables. The admin account is created for you.

  • What you keep

    Root SSH on the VPS. You own pages, users, DNS, TLS, OS updates, SMTP and backups unless a provider product says otherwise.

  • What is not included

    Managed SMTP, automatic TLS and Wiki.js paid add-ons are not bundled in. Finish TLS and mail after the server is up if you need them.

  • Support boundaries

    NodeRings helps with marketplace, billing and console. Provider hardware issues go to that provider. Looking after Wiki.js on the server is yours.

Wiki.js VPS FAQs

What is Wiki.js?

Wiki.js is a free, open-source documentation wiki. Teams use it for handbooks, specs and knowledge bases on hardware they control.

Do I need to fill Instant App variables for Wiki.js?

No. Wiki.js Instant App asks for no form variables at create time. After the VPS is ready, sign in with the admin email and password from your server notes.

Does NodeRings run the Wiki.js server?

No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Wiki.js is prepared on that provider server, and you manage the wiki from there.

Is this managed Wiki.js hosting?

No. You get a virtual machine with Wiki.js prepared for you, plus root access. That is different from a managed product that owns updates and support for you.

What is Wiki.js Instant App?

It prepares Wiki.js on the VPS you choose so you skip hunting through install guides by hand. It is still your self-hosted server, not a separate managed hosting brand.

How do I sign in after deploy?

Open http://YOUR_IP/ and sign in with wikijs_admin_email and wikijs_admin_pass from /root/.noderings_password. Nothing was collected from you at checkout for Wiki.js.

What size Wiki.js VPS do I need?

A common starting point is about 1 vCPU, 2 GB RAM and 20 GB disk. Larger teams and upload libraries usually need more RAM and disk. Use the sizing guide above and compare plans in the list.

Can I invite teammates by email?

Yes after you configure SMTP in Wiki.js settings. Invites and password resets need mail credentials you add yourself.

What happens after I click Deploy Wiki.js?

You confirm the plan and finish checkout. When the server is ready, open the site URL and sign in with the admin credentials from your server notes.

Can I choose the server region?

Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.

Back to live Wiki.js plans

Compare provider offers, then launch Wiki.js on the plan that fits.