---
title: Private Repositories
url: "/docs/build/private-repositories/"
canonical_url: https://docs.blossom88.com/docs/build/private-repositories/
markdown_url: https://docs.blossom88.com/docs/build/private-repositories.md
summary: Build from a private Git repository with a deploy key
categories:
- build
---

# Private Repositories

Blossom builds from a private repository over SSH with a **deploy key**.
Blossom generates the key pair and keeps the private half; you add the public
half to your repository. Ask your agent:

> Generate a deploy key for my private repository and show me its public key.

## Generate A Key

    blossom git_ssh_key:create -d '{"git_ssh_key":{"name":"storefront"}}'
    blossom git_ssh_key:show --id git_ssh_key-100

In the dashboard, open **Integrations → Git SSH Keys** and choose **Generate
Deploy Key**. The key's page shows the public key and its SHA256 fingerprint,
the same one your Git host shows.

## Add It To Your Repository

Read access is enough: Blossom only clones.

| Git host | Where the key goes |
| --- | --- |
| GitHub | Repository → Settings → Deploy keys → Add deploy key |
| GitLab | Project → Settings → Repository → Deploy keys |
| Bitbucket | Repository settings → Access keys → Add key |

GitHub takes a key on one repository, so generate one per repository there.

## Check Access

On the key's page, paste the repository's SSH URL and choose **Check Access**.
Blossom signs in to your Git host with the key and asks for the repository,
the way a Build's clone starts.

## Deploy With It

Use the repository's SSH URL and name the key in your plan:

app_plan.yml:

```yaml
app_plan:
  app_name: storefront
  repository_type: private_ssh
  clone_url: git@github.com:acme/storefront.git
  git_ssh_key_id: git_ssh_key-100
```

    blossom app_plan:create --data app_plan.yml

## What You Get

- Builds that clone your private repository without sharing a personal token
- A key scoped to the repositories you add it to
- A check that tells you the key works before the first Build
