Self-host

Self-host path for UGP

Self-host means running the UGP website, server, database, workers, and model/provider configuration on infrastructure you control.

  1. Prepare a VPS or private infrastructure for the website, server, database, Redis, Qdrant, and workers.
  2. Configure the site and API addresses, session secret, SMS delivery, Paddle, and model providers.
  3. Build and verify the website and server in your deployment environment.
  4. Run local verification in a private environment before exposing the service to users.
  5. Run database migrations, then verify accounts, payments, devices, teams, limits, and history.
  6. Deploy the website behind HTTPS with security headers and verify public and account routes.

When self-host makes sense

Controlled infrastructure

Use self-host when your team needs to run the website, API, storage, workers, and provider configuration on infrastructure you operate.

Policy review

Self-host is useful when security, procurement, data handling, network access, or model-provider policy must be reviewed before launch.

Explicit ownership

You own the environment variables, domains, backups, deploy procedure, monitoring, and provider keys. UGP should not hide that operational responsibility.

Owner responsibilities

  • Keep production secrets out of the repository and deployment evidence.
  • Back up database and storage before upgrades or migrations.
  • Verify account, billing, download, email, provider, and team flows after every deploy.
  • Monitor website, API, workers, Postgres, Redis, Qdrant, and nginx health.
  • Document rollback steps before changing production routes or container images.