Private SBT Repository Hosting for Scala Teams
Maven repository hosting with perfect SBT integration. Support for cross-compilation, Scala.js, and Scala Native. Simple, published pricing vs JFrog Artifactory.
14 days free. No credit card required.
publishTo := Some("CloudRepo" at "https://your-org.mycloudrepo.io/repositories/your-repo")
credentials += Credentials(
"your-org.mycloudrepo.io",
"your-org.mycloudrepo.io",
sys.env("CLOUDREPO_USERNAME"),
sys.env("CLOUDREPO_TOKEN")
)
// Perfect cross-compilation support
crossScalaVersions := Seq("2.13.12", "3.3.1")
// Then run "sbt +publish" to publish for all Scala versionsIncluded on every plan
Plans differ only in storage and transfer allowance.
- SSO (SAML, OIDC)
- Multi-factor authentication (MFA)
- Audit log
- Repository tokens
- Unlimited users, no per-seat pricing
- Human support
- Maven, npm, Python, Docker with Helm charts, and plain files
- Proxy repositories
- SCIM
Coming soon: Access log
Looking for a Bintray Replacement?
Need a home for your Scala artifacts after Bintray? CloudRepo hosts them in Maven format, with no vendor lock-in.
Every plan includes human support and SSO. See pricing
Built for Modern Scala Development
Everything you need for SBT builds and Scala projects
- Scala Cross-Compilation
- Perfect support for cross-building across Scala 2.12, 2.13, and Scala 3. Manage all your cross-compiled artifacts in one place.
- Maven Repository Format
- SBT uses standard Maven repositories. CloudRepo provides Maven hosting with perfect SBT compatibility.
- Multi-Project Builds
- Ideal for complex SBT projects with submodules. Share internal libraries across your Scala microservices and applications.
- Scala.js & Scala Native
- Full support for Scala.js and Scala Native artifacts. Build once, deploy everywhere - JVM, browser, and native.
- Enterprise Security
- API tokens for CI/CD and team-based access controls for enterprise Scala teams.
Supporting the Entire Scala Ecosystem
Host artifacts for all major Scala frameworks and libraries
- Akka & Pekko
- Host internal Akka/Pekko modules and custom extensions for your actor systems.
- Play Framework
- Perfect for Play Framework plugins and shared components across services.
- Apache Spark
- Distribute custom Spark libraries and UDFs across your data engineering teams.
- ZIO & Cats Effect
- Share effect system utilities and domain libraries for functional Scala.
- Scala.js Libraries
- Host frontend Scala.js components and share code between frontend and backend.
- ScalaTest & Specs2
- Distribute custom testing utilities and fixtures across your organization.
Quick SBT Setup Guide
Configure your build.sbt in minutes, not hours
Configure build.sbt for Publishing
Add CloudRepo as your private repository for publishing Scala artifacts. sbt sends the credential only when the realm is your repository host, so use the host for both.
publishTo := Some("CloudRepo" at "https://your-org.mycloudrepo.io/repositories/your-repo")
credentials += Credentials(
"your-org.mycloudrepo.io",
"your-org.mycloudrepo.io",
sys.env.getOrElse("CLOUDREPO_USERNAME", ""),
sys.env.getOrElse("CLOUDREPO_TOKEN", "")
)
// Cross-compilation settings
crossScalaVersions := Seq("2.12.18", "2.13.12", "3.3.1")
scalaVersion := "3.3.1"Add CloudRepo as Dependency Source
Configure SBT to resolve private dependencies from your CloudRepo repository.
resolvers += "CloudRepo" at "https://your-org.mycloudrepo.io/repositories/your-repo"
// Dependencies from your private repository
libraryDependencies ++= Seq(
"com.yourcompany" %% "core-library" % "2.1.0",
"com.yourcompany" %% "akka-utils" % "1.5.2",
"org.typelevel" %% "cats-core" % "2.10.0"
)Publish with SBT
Deploy your Scala libraries with standard SBT commands. Perfect for CI/CD integration.
# Publish current version
sbt publish
# Publish all cross-compiled versions
sbt +publish
# Publish specific Scala version
sbt ++2.13.12 publish
# Publish local for testing
sbt publishLocal
# For multi-module projects
sbt "project core" publish
sbt "project api" publish# CI/CD with GitHub Actions. CLOUDREPO_USERNAME is the email address of
# the account that created the repository token.
- name: Publish to CloudRepo
env:
CLOUDREPO_USERNAME: you@example.com
CLOUDREPO_TOKEN: ${{ secrets.CLOUDREPO_TOKEN }}
run: sbt +publishNeed detailed configuration examples?
Check out our comprehensive SBT documentation with cross-compilation, multi-module, and CI/CD examples.
Perfect for Enterprise Scala Teams
From fintech to big data, CloudRepo scales with your needs
Microservices with Akka/Pekko
Share Akka actors, streams utilities, and custom extensions across your microservices. Perfect for event-sourced systems and CQRS architectures.
Apache Spark Libraries
Distribute custom Spark transformations, UDFs, and data pipeline components. Essential for data engineering teams using Databricks or EMR.
Play Framework Applications
Host Play plugins, authentication modules, and shared controllers. Streamline development across multiple Play applications.
Scala.js Frontend Libraries
Share Scala.js components between projects. Perfect for teams building full-stack Scala applications with shared domain models.
Frequently asked questions
Everything you need to know about CloudRepo for SBT
- Is CloudRepo a good replacement for Bintray?
- Yes. CloudRepo uses the same Maven repository format Bintray did, so moving is a new URL in build.sbt. Pricing is simple and published.
- How does CloudRepo handle Scala cross-compilation?
- CloudRepo perfectly supports SBT's cross-compilation features. When you publish with +publish, all your cross-built artifacts (2.12, 2.13, 3.x) are stored and organized correctly. Dependency resolution with %% works seamlessly, automatically selecting the right Scala version.
- Can I host both public and private Scala libraries?
- Yes! You can create multiple repositories with different access levels. Use private repositories for proprietary code and public repositories for open-source libraries. Unlike Sonatype, you don't need complex staging workflows.
- Does CloudRepo support Scala.js and Scala Native?
- Absolutely! CloudRepo fully supports Scala.js and Scala Native artifacts. Your cross-platform Scala projects can share code between JVM, JavaScript, and Native targets, all hosted in the same repository.
- How much can I save compared to JFrog Artifactory?
- Past light usage, CloudRepo costs less. CloudRepo Business costs less than JFrog Pro at list price from 705 GB of storage plus downloads a month. At 2 TB of downloads a month, Business is $999/month billed annually and JFrog Pro is about $2,374 a month, billed monthly (JFrog's pricing page, read 2026-10-06). Our support is included.
- Can I migrate from Sonatype Nexus to CloudRepo?
- Yes, migration is straightforward. Both use Maven repository format, so your existing artifacts can be uploaded to CloudRepo. Your build.sbt files need minimal changes - just update the repository URLs. We provide migration guides and free support.
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.”
“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.”
Easy Migration from Any Repository
Switch to CloudRepo in minutes with our migration guides
From Sonatype
Skip the staging complexity. Direct publishing with simple configuration.
Migration guideStart hosting SBT artifacts today
14 days free. No credit card required. Free migration support.
Enterprise Ready
SSO • Team access controls • Encryption at rest