SkyPort Logo

SkyPort Docs

Deployment

Scaling

How to scale SkyPort operationally without inventing unsupported orchestration.

SkyPort does not currently advertise automatic horizontal scaling. Scale it the same way many self-hosted infrastructure tools scale: by adding capacity, isolating responsibilities, and keeping each layer simple.

Practical Scaling Patterns

  • move the backend to a larger VPS when the host is saturated
  • split workloads across multiple VPS profiles
  • keep Docker workloads separate from PM2-managed processes where possible
  • use reverse proxy mappings to keep public entrypoints stable

What To Monitor First

terminal
skyport status
skyport docker ps
skyport pm2 list

What Not To Claim

  • automatic auto-scaling
  • cluster scheduling
  • multi-node orchestration unless the feature is actually implemented

Next

  1. Read Production Setup.
  2. Read Monitoring.

Production Setup

Run SkyPort in production using systemd, reverse proxy, HTTPS, and real VPS infrastructure.

GitHub Actions

Deploy the SkyPort docs site and build artifacts with GitHub Actions.

SkyPort

SkyPort Docs

Self-hosted infrastructure platform