BatleHubYour package hub. Proxy, cache, and host.

Sit between your build tools and the internet. Cache artifacts, enforce access control, and publish private packages — all from one self-hosted server.

Get Started

View on Git

⚡

Cache what you already pull

Every artifact is fetched from upstream once and served from disk or S3 after that. Twenty-one ecosystems, one server, no change to how your build tools are invoked.

How caching works

🔒

Publish what is yours

Private npm packages, Cargo crates, Go modules, Python wheels, NuGet packages and more — on the same server, in the same URL space, published with the tool you already use.

Publishing guide

🛡️

Decide who gets what

Per-registry permissions for anonymous, user and admin roles, groups from OIDC or CI tokens, and gates on what may be pulled at all — by age, by advisory, by licence.

Access control

BatleHub proxies, caches and privately hosts 21 registry types — from npm and Cargo to Debian, Terraform and the VS Code marketplace. See the Registries reference for the feature matrix and a setup page for each one, or the full feature list for everything the server does.