Komodo Instant App

Self-hosted Komodo VPS hosting

Komodo is an open-source control plane for Docker hosts, compose stacks and deployments. Compare live VPS prices, CPU, RAM, disk and regions, launch with a prepared admin login on the plan you choose, and keep root access.

Komodo

Instant App on marketplace VPS

Live marketplace offers

Compare Komodo VPS plans

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

No compatible plans are listed right now.

Inside Komodo

Komodo is an open-source Docker and compose control plane with Core UI and a Periphery agent. Use it instead of paying for Portainer Business. Sign in after boot with the prepared admin account. No Instant App form fields are required at create time.

  • Komodo dashboard after Instant App setup

    Dashboard

    See servers and resources in the Core UI after you sign in.

  • Komodo sign-in page with registration disabled

    Prepared admin, closed signup

    The Instant App creates the admin account and disables user registration.

  • Komodo stacks / compose view

    Stacks and compose

    Deploy and manage compose stacks on the Local Periphery agent that ships with this Instant App.

  • Komodo servers list

    Servers

    The Local server is registered for you. Add more Periphery agents later when your fleet grows.

Why use the NodeRings marketplace?

Compare live Komodo VPS plans from independent providers, then self-host Docker and compose management on the offer you pick. Use it instead of paying for Portainer Business.

  • Compare Komodo VPS offers in one place

    See live prices, regions and plan sizes before you buy. Shop Docker control-plane hosts across independent providers, from the 2 vCPU and 2 GB floor upward.

  • Self-host Komodo without a manual install

    Pick a plan and Komodo Core, Periphery and MongoDB are prepared on that VPS for you, including the admin account. You still get root access.

  • Manage stacks near your servers

    Compatible offers list cities and countries. Keep compose deploys and UI latency low for the region you pick.

  • Admin login and closed registration

    The Instant App creates your admin and disables user registration so strangers cannot open accounts on your IP.

Komodo hosting as a marketplace, not a single hoster

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

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

Single-provider Komodo hosting

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

NodeRings marketplace

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

How it works

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

  1. 01

    Compare Komodo VPS plans

    Browse live offers below. Start around 2 vCPU and 2 GB RAM with 20 GB disk. Prefer more RAM when many stacks run on the same host.

  2. 02

    Deploy Komodo on the plan you pick

    Finish checkout on that provider offer. Komodo and the first admin login are prepared on the VPS for you. There are no Instant App form fields.

  3. 03

    Sign in and manage stacks

    Open the site URL and use the admin credentials from your server notes. Deploy compose stacks through the Local server.

On the VPS after Komodo deploys

NodeRings Instant App brings Komodo Core, Periphery and MongoDB up with Docker Compose and prepares the first admin 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 komodo_admin_user and komodo_admin_pass from the credentials file.
  • The Local server should appear under Servers once Periphery connects.

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 komodo_admin_user, komodo_admin_pass, site_url and admin_url.
  • SSH in as root with the create-flow password or key, then run the command above.
  • Change the Komodo admin password after you first sign in if you prefer a new secret.

Where files live

Compose project directory

/opt/noderings/komodo
/opt/noderings/komodo/docker-compose.yml
/opt/noderings/komodo/.env
/opt/noderings/komodo/backups

Compose file, secrets and Core backups directory.

Periphery root directory

/etc/komodo

Stacks and repos for the Local Periphery agent.

Credentials file

/root/.noderings_password

Written once on first boot.

Install logs

/tmp/komodo-admin.log

Login probe log from first boot.

What runs in Docker

Compose runs MongoDB, Komodo Core and Komodo Periphery. The UI is on HTTP port 80 (container 9120).

  • mongo

    MongoDB for Komodo Core state.

  • core

    Komodo Core web UI and API on HTTP port 80.

  • periphery

    Local Periphery agent with Docker socket access.

Container status

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

Live logs

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

Restart stack

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

Login API check

source /opt/noderings/komodo/.env && curl -sS -X POST http://127.0.0.1/auth/login/LoginLocalUser -H 'Content-Type: application/json' -d "{\"username\":\"${ADMIN_USER}\",\"password\":\"${ADMIN_PASS}\"}"

Add HTTPS with Cloudflare

Your Komodo UI 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 credentials from /root/.noderings_password.

  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

Keep port 22 allowed for SSH. Leave other ports denied except this Cloudflare allow for 80 and 443.

More detail

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

Komodo VPS requirements and sizing

Komodo runs Core, Periphery and MongoDB on the same VPS in this Instant App. Idle use is moderate; concurrent stack deploys push the plan up.

Illustrative starting points for Komodo VPS sizing
WorkloadIllustrative starting pointNote
Single host control plane2 vCPU / 2 GB RAM / 20+ GB diskSuggested Instant App floor for Core + Periphery + Mongo on one VPS.
Many stacks on the same host2 to 4 vCPU / 4+ GB RAMCompose workloads share the VPS with Komodo itself.
Backups and stack dataDisk sized to retention plus growthCore backups live under /opt/noderings/komodo/backups. Stack files use /etc/komodo.
Extra Periphery agentsSame Core size; agents on other machinesThis Instant App includes a Local agent. Add remote agents when your fleet grows.

These are starting points, not guarantees. Needs depend on stack count, image pulls and concurrent deploys.

Root access and who does what

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

  • What you get ready

    Komodo Core, Periphery and MongoDB are prepared with a first admin account, local auth enabled, user registration disabled, and no Instant App form variables. The Docker socket is mounted for the Local Periphery agent.

  • What you keep

    Root SSH on the VPS. You own provider billing, DNS, TLS, stacks, backups and day-to-day Komodo care.

  • What is not included

    A domain, TLS certificates, backup jobs and additional remote agents are not part of the Instant App. You add those after the server is ready.

  • Support boundaries

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

Komodo VPS FAQs

Is this managed Komodo hosting?

No. You get a virtual machine with Komodo prepared for you, plus root access. That is different from a managed Docker panel that owns upgrades and backups for you.

What is Komodo Instant App?

It prepares Komodo 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 komodo_admin_user and komodo_admin_pass from /root/.noderings_password.

Can strangers create accounts on my instance?

No. User registration is disabled. Invite people from inside Komodo when you want teammates.

Does NodeRings run the Komodo server?

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

What size Komodo VPS do I need?

A common starting point is about 2 vCPU, 2 GB RAM and 20 GB disk. Prefer more RAM when many compose stacks share the host.

Why is the Docker socket mounted?

The bundled Periphery agent manages containers on this VPS. Keep admin access private and review stack definitions before you trust them.

Back to live Komodo plans

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