Install or update your VPS.

Keep your data. Add the new controls.

Extract the new package outside your website’s public folder. From its harbor directory, run:

sudo bash deploy/install-agent.sh --check
sudo bash deploy/install-agent.sh --install

The installer briefly stops Harbor, takes a protected snapshot of member data, and replaces the app. Existing Docker workloads continue running. It checks Docker and the updated portal before reporting success. Reload your browser afterward and reconnect the admin page with your private token.

Member accounts now have a primary server and an optional secondary. Members can delete unwanted servers, while their named data volumes remain for operator recovery. A secondary may be stopped to make room for a primary; it keeps its data and can be restarted when spare capacity returns.

Download the new release before updating. This download contains the version currently serving this page. If your VPS still runs the older release, use the new release link supplied with the update. The upgrade guide includes upload, verification and recovery steps.

Dynamic capacity, with a minimum of 10.

The server count grows or shrinks with the CPU and RAM already allocated. It can show 15, 20, 50 or more slots, up to 500. It uses reserved resources rather than momentary CPU activity, so idle workloads cannot cause overbooking when they get busy.

The minimum of 10 is a service-count floor; every server still needs to fit the shared CPU/RAM budget. Larger server types may use the available resources before that count is reached. Admin can also choose a fixed count.

Primary servers and owner-created servers keep their allocation while stopped. Stopped member secondaries release active capacity, but retain their container and saved data. Storage remains on disk and needs monitoring and backups.

Three tiers. One primary and one secondary.

• Starter: 0.25 CPU + 250 MB RAM per server. Automatic account access; deployment still needs free shared capacity.
• Standard: 0.5 CPU + 500 MB RAM per server. Granted when capacity permits; otherwise the account joins the waitlist.
• Plus: 1 CPU + 1024 MB RAM per server. Requires administrator approval and available capacity.

A secondary uses spare capacity. When another primary needs room it can be stopped gracefully, keeping its credentials, port and saved data. Its owner can restart it when capacity is available. Deleting a server removes its container, while retaining its named data volume for operator recovery.

Server types have their own requirements. PostgreSQL and Redis fit all three tiers. MySQL needs at least 512 MB, so Standard’s 500 MB is too small. Minecraft Java needs 1024 MB / 1 CPU and EULA consent, with a hosted limit of five players. MySQL and Minecraft require Plus under these defaults.

For larger services or custom images, run Harbor on your own computer or VPS and use its host console. Database ports stay private on that machine; application connections or authenticated tunnels need to be arranged by the owner.

Keep member and server data backed up.

Back up /var/lib/harbor-agent/portal privately, separately from game/database volumes. The installer creates a protected portal snapshot during an update; this is not a workload-data backup. Disk storage has no per-member quota.

A static preview does not save real registrations or run Docker. The VPS backend handles real accounts and workloads. Check image startup, credentials and saved data on the actual host after upgrading.