Shared Compute - General Compute
$5.00/mo
1 vCPU · 1 GB · 20 GB
Choose location
Ashburn, United States
| Provider | Plan | vCPU | RAM | Disk | Regions | Billing | Price |
|---|---|---|---|---|---|---|---|
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Amsterdam, Netherlands | Fixed price | $5.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Amsterdam, Netherlands | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Fixed price | $9.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Amsterdam, Netherlands | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 4 | 8 GB | 160 GB | Ashburn, United States | Fixed price | $16.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Amsterdam, Netherlands | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 8 | 16 GB | 320 GB | Ashburn, United States | Fixed price | $32.00/mo |
| Enzonix | Shared Compute - General Compute | 1 | 1 GB | 20 GB | Ashburn, United States | Hourly | $0.007/hr |
| Enzonix | Shared Compute - General Compute | 1 | 2 GB | 40 GB | Ashburn, United States | Hourly | $0.01/hr |
| Enzonix | Shared Compute - General Compute | 2 | 4 GB | 80 GB | Ashburn, United States | Hourly | $0.015/hr |
Wiki.js Instant App
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
Choose billing and size, compare providers side by side, pick a location, then launch.
1 provider
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.

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

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

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

Sites, groups, users and system health in one place. Keep operations on your VPS instead of a SaaS tenant.
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.
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.
Pick a plan and Wiki.js is prepared on that VPS for you, including the admin account. You still get root access.
Compatible offers list cities and countries. Keep latency low for your team or keep data in a place that matches policy.
Pages, assets and users live on your VPS volume. You control SSH, DNS and who can open the wiki.
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.
Compare plans, pick a provider offer, and launch Wiki.js on that server.
01
Browse live offers below. A 2 GB plan is a solid start for Wiki.js with Postgres. Sort by provider, size, price and region.
02
Choose the provider plan and region. There are no Instant App form fields to fill for Wiki.js.
03
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.
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.
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_passwordCompose project directory
/opt/noderings/wikijs
/opt/noderings/wikijs/docker-compose.yml
/opt/noderings/wikijs/.envWorking directory for compose, the stack file, and generated secrets.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Boot unit
/etc/systemd/system/noderings-wikijs.serviceBrings compose up after Docker is ready.
Compose runs Wiki.js with Postgres. The UI is on HTTP port 80.
wikiWiki.js UI on HTTP port 80.
dbPostgres database for Wiki.js.
Container status
cd /opt/noderings/wikijs && docker compose psLive logs
cd /opt/noderings/wikijs && docker compose logs -fRestart containers
cd /opt/noderings/wikijs && docker compose restartsystemd unit status
systemctl status noderings-wikijsYour Wiki.js site starts on http://. Cloudflare can give visitors a padlock without installing anything on the VPS.
Add your domain
Sign up at Cloudflare and add the domain you want to use.
Point it at your VPS
Create an A record to your server IP and leave the orange cloud on.
Open the https site
Visit https://your-domain and sign in with the admin credentials from your server notes.
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; doneThat 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.
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.
| Workload | Illustrative starting point | Note |
|---|---|---|
| Personal or small team wiki | 1 vCPU / 2 GB RAM / 20+ GB disk | Suggested Instant App floor for Wiki.js plus Postgres. |
| Active documentation team | 2 vCPU / 4 GB RAM | More headroom when many editors and assets are in use at once. |
| Large libraries | Disk sized to page history and files | Uploads and history grow on the VPS volume. Keep backups off-box. |
| SMTP invites | Same size as the app; mail elsewhere | Optional 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.
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.
Wiki.js is prepared on the VPS with no Instant App form variables. The admin account is created for you.
Root SSH on the VPS. You own pages, users, DNS, TLS, OS updates, SMTP and backups unless a provider product says otherwise.
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.
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 is a free, open-source documentation wiki. Teams use it for handbooks, specs and knowledge bases on hardware they control.
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.
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.
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.
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.
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.
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.
Yes after you configure SMTP in Wiki.js settings. Invites and password resets need mail credentials you add yourself.
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.
Yes. Each compatible plan lists available regions. Pick the city or country that matches latency and compliance needs.