Skip to content
Ravenstash
Create account

Private Maven Repository for Java, Kotlin, and Scala

Ravenstash gives Java, Kotlin, Scala, and broader JVM teams private release and snapshot repositories with Maven-compatible metadata and authenticated artifact delivery.

A private Maven repository that stays close to your tools

Ravenstash is built to make private package publishing feel familiar for developers and manageable for teams.

Resolve with Mavenbash
rvs art select platform/packages
rvs mvn verify
Deploy with Mavenbash
rvs art select platform/packages
rvs mvn deploy

Works with your Maven tools

Tools marked Ravenstash CLI sign in for you: run them through the CLI and keep using the same commands. Other tools work with a short setup that adds your repository address and a short-lived token.

  • Maven: Ravenstash CLI
  • Gradle: Manual setup
  • sbt: Manual setup

About the Ravenstash CLI → Set up a tool manually →

Maven-native publish and install

Run Maven and Gradle through rvs without moving developers away from familiar JVM builds.

Maven builds keep working

Ravenstash provides the repository files Maven builds expect, including metadata, artifacts, and checksums, so dependency resolution stays familiar.

Protected public dependencies

Use approved Maven Central dependencies through a private mirror with security scanning, minimum package age, and faster repeat builds.

Private mirror

Use Maven Central through a private mirror

Give developers and CI one authenticated path to public Maven dependencies, with security scanning and minimum package age. Install from the mirror directly or connect it to a private Maven repository.

Learn about private mirrors →
Build with the Maven Central mirrorbash
rvs art mirror select maven-central
rvs mvn verify

Maven questions

Does Ravenstash support Maven snapshots and releases?

Yes. Ravenstash supports release and snapshot-style Maven publishing and the repository files Maven builds expect.

Is Ravenstash a public Maven Central mirror?

No. Ravenstash provides authenticated private mirrors for controlled team builds, not an anonymous public mirror.

Can teams manage shared Maven credentials?

Yes. Organization admins can create shared repositories and automation tokens for CI without tying builds to one developer's account.

Publish your first private Maven package.

Create an account, select a repository with rvs, and keep using the tools you already know.