# Overview

Users generally store their artifacts in a version controlled repository (Git or Helm). In addition to users having to upload the artifacts to the Controller for workload deployments, it can also **pull** the artifacts directly from the repository if so configured.

* * *

## Supported Repository Types

The controller supports both [Git](https://en.wikipedia.org/wiki/Git) and [Helm](https://helm.sh/) type repositories. The controller also supports repositories that may be hosted in private networks behind firewalls.

* * *

## Security and Isolation

Repositories in the Controller follow the security isolation model supported by [Projects](https://docs.rafay.co/security/tenancy/projects/). This means that every Project has its own repositories and access to these are secured via the [RBAC](https://docs.rafay.co/security/rbac/roles/) model implemented by the Controller.

* * *

## Number of Repositories

There are no limits (soft or hard enforced) to the number of repositories that can be configured and in use in any Org or Project.

* * *
