🚀 Built for CircleCI Teams

A Private Artifact Repository for CircleCI

A private artifact repository for your CircleCI jobs. Works with the Maven, Gradle, npm and Python tooling you already run, at a published price.

14 days free. No credit card required.

2min
Setup Time
$0
Hidden Fees
Simple
Published Pricing

Why CircleCI Teams Choose CloudRepo

Purpose-built for modern CI/CD workflows with features that accelerate development

Lightning Fast Builds

US-based infrastructure ensures your dependencies download quickly for faster CI builds.

Enterprise Security

Encryption with TLS in transit and AES-256 at rest, plus team-based access controls for your artifacts.

CircleCI Contexts

Keep your CloudRepo token in one CircleCI context. Jobs that attach it read CLOUDREPO_TOKEN from the environment, and your config.yml holds no secret.

Parallel Workflows

Perfect for CircleCI's parallelism features and matrix builds.

Expert Support

Real engineers who understand CI/CD. Get help with migrations, optimizations, and best practices.

Set Up CloudRepo in Your CircleCI Pipeline

Get started in minutes with workflow templates you can copy

1

Create Your Repository

Sign up for CloudRepo and create your first repository in seconds.

# In CloudRepo Dashboard
+ New Repository
→ Type: Maven/Python/npm/Docker
→ Name: my-artifacts
✓ Create
2

Add CircleCI Context

Store your CloudRepo credentials securely in CircleCI contexts.

# CircleCI → Org → Contexts
→ Create Context: cloudrepo
→ Add Environment Variable
CLOUDREPO_TOKEN: paste your token
3

Update config.yml

Give your job the context so it receives the token.

.circleci/config.yml
workflows:
  build-deploy:
    jobs:
      - build-and-publish:
          context: cloudrepo

Configuration Examples for Your Stack

.circleci/config.yml
version: 2.1

jobs:
  build-and-publish:
    docker:
      - image: cimg/openjdk:17.0
    steps:
      - checkout
      - restore_cache:
          keys:
            - maven-{{ checksum "pom.xml" }}

      # Configure CloudRepo for Maven. The repository id in your pom.xml
      # distributionManagement must be cloudrepo.
      - run:
          name: Configure Maven Settings
          command: |
            mkdir -p ~/.m2
            # you@example.com is the email address of the account that created the token
            # Maven fills in ${env.NAME} from the context's variables when it runs, so the file holds no token
            cat > ~/.m2/settings.xml << 'EOF'
            <settings>
              <servers>
                <server>
                  <id>cloudrepo</id>
                  <username>you@example.com</username>
                  <password>${env.CLOUDREPO_TOKEN}</password>
                </server>
              </servers>
            </settings>
            EOF

      # Build and test
      - run: mvn clean test

      # Deploy to CloudRepo
      - run:
          name: Deploy to CloudRepo
          command: mvn deploy -DskipTests

      - save_cache:
          paths:
            - ~/.m2
          key: maven-{{ checksum "pom.xml" }}

workflows:
  version: 2
  build-deploy:
    jobs:
      - build-and-publish:
          context: cloudrepo

Perfect for Modern CircleCI Workflows

CloudRepo integrates seamlessly with CircleCI's advanced features

Microservices & Monorepos

Deploy hundreds of services efficiently with CloudRepo's unlimited repositories and parallel upload support.

  • Matrix builds with shared artifact caching
  • Dynamic configuration with per-service repositories
  • Fan-in/fan-out workflows with dependency management

Mobile App Development

Store iOS and Android builds, SDKs and release artifacts.

  • Store APKs, IPAs, and debug symbols
  • Automated nightly build distribution
  • Cross-platform dependency management

Machine Learning Pipelines

Store ML models, datasets and training artifacts.

  • Store model checkpoints and weights
  • Python package repository for custom libraries
  • Docker images for training environments

Enterprise Compliance

Access controls, repository tokens and overwrite protection for your release artifacts.

  • Release overwrite protection, enabled by default
  • Version history retained for 30 days after an overwrite
  • Team-based access with CircleCI contexts

Why Teams Switch from Self-Hosted Solutions

CloudRepo eliminates the overhead of managing your own artifact repository

Feature CloudRepo Self-Hosted JFrog Cloud
High Availability Complex
Security Updates Automatic Manual Automatic
Support Included Community on Pro; 24/7 SLA on Enterprise X
Total Cost (250GB, 1TB/mo egress) $499/month billed annually - $1,624/mo (list price, billed monthly)

Competitor figures were read on 2026-10-06 from: JFrog pricing (archived), JFrog Pro checkout (archived). Vendors change prices and plans, so check each page before you decide.

Every plan includes human support and SSO. See pricing

Why engineering teams choose CloudRepo

  • Perfecto
  • GoodRx
  • Paravision

“We were industrializing our partner-startup's codebase, and they were missing an artifact repository. We needed a private Maven repository, and we didn't want to set it up ourselves on AWS. We felt that CloudRepo was priced nicely with a good feature set. In my experience, managing a private repository takes maintenance (cleaning up snapshots, resizing disks, upgrades...) and I didn't want my team to waste time with that.”

Michael Técourt
Michael Técourt
Lead Architect, Dreev

“We use CloudRepo because we needed a closed source Maven Repository that could be easily managed to provide/restrict access to our clients, didn't cost the world to use, and that wouldn't require significant effort to set up/maintain.”

Paul Jervis
Paul Jervis
Director, Twelve Oaks Software

Ready to Optimize Your CircleCI Pipelines?

14 days free. No credit card required.

Have questions? Contact our CircleCI experts