Storage

The Orchestrator manages artifact storage for pipeline runs. Artifacts produced during job execution (build outputs, test reports, logs) are stored and made available for download.

💾 Storage Modes

Configure the storage mode during project setup or from Project Settings → Storage.

Internal

Artifacts are stored on the orchestrator’s managed storage. No external configuration needed.

Best for: Small teams, development environments, or when artifact volume is low.

Orchestrator Proxy

The orchestrator proxies all upload and download requests to an S3-compatible backend. Agents communicate only with the orchestrator.

Agent → Orchestrator → S3

Best for: Teams that want centralized control over storage access without exposing S3 credentials to agents.

Orchestrator Pre-sign

The orchestrator generates pre-signed S3 URLs and provides them to agents. Agents upload and download directly to/from S3 using these temporary URLs.

Agent → S3 (via pre-signed URL)

Best for: High-volume artifact storage where you want to offload bandwidth from the orchestrator.

Agent Direct

Agents access the S3 backend directly using their own credentials.

Agent → S3 (direct)

Best for: Teams where agents already have S3 access and you want the simplest data path.

☁️ S3 Configuration

When selecting an S3-backed storage mode, configure the following fields in the storage settings page:

Field	Description
Bucket	S3 bucket name
Region	AWS region
Endpoint	S3 endpoint URL (use custom endpoints for MinIO, R2, etc.)
Access key	AWS access key ID
Secret key	AWS secret access key
Prefix	Optional path prefix within the bucket

S3-Compatible Providers

Any S3-compatible storage backend works, including AWS S3, MinIO, Cloudflare R2, DigitalOcean Spaces, and Backblaze B2. Set the endpoint field to your provider’s S3-compatible endpoint.

📐 Scope Hierarchy

Storage configuration can be set at three levels:

• Personal: Default for personal projects (Settings → Storage)
• Organization: Shared across org projects (Organization Settings → Storage)
• Repository: Per-project override (Project Settings → Storage)

Repository-level config takes priority over organization, which takes priority over personal.

🛡️ Organization Policy

Organization admins can enforce a storage mode from Organization Settings → Security Policy. When set to non-overridable, all projects must use the specified mode. See Organizations for details.

For programmatic storage configuration, see REST API.