Celebrating 10 Years | Since 2016

Private Gradle Repository Hosting

Enterprise-grade Gradle artifact hosting with flat, predictable pricing, unlike JFrog Artifactory's metered model. No egress fees, no per-user pricing. Just powerful repository management that works.

Flat, predictable pricing vs JFrog Artifactory

Setup in 5 minutes, not days

Native Kotlin DSL and Groovy support

Start free 14-day trial See pricing comparison

No credit card required • Setup in minutes • Cancel anytime

repositories {
    maven {
        url "https://acme.mycloudrepo.io/repositories/libs"
        credentials {
            username = System.getenv("CLOUDREPO_USER")
            password = System.getenv("CLOUDREPO_PASS")
        }
    }
}

Calculate Your Savings

See how much you can save compared to JFrog and Nexus

Storage Needed

250 GB

Monthly Data Transfer (Downloads/Egress)

1 TB

Common Scenarios

JFrog Artifactory

Consumption

Base Cost $150

Usage Costs $0

Monthly $150

Annual $1,800

25GB included. $1.25/GB (26-1204GB), $1.00/GB (1205-2024GB), $0.75/GB (2025+GB)

Nexus Repository

Consumption

Base Cost $135

Usage Costs $0

Monthly $135

Annual $1,620

20GB included. $1.10/GB (first 1000GB), $0.90/GB (above 1000GB)

CloudRepo

Predictable

Plan Team

Storage Included 250 GB

Transfer Included 3 TB / month

Monthly Total $499

Annual Cost $5,988

No egress fees. We never meter downloads per GB. Fair-use transfer with reach-out-first overage.

Your Savings with CloudRepo

Monthly Savings $0

Annual Savings $0

Percentage Saved 0%

Compared to the higher-priced competitor

Start Saving Now

Everything you need for Gradle builds

CloudRepo gives you the features you need at fair, predictable pricing

Native Gradle Support: First-class support for Gradle builds with both Groovy and Kotlin DSL configurations.
SNAPSHOT Versioning: Full support for SNAPSHOT versions with automatic cleanup policies and metadata management.
Multi-Module Projects: Perfect for complex Gradle builds with multiple subprojects and composite builds.
Zero Egress Fees: No charges for downloading dependencies. Build as often as you need without cost concerns.
Maven Compatible: Host both Gradle and Maven artifacts in the same repository for maximum flexibility.
Enterprise Security: User management, API tokens, and team-based access controls.

Quick Gradle Setup Guide

Get your Gradle repository running in minutes, not hours

Configure Your Repository

Add CloudRepo to your build.gradle for publishing artifacts.

                    // build.gradle (Groovy DSL)
publishing {
    repositories {
        maven {
            name = "CloudRepo"
            url = "https://[organization-id].mycloudrepo.io/repositories/[repository-id]"
            credentials {
                username = System.getenv("CLOUDREPO_USERNAME")
                password = System.getenv("CLOUDREPO_PASSWORD")
            }
        }
    }
}

Configure Dependencies

Add CloudRepo as a source for your project dependencies.

                    // settings.gradle.kts (Kotlin DSL)
dependencyResolutionManagement {
    repositories {
        maven {
            url = uri("https://[organization-id].mycloudrepo.io/repositories/[repository-id]")
            credentials {
                username = System.getenv("CLOUDREPO_USERNAME")
                password = System.getenv("CLOUDREPO_PASSWORD")
            }
        }
        mavenCentral()
    }
}

Publish Your Artifacts

Deploy artifacts with standard Gradle commands. Works with CI/CD pipelines.

                    # Publish release version
./gradlew publish

# Publish snapshot version
./gradlew publish -Pversion=1.0.0-SNAPSHOT

# Publish specific module
./gradlew :module-name:publish

Need more details?

Check out our comprehensive Gradle documentation with advanced configurations and best practices.

View Gradle Documentation

Perfect for modern Gradle teams

From microservices to monoliths, CloudRepo scales with your architecture

Microservices Architecture

Host shared libraries and service artifacts. Perfect for Spring Boot microservices with automatic SNAPSHOT management for continuous deployment.

Android Development

Distribute internal Android libraries and SDK components. Full support for Android Gradle Plugin and AAR packages.

Multi-Module Projects

Manage complex Gradle builds with composite builds and includedBuilds. Perfect version management across all subprojects.

CI/CD Pipelines

Seamless integration with Jenkins, GitHub Actions, and GitLab CI. Publish artifacts automatically on every build.

Frequently asked questions

Everything you need to know about CloudRepo for Gradle

How does CloudRepo compare to JFrog Artifactory for Gradle?: CloudRepo provides native Gradle support at a fraction of Artifactory's metered cost. We include a generous transfer allowance (no egress fees), support is included free, and setup takes minutes instead of days. For most teams, CloudRepo delivers everything Artifactory does at a predictable, flat price.
Can I migrate from Artifactory or Nexus?: Yes! CloudRepo supports the same Maven repository format used by Artifactory and Nexus. You can easily migrate your existing artifacts, and your Gradle builds will work with minimal configuration changes.
Does CloudRepo support Gradle build caching?: Yes, CloudRepo fully supports Gradle's build cache, helping your team achieve faster builds by reusing outputs from previous builds. This feature is included in all plans, unlike competitors who charge extra.
How do SNAPSHOT versions work in CloudRepo?: CloudRepo provides full SNAPSHOT support with automatic cleanup policies. You can configure retention periods, and we handle metadata management automatically. Your CI/CD pipeline can publish SNAPSHOTs continuously without storage concerns.
What's included in CloudRepo's free support?: All CloudRepo plans include direct access to our engineering team, with typical response times under 2 hours. Unlike JFrog's $100k+ support contracts, we believe good support should be standard, not a luxury.

Why JVM teams choose CloudRepo

“Your software is solid for being so young and we hope to consolidate our binaries from two disparate sources into CloudRepo. I am thoroughly finished with Artifactory and JFrog on the whole.”

Clarence A.

Engineer, Kraneware

“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.”