Deploy from GitHub - Hyze Cloud

Use GitHub deploys when your source code already lives in a repository. Hyze downloads the branch, installs dependencies, detects the start command, and starts the app.

Prerequisites

Connect GitHub in the dashboard before using this flow: Dashboard → GitHub (or check status with GET /api/integrations/github/status).

Deploy a repository

curl -X POST https://api.hyzecloud.com/api/apps/deploy-from-repo \
  -H "Authorization: Bearer hyze_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "api",
    "runtime": "node",
    "memoryMB": 512,
    "exposePort": 3000,
    "autoDeploy": true,
    "repository": {
      "owner": "hyzecloud",
      "name": "api",
      "branch": "main"
    }
  }'

With autoDeploy: true, every push to the selected branch triggers a new deploy automatically.

Verify the result

Check status: GET /api/apps/:appId — wait for status: running
Open the logs: GET /api/apps/:appId/logs to watch startup

Common problems

404 when listing repositories

The GitHub integration isn’t connected for the workspace, or the app was installed with access restricted to other repositories. Reconnect at Dashboard → GitHub.

Deploy fails at the build step

Check build history: GET /api/apps/:appId/builds. Common causes: missing lockfile, incompatible runtime version, or a wrong start command. startupCommand is optional — omit it and Hyze detects (Vite, Next, Node, static, Python).

App starts but doesn't respond

Check exposePort: it must match the port your server listens on, and the server must accept connections on 0.0.0.0.

Next steps

View logs

Inspect startup and runtime output.

Apps reference

All app endpoints, including ZIP deploy.

Last modified on September 1, 2026

​Prerequisites

​Deploy a repository

​Verify the result

​Common problems

​Next steps

View logs

Apps reference

Prerequisites

Deploy a repository

Verify the result

Common problems

Next steps