Ravenstash
Create account
Java and JVM artifacts

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.

Create accountRead quickstarts
Add a Maven repositoryxml
<repository>
  <id>ravenstash</id>
  <url>https://rvnsta.sh/maven/x/acme/jvm/</url>
</repository>
Deploy with Mavenbash
mvn deploy \
  -DaltDeploymentRepository=ravenstash::default::https://push.rvnsta.sh/native/maven/x/acme/jvm/
Workflows

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.

Maven-native publish and install

Use Maven repository URLs in Java, Kotlin, Scala, and JVM builds without moving developers away from Maven.

Maven builds keep working

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

Controlled Maven Central fallback

Let Maven builds use approved Maven Central packages through your private repository while Ravenstash caches repeat downloads.

Setup

Copyable Maven examples

These examples use placeholder customer and repository names. Replace them with your Ravenstash customer and repository public IDs.

Add a Maven repositoryxml
<repository>
  <id>ravenstash</id>
  <url>https://rvnsta.sh/maven/x/acme/jvm/</url>
</repository>
Deploy with Mavenbash
mvn deploy \
  -DaltDeploymentRepository=ravenstash::default::https://push.rvnsta.sh/native/maven/x/acme/jvm/
Token in settings.xmlxml
<server>
  <id>ravenstash</id>
  <username>token</username>
  <password>${env.RAVENSTASH_TOKEN}</password>
</server>
FAQ

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 keeps upstream fallback behind your private repository. It is built for controlled team builds, not an anonymous public mirror.

Can teams manage shared Maven credentials?

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