LFS HarborLFS Harbor

Configure your server

LFS Harbor stores objects in an external storage backend. Choose the provider that suits your infrastructure.

Storage backends

Google Cloud Storage

Single-region GCS bucket with a least-privilege service account key.

Amazon S3

S3 bucket with a dedicated IAM user and scoped access policy.

Cloudflare R2

S3-compatible bucket with no egress fees, using a scoped R2 API token.

MinIO

Self-hosted S3-compatible object storage with service account credentials.

S3-compatible storage

LFS Harbor transfers objects using S3 v4 presigned URLs. When a git client pushes or pulls a large file, LFS Harbor generates a short-lived signed URL and hands it directly to the client — the object is transferred straight to the storage backend without proxying through the LFS Harbor server. Any provider that implements the S3 API and supports v4 presigned URLs is compatible via the MinIO setup guide.

Known compatible providers

  • Backblaze B2
  • Wasabi
  • DigitalOcean Spaces
  • Linode Object Storage
  • Scaleway Object Storage

Any S3-compatible provider that supports v4 presigned URLs should work. If yours isn't listed, try the MinIO setup guide and point the endpoint at your provider.

Request support for another provider

Need a first-class integration with a provider not listed above?