Skip to content

Deploy from a private GitHub or GitLab repository

Deploying from a private repository works exactly like a public one — you just add a personal access token (PAT) so the panel can clone it. OrbixPanel uses the token for the clone and then discards it; it’s never written to the build log.

Create a read-only token

GitHub:

  1. Go to Settings → Developer settings → Personal access tokens → Fine-grained tokens.
  2. Give it Contents: Read-only access to just the repo you’re deploying.
  3. Copy the token (you only see it once).

GitLab:

  1. Preferences → Access Tokens (or a project Deploy Token).
  2. Scope: read_repository.
  3. Copy it.

Always use the narrowest scope possible — read-only, single repo. The token only needs to clone, nothing more.

Deploy

  1. In Apps → Deploy from Git, paste the repository URL and branch.
  2. Paste your access token in the token field.
  3. Click Deploy.

The panel clones over HTTPS using the token, then builds and serves exactly like a normal Git deploy. The token is redacted from any output and not retained after the clone.

Rotating the token

If you ever revoke or rotate the token on GitHub/GitLab, just paste the new one the next time you deploy. A good habit: give deploy tokens an expiry and refresh them on a schedule.


Running OrbixPanel? Private-repo deploys are built in. OrbixPanel.com → — the free, self-hosted, AI-powered hosting control panel.