Yacht Instant App
Self-hosted Yacht VPS hosting
Yacht is an open-source Docker management UI with templates and one-click app deploys. Compare live VPS prices, CPU, RAM, disk and regions, launch with a prepared admin login on the plan you choose, and keep root access.
Yacht
Instant App on marketplace VPS
Live marketplace offers
Compare Yacht VPS plans
Choose billing and size, compare providers side by side, pick a location, then launch.
Inside Yacht
Yacht is an open-source Docker management UI with templates for one-click app deploys. Sign in after boot with the prepared admin account. No Instant App form fields are required at create time.

Dashboard
See containers and host status in the Yacht UI after you sign in.

Prepared admin login
The Instant App creates the admin account. New users can only be added by a signed-in admin.

Applications
Browse and manage containers on the local Docker host.

Templates
Use Yacht templates for one-click style deploys of common self-hosted apps.
Why use the NodeRings marketplace?
Compare live Yacht VPS plans from independent providers, then self-host a Docker container management UI with templates on the offer you pick. Use it instead of paying for Portainer Business.
Compare Yacht VPS offers in one place
See live prices, regions and plan sizes before you buy. Shop Docker management hosts across independent providers, from the 1 vCPU and 1 GB floor upward.
Self-host Yacht without a manual install
Pick a plan and Yacht is prepared on that VPS for you, including the admin account. You still get root access.
Manage containers near your servers
Compatible offers list cities and countries. Keep UI latency low for the region you pick.
Admin login without open signup
The Instant App creates your admin. Creating additional users requires that admin session, so strangers cannot open accounts on your IP.
Yacht hosting as a marketplace, not a single hoster
Most Yacht 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.
Yacht Instant App prepares Yacht on the provider VPS you selected. NodeRings does not operate that hardware or sell its own VPS fleet.
Single-provider Yacht hosting
- One company catalogue and renewal pricing
- One set of regions and support paths
- One vendor panel for that host only
NodeRings marketplace
- Yacht VPS offers from independent providers
- Compare resources, prices and regions side by side
- Deploy Yacht on the plan you pick
How it works
Compare plans, pick a provider offer, and launch Yacht on that server.
01
Compare Yacht VPS plans
Browse live offers below. Start around 1 vCPU and 1 GB RAM with 20 GB disk. Prefer more RAM when many containers share the host.
02
Deploy Yacht on the plan you pick
Finish checkout on that provider offer. Yacht and the first admin login are prepared on the VPS for you. There are no Instant App form fields.
03
Sign in and manage containers
Open the site URL and use the admin credentials from your server notes. Deploy templates and manage containers from there.
On the VPS after Yacht deploys
NodeRings Instant App brings Yacht 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 yacht_admin_user and yacht_admin_pass from the credentials file.
- Use Applications and Templates to manage containers on this host.
Where the password is
Credentials are written on first boot to:
/root/.noderings_passwordRead them over SSH:
cat /root/.noderings_password- Keys in that file include yacht_admin_user, yacht_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 Yacht admin password after you first sign in if you prefer a new secret.
Where files live
Compose project directory
/opt/noderings/yacht
/opt/noderings/yacht/docker-compose.yml
/opt/noderings/yacht/.env
/opt/noderings/yacht/configCompose file, secrets and Yacht config volume (SQLite).
Compose projects directory
/opt/noderings/yacht/config/composeCOMPOSE_DIR for Yacht compose projects.
Credentials file
/root/.noderings_passwordWritten once on first boot.
Install logs
/tmp/yacht-admin.logLogin probe log from first boot.
What runs in Docker
Compose runs a single Yacht service. The UI is on HTTP port 80 (container 8000).
yachtYacht web UI and API on HTTP port 80.
Container status
cd /opt/noderings/yacht && docker compose psLive logs
cd /opt/noderings/yacht && docker compose logs -fRestart stack
cd /opt/noderings/yacht && docker compose restartLogin API check
source /opt/noderings/yacht/.env && curl -sS -X POST http://127.0.0.1/api/auth/login -H 'Content-Type: application/json' -d "{\"username\":\"${ADMIN_EMAIL}\",\"password\":\"${ADMIN_PASSWORD}\"}"Add HTTPS with Cloudflare
Your Yacht UI 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 credentials from /root/.noderings_password.
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 Yacht as a product and is not the Yacht project.
Yacht VPS requirements and sizing
Yacht itself is light. The containers you deploy through it are what push the plan up.
| Workload | Illustrative starting point | Note |
|---|---|---|
| UI and a few containers | 1 vCPU / 1 GB RAM / 20+ GB disk | Suggested Instant App floor for Yacht on one VPS. |
| Many apps on the same host | 2 vCPU / 2+ GB RAM | App workloads share the VPS with Yacht itself. |
| Compose projects and images | Disk sized to image pulls plus growth | Compose projects live under /opt/noderings/yacht/config/compose. |
| Backups | Snapshot the VPS or back up /opt/noderings/yacht | Yacht state is in the config volume (SQLite). |
These are starting points, not guarantees. Needs depend on container count, image size and concurrent deploys.
Root access and who does what
This is self-hosted Yacht on a provider VPS, not managed Docker SaaS. You pick the plan. Yacht is prepared on that server. Day-to-day care stays with you.
What you get ready
Yacht is prepared with a first admin account, auth enabled, and no Instant App form variables. The Docker socket is mounted so Yacht can manage containers on this VPS.
What you keep
Root SSH on the VPS. You own provider billing, DNS, TLS, containers, backups and day-to-day Yacht care.
What is not included
A domain, TLS certificates, backup jobs and extra 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 Yacht on the server is yours.
Yacht VPS FAQs
Is this managed Yacht hosting?
No. You get a virtual machine with Yacht prepared for you, plus root access. That is different from a managed Docker panel that owns upgrades and backups for you.
What is Yacht Instant App?
It prepares Yacht 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 yacht_admin_user and yacht_admin_pass from /root/.noderings_password.
Can strangers create accounts on my instance?
No. Creating users requires an authenticated admin. The Instant App only creates the first admin for you.
Does NodeRings run the Yacht server?
No. NodeRings is a marketplace. Independent providers list VPS plans. You pick a plan, Yacht is prepared on that provider server, and you manage Docker from there.
What size Yacht VPS do I need?
A common starting point is about 1 vCPU, 1 GB RAM and 20 GB disk. Prefer more RAM when many containers share the host.
Why is the Docker socket mounted?
Yacht manages containers on this VPS. Keep admin access private and review templates before you trust them.
