Built for Clojure teams

Private Repository for Clojure deps.edn

Host private Clojure libraries for deps.edn and tools.build, next to the public ones you pull from Clojars. Simple, published pricing.

Native deps.edn and tools.build support

Works with Clojars for public dependencies

Start free trial Compare with Clojars

14 days free. No credit card required.

deps.edn

{:deps {
  com.acme/secret-sauce {:mvn/version "2.1.0"}
  com.acme/data-pipeline {:mvn/version "1.5.3"}}

 :mvn/repos {
  "cloudrepo" {:url "https://your-org.mycloudrepo.io/repositories/your-repo"}
  "clojars" {:url "https://repo.clojars.org/"}}}

View Complete Clojure Documentation

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

Built for modern Clojure development

Everything you need for deps.edn, tools.build, and modern Clojure workflows

Native deps.edn Support: First-class support for Clojure's tools.deps with Maven repository format. Works seamlessly with deps.edn and tools.build.
Monorepo Excellence: Perfect for Clojure monorepos with local deps. Share libraries across projects without publishing to Clojars.
Clojars Compatible: Use Clojars for public dependencies and CloudRepo for your private libraries.
tools.build Integration: Full support for modern Clojure build tooling. Deploy JARs directly with tools.build and deps-deploy.
Enterprise Security: API tokens for CI/CD and team-based access controls for compliance requirements.

Quick Clojure Setup Guide

Configure deps.edn and start using private libraries in minutes

Configure deps.edn for CloudRepo

Add CloudRepo as a Maven repository in your deps.edn configuration for private dependencies. The key, "cloudrepo", must be the server id in step 2.

deps.edn

{:deps {
  ;; Your private Clojure libraries
  com.mycompany/private-lib {:mvn/version "1.2.3"}
  com.mycompany/internal-api {:mvn/version "2.0.1"}}

 :mvn/repos {
  "cloudrepo" {:url "https://your-org.mycloudrepo.io/repositories/your-repo"}
  "central" {:url "https://repo1.maven.org/maven2/"}
  "clojars" {:url "https://repo.clojars.org/"}}}

Set Authentication in settings.xml

tools.deps looks for a server in ~/.m2/settings.xml whose id is the repository key in deps.edn. The username is your email address and the password is a repository token, read from an environment variable so the file never holds it.

~/.m2/settings.xml

<settings>
  <servers>
    <server>
      <id>cloudrepo</id>
      <username>you@example.com</username>
      <password>${env.CLOUDREPO_TOKEN}</password>
    </server>
  </servers>
</settings>

.github/workflows/build.yml

env:
  CLOUDREPO_TOKEN: ${{ secrets.CLOUDREPO_TOKEN }}

Deploy with deps-deploy

Build your jar and pom with tools.build, then publish with deps-deploy. Its login comes from two environment variables set on that one command, not from settings.xml; CLOUDREPO_USERNAME is your email address and CLOUDREPO_TOKEN is your repository token.

deps.edn

:aliases
{:deploy {:replace-deps {slipset/deps-deploy {:mvn/version "0.2.5"}}
          :exec-fn deps-deploy.deps-deploy/deploy
          :exec-args {:installer :remote
                      :artifact "target/my-lib-1.0.0.jar"
                      :sign-releases? false
                      :repository {"cloudrepo" {:url "https://your-org.mycloudrepo.io/repositories/your-repo"}}}}}

Terminal

# Set the two variables on this one command. Exported, they would be sent
# to Clojars the next time you deploy there.
CLOJARS_USERNAME="$CLOUDREPO_USERNAME" CLOJARS_PASSWORD="$CLOUDREPO_TOKEN" clojure -X:deploy

Need advanced configuration?

Check out our comprehensive Clojure deps.edn documentation for monorepos, CI/CD integration, and more.

View Complete Documentation

Perfect for every Clojure use case

From startups to enterprises, CloudRepo scales with your Clojure projects

Enterprise Clojure Teams

Share proprietary Clojure libraries across teams and projects with team-based access control.

Clojure Consultancies

Host client-specific libraries securely. Create separate repositories for each client with isolated access.

Financial Services

Deploy trading algorithms and risk models as private Clojure libraries with access controls and security features.

SaaS Platforms

Manage microservices and shared libraries in a Clojure monorepo with seamless dependency management.

