Private Gradle Repository Hosting

Host your private Gradle and Maven artifacts with simple, published pricing and no per-user fees.

Simple, published pricing vs JFrog Artifactory

Setup in 5 minutes, not days

Native Kotlin DSL and Groovy support

Start free trial See pricing comparison

14 days free. No credit card required.

build.gradle.kts

repositories {
    maven {
        url = uri("https://your-org.mycloudrepo.io/repositories/your-repo")
        credentials {
            username = providers.gradleProperty("cloudrepoUsername").get()
            password = providers.gradleProperty("cloudrepoToken").get()
        }
    }
}

Included on every plan

Plans differ only in storage and transfer allowance.

Coming soon: Access log

Every plan includes human support and SSO. See pricing

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 a Snapshot Cleanup setting for how many snapshot builds to keep. A group of hosted repositories merges maven-metadata.xml across its members automatically.
Multi-Module Projects: Perfect for complex Gradle builds with multiple subprojects and composite builds.
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

Store Your Credentials

Keep the credential in ~/.gradle/gradle.properties, outside your project, so it is never committed. The username is your email address and the password is a repository token.

~/.gradle/gradle.properties

cloudrepoUsername=you@example.com
cloudrepoToken=YOUR_REPOSITORY_TOKEN

Configure Your Repository

Start your build script with the maven-publish plugin, then add CloudRepo as the repository. The group and version name your artifact, so put your own there.

build.gradle.kts

plugins {
    java
    `maven-publish`
}

group = "com.example"
version = "1.0.0"

publishing {
    publications {
        create<MavenPublication>("library") {
            from(components["java"])
        }
    }
    repositories {
        maven {
            url = uri("https://your-org.mycloudrepo.io/repositories/your-repo")
            credentials {
                username = providers.gradleProperty("cloudrepoUsername").get()
                password = providers.gradleProperty("cloudrepoToken").get()
            }
        }
    }
}

build.gradle

plugins {
    id 'java'
    id 'maven-publish'
}

group = 'com.example'
version = '1.0.0'

publishing {
    publications {
        library(MavenPublication) {
            from components.java
        }
    }
    repositories {
        maven {
            url = "https://your-org.mycloudrepo.io/repositories/your-repo"
            credentials {
                username = findProperty("cloudrepoUsername")
                password = findProperty("cloudrepoToken")
            }
        }
    }
}

Already Have a Build Script?

Keep it, with its own group and version, and copy in the publishing block from the file in step 2. Then add the plugin. In a Kotlin script, add maven-publish to the plugins block at the top of the file. In a Groovy script, add this line above the publishing block:

build.gradle

apply plugin: "maven-publish"

Configure Dependencies

Add CloudRepo as a source for your project dependencies.

settings.gradle.kts

dependencyResolutionManagement {
    repositories {
        maven {
            url = uri("https://your-org.mycloudrepo.io/repositories/your-repo")
            credentials {
                username = providers.gradleProperty("cloudrepoUsername").get()
                password = providers.gradleProperty("cloudrepoToken").get()
            }
        }
        mavenCentral()
    }
}

Publish Your Artifacts

Deploy artifacts with standard Gradle commands. Works with CI/CD pipelines. A version ending in -SNAPSHOT can be published again and again; a release version is published once.

Terminal

# Publish the project
./gradlew publish

# Publish a 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. We include a generous transfer allowance, and support is included free.
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. A CloudRepo repository with Overwrite Protection turned off works as a Gradle remote build cache through Gradle's built-in HttpBuildCache: CI uploads task outputs and other machines restore those tasks from the cache. The Gradle build cache page (/gradle-build-cache) shows the setup.
How do SNAPSHOT versions work in CloudRepo?: CloudRepo provides full SNAPSHOT support. A group of hosted repositories merges maven-metadata.xml across its members automatically. Your CI/CD pipeline can publish SNAPSHOTs continuously. On a Maven repository, the Snapshot Cleanup setting is where you choose how many builds to keep for each snapshot version.
What's included in CloudRepo's free support?: All CloudRepo plans include direct access to our engineering team, with responses within one business day. We believe good support should be standard, not a luxury.

Why JVM teams choose CloudRepo

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