Source control

Connect GitHub and GitLab — deploy from the repository you already use

Connect the GitHub or GitLab account you already work in and deploy straight from a repository — a static site to Pages, or a project onto managed hosting. You can also sign in to Zinn Digital with GitHub or GitLab. Every connection shows the privileges it needs, is validated on entry, and is stored in Vault — never in code or a log.

  • GitHub + GitLabconnect either account
  • Deploy to Pagesor to managed hosting
  • Sign in with GitLabas well as GitHub
  • Vault-stored tokensvalidated on entry

Connect once, safely

Connecting a source-control account uses the same connected-account flow as every other credential on the platform: least privilege, validated, and stored in Vault.

See the privileges first

Before you authorise anything, we show exactly which repository and account permissions the connection needs — nothing more — so you grant a scoped token rather than a blanket one.

Validated on entry

The moment you connect, we call the provider's API to confirm the token is live and correctly scoped, and show a green or red check. An invalid or over-scoped grant is refused.

Straight into Vault

A validated token is written to Vault through the same connection seam every credential uses. It is never committed to code, printed to a log, or left in an environment file.

Revocable, and audited

You can revoke our access at GitHub or GitLab, and remove the connection on our side, whenever you like. Every action taken through a connected account is audit-logged.

Deploy where it suits the project

A repository can go to a Pages host for a static or built site, or onto managed hosting for a full application. Pushes can trigger a redeploy so the live site tracks your default branch.

  • GitLab Pages and GitHub Pages for static and pre-built sites, driven from your connected account.
  • Cloudflare Pages as an alternative Pages target, for framework builds and edge delivery.
  • Managed hosting for a full WordPress, PHP, static or Node application, deployed from the repository.
  • Push-to-deploy: a push to your default branch can trigger a rebuild, so the live site tracks the repository.
  • The same connection powers sign-in — you can log in to Zinn Digital with GitHub or GitLab instead of a password.

From repository to live site

  1. Connect your account

    Authorise GitHub or GitLab with a scoped token. We show the privileges first and validate them on entry.

  2. Pick a repository and target

    Choose the repository and where it deploys — GitLab Pages, GitHub Pages, Cloudflare Pages, or managed hosting.

  3. Deploy

    We build and publish. A temporary URL lets you preview before DNS resolves.

  4. Track your branch

    Enable push-to-deploy so a push to your default branch rebuilds the live site automatically.

FAQ

Which source-control providers can I connect?

GitHub and GitLab. Connect the account you already work in and we can deploy from its repositories and, if you enable it, use it to sign you in. Both are driven through the same connected-account seam.

Can I sign in with GitLab as well as GitHub?

Yes. Alongside email and GitHub, you can sign in to your Zinn Digital account with GitLab. The identity layer handles the OAuth handshake; we never see your provider password.

Where can I deploy a repository?

To GitLab Pages, GitHub Pages or Cloudflare Pages for a static or built site, or onto managed hosting for a full application. You choose the target when you connect the repository, and pushes can trigger a redeploy.

How is my access token protected?

We show you the privileges the connection needs, validate the token against the provider's API on entry, and only then store it in Vault. It never touches code, a log or an environment file, and you can revoke it at the provider or remove the connection on our side at any time.

Can I use Pages deployment on the Footprint-Free line?

It is offered but flagged there. GitLab Pages and GitHub Pages share provider infrastructure and public gitlab.io / github.io domains, which is a footprint. For a zero-footprint network, deploy to isolated hosting instead; on Mainstream, Pages is first-class.

Deploy from your repository

Start a card-free 7-day trial, connect GitHub or GitLab, and deploy from the repository you already use — validated on entry and stored in Vault.

Start free