Frequently asked questions

Everything you need to know about CloudRepo for Clojure

Why use CloudRepo instead of Clojars for private Clojure libraries?: Clojars is excellent for open-source Clojure libraries but doesn't support private repositories. CloudRepo provides private repository hosting with access controls and team management. You can use both together - Clojars for public dependencies and CloudRepo for private ones.
How does CloudRepo compare to self-hosting a Maven repository?: Self-hosting means you maintain the server, its updates, backups and scaling. CloudRepo runs it for you, with automatic backups.
Can I use CloudRepo with both deps.edn and Leiningen?: Yes! CloudRepo is a standard Maven repository that works with all Clojure build tools - deps.edn/tools.deps, Leiningen, and Boot. You can even mix tools across different projects while sharing the same private repository.
How does CloudRepo handle Clojure monorepos with local deps?: CloudRepo excels at monorepo support. You can publish internal libraries from your monorepo to CloudRepo and reference them as Maven dependencies in other projects. This works seamlessly with deps.edn's local/root dependencies for development and Maven dependencies for production.
What's the migration path from JFrog Artifactory?: CloudRepo uses the same Maven repository format. Export your artifacts from Artifactory, upload them to CloudRepo, and update the repository URLs in deps.edn and your credentials in settings.xml.
Does CloudRepo support SNAPSHOT versions for Clojure libraries?: Yes, CloudRepo fully supports SNAPSHOT versions. Perfect for continuous integration where you want to publish development builds. On a Maven repository, the Snapshot Cleanup setting is where you choose how many builds to keep for each snapshot version.

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 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

Lead Architect, Dreev

The Modern Clojure Ecosystem Choice

deps.edn is the future of Clojure dependency management

Why deps.edn?

Official Clojure tooling by Cognitect
Simpler, more predictable than Leiningen
Built-in support for git dependencies
Excellent monorepo support with local deps

CloudRepo + Clojars

CloudRepo for private libraries
Clojars for open source dependencies
Seamless integration in deps.edn
Best of both worlds approach

Example: Using Both CloudRepo and Clojars

deps.edn

{:deps {
  ;; Public dependencies from Clojars
  metosin/reitit {:mvn/version "0.5.18"}
  com.taoensso/timbre {:mvn/version "5.2.1"}

  ;; Private dependencies from CloudRepo
  com.acme/auth-service {:mvn/version "2.1.0"}
  com.acme/data-models {:mvn/version "3.0.2"}}

 :mvn/repos {
  "cloudrepo" {:url "https://your-org.mycloudrepo.io/repositories/your-repo"}
  "central" {:url "https://repo1.maven.org/maven2/"}
  "clojars" {:url "https://repo.clojars.org/"}}}

CloudRepo Supports All Clojure Build Tools

Whether you prefer deps.edn or Leiningen, CloudRepo has you covered.

ClojureScript

Full support for ClojureScript artifacts. Host your CLJS libraries alongside your Clojure code.

View documentation →

Multi-Language Projects

Mix JVM and Python artifacts in one account. Perfect for polyglot teams.

See unified pricing →

All JVM build tools use CloudRepo's Maven repository format. See our documentation for detailed configuration guides.

Start hosting private Clojure libraries today

14 days free. No credit card required. Setup in 5 minutes.

Native deps.edn support

Works with Clojars

Start free trial View documentation

Additional Resources

Clojure deps.edn Documentation Transparent Pricing Free Support Included Talk to us

Private Repository for Clojure deps.edn

Included on every plan

Built for modern Clojure development

Quick Clojure Setup Guide

Configure deps.edn for CloudRepo

Set Authentication in settings.xml

Deploy with deps-deploy

Perfect for every Clojure use case

Enterprise Clojure Teams

Clojure Consultancies

Financial Services

SaaS Platforms

Frequently asked questions

Why JVM teams choose CloudRepo

The Modern Clojure Ecosystem Choice

Why deps.edn?

CloudRepo + Clojars

Example: Using Both CloudRepo and Clojars

CloudRepo Supports All Clojure Build Tools

Leiningen

Maven

Gradle

SBT (Scala)

ClojureScript

Multi-Language Projects

Start hosting private Clojure libraries today

Additional Resources

Java/JVM Tools

Python Tools

JavaScript Tools

Containers & OCI

Resources

Security

Compare

Company