Skip to content

Maven hosting without the enterprise price tag

Private Maven and Gradle repositories that drop into your existing build and keep it running when Maven Central rate limits you.

Free for up to 5 GB, with no time limit. See all plans

What a year costs

At 250 GB of storage and 1 million requests a month

  1. JFrog Artifactory Enterprise X282× more expensive$27,897
  2. Cloudsmith Pro240× more expensive$23,748
  3. JFrog Artifactory Pro197× more expensive$19,497
  4. Sonatype Nexus Repository Cloud177× more expensive$17,520
  5. Packagecloud Pro110× more expensive$10,896
  6. GitHub Packages367× more expensive$6,632
  7. CloudRepo Team60× more expensive$5,988
  8. Azure Artifacts21× more expensive$2,069
  9. Google Cloud Artifact Registry216× more expensive$1,618
  10. AWS CodeArtifact113× more expensive$1,283
  11. Artifex Pro$99
Storage and requests

List prices published September 26, 2026, in US dollars, before tax. Transfer is priced as leaving the provider's network. 1 us-east-1, without the account-wide 100 GB of free transfer. 2 us-central1. 3 Team plan, without its per-user price.

Switch tonight, ship tomorrow

Three steps, and no servers of your own to run.

  1. 1

    Create a repository

    Name it, choose who can read it, and you get an address your builds can use.

  2. 2

    Point your build at it

    When Maven Central or a mirror fails, your build still gets a verified copy.

  3. 3

    Publish

    Deploy from Gradle or Maven. Every version is kept, with who published it and when.

Already on Artifactory or Nexus?

Add your current repository as an upstream, with its own sign-in. Artifex serves your existing packages alongside new ones, so you can move one build at a time. Or paste the Set up with AI prompt into your coding agent and let it configure the build.

Works with the tools you have

Gradle and Maven builds, including Gradle Module Metadata and signatures from the Gradle signing and Maven GPG plugins. The Maven index shows your packages in IntelliJ IDEA, Eclipse, and NetBeans.

Built for the bad days

Every file your builds fetch through Artifex is kept, so the build that worked yesterday works today, whatever happens upstream.

  • Maven Central goes down

    Your builds still resolve everything they've fetched before, from the copy Artifex kept.

  • A version is removed

    Artifex's copy stays, so nothing your builds depend on disappears.

  • A file is corrupted

    If it doesn't match its published checksum, it's refused and never handed to your build.

  • Someone republishes a release

    Refused. A release's files never change, unless you allow it for that repository.

No surprise bills

Go over a limit on Free or Plus and the extra is refused, never charged. Pro only charges for extra usage if you turn it on.

Plans compared

Free

For trying it out

$0 forever

Start free

Plus

For a small team

$19 a year

Choose Plus

Pro

For a whole company

$99 a year

Choose Pro
Storage5 GB25 GB250 GB
Requests a month20,000100,0001,000,000
Custom domainsNone15
Extra usageNoneNone$0.02 per GB, $5 per million requests

Every plan includes

  • Unlimited repositories and upstreams
  • Private and public repositories
  • Advanced upstream rules
  • Snapshot publishing
  • Activity log
  • Maven index

Prices are in US dollars, billed yearly. Tax is added at checkout where it applies.

Questions

Anything not answered here is in the documentation.

What counts as a request?
Every file your repositories serve or accept. Requests refused for lack of access don't count.
What happens when I reach a limit?
On Free and Plus, further requests are refused until the month ends, and a deployment that needs more storage is refused. On Pro you can turn on extra usage for $5 per further million requests and $0.02 per further GB a month, with a monthly cap.
Can I use my own domain?
Yes: one domain on Plus, and five on Pro, then $2 a year for each extra one. Your builds can use an address like maven.yourcompany.com instead of artifex.soh.gg.
Can I move my packages out again?
Yes. Repositories use the standard Maven layout, so any Maven or Gradle tool can download everything in them. Everything you can do on the site you can also do through the API.
Can a published release change?
No. Publishing a file that already exists is refused, and so is deleting one, so a release's files are the same every time a build requests them. For a scratch repository, an admin can allow replacing or deleting files, and every change is recorded in its activity.
What else is included?
Rules for which upstream serves each group, snapshot publishing, a browser for POM and Gradle module details, an activity log of who published what and when, usage analytics, and a Maven index so that your IDE can find your artifacts.

Give your next build a repository

Create a free repository