RenoP

RenoP is a lightweight, rapidly deployable self-hosted Maven server for individuals and teams.

If you intend to use it for public hosting, RenoP currently does not support that.

Features

• Hosted release, snapshot, and private repositories
• Maven mirror proxying with local caching and negative caching
• Browser, upload, user, token, and repository management in the web UI
• Local disk or S3-compatible object storage
• Repository permissions, Basic authentication, and upload tokens
• Embedded Javadoc browsing, checksums, health data, and runtime statistics

Quick start

Download a release archive, extract it, and run renop.exe on Windows or ./renop on Unix-like systems. RenoP listens on 0.0.0.0:3000 by default.

On first start, RenoP creates an admin account. Set its password before starting the server:

RENOP_DEFAULT_ADMIN_PASSWORD='replace-this-password' ./renop

If the variable is not set, a random password is printed to the server log. Open http://localhost:3000 after startup.

The default repository endpoints are:

http://localhost:3000/releases
http://localhost:3000/snapshots
http://localhost:3000/private

Use one of these URLs in Maven's <repositories> or <distributionManagement> configuration.

HTTP API reference (auth, tokens, Maven helpers, settings, updater, storage paths) lives under docs/api/. OpenAPI 3: openapi.yaml.

Configuration

RenoP creates its configuration and state files in the working directory. Their paths can be overridden with environment variables.

Variable	Default	Purpose
RENOP_CONFIG	config.yaml	Server, frontend, and storage settings
RENOP_REPOSITORIES	repositories.yaml	Repositories, mirrors, and per-repository S3 settings
RENOP_TOKENS	tokens.yaml	Accounts and access tokens
RENOP_INDEX	index.json	Persisted artifact index
RENOP_SESSIONS	sessions.json	Persisted login sessions
RENOP_DEFAULT_ADMIN_PASSWORD	generated	Password used when the first admin account is created

Most settings can also be changed from the management UI. Restart the server after changing listener or TLS settings.

Building

Building from source requires Go, PowerShell 7, and Node.js (for the frontend Rolldown bundle).

pwsh ./build.ps1                 # full target matrix, packaged in dist/
pwsh ./build.ps1 s               # Linux amd64/arm64 and Windows amd64
pwsh ./build.ps1 c               # current platform only
pwsh ./build.ps1 c nb            # current platform, no archive
pwsh ./build.ps1 -Version v1.2.3 -Development false

The nb suffix writes binaries directly to the directory where the script was started and skips ZIP and manifest generation. Full Git hashes are shortened to seven characters in archive names; the binary and manifest keep the full hash.

The build script first generates Protocol Buffer code, then runs pnpm run build in frontend/renop-html (protobuf static modules + Rolldown for JS, lightningcss for CSS into frontend/renop-html/dist), then embeds those assets and builds with CGO_ENABLED=0, restoring the previous CGO setting afterward. It does not change GOCACHE, GOMODCACHE, GOMODULE, or any Go module path.

Protobuf (partial API transport): schemas live under proto/api/v1/. At compile time:

• Go: protoc + protoc-gen-go → pb/api.pb.go (requires protoc on PATH)
• Frontend: pbjs (protobufjs-cli) → frontend/renop-html/js/proto/api.js

Selected UI APIs use application/x-protobuf instead of JSON (status, auth login/me, tokens list, maven repositories/details). Other endpoints remain JSON.

To rebuild only the frontend (or before a plain go build / go test):

# regenerate Go pb code (from repo root)
protoc -I proto --go_out=. --go_opt=module=renop proto/api/v1/api.proto
# or: go generate ./pb

cd frontend/renop-html
pnpm install --frozen-lockfile   # or: pnpm install
pnpm run build
# or from repo root:
go generate ./frontend

Run the test suite with go test ./... (after the frontend dist has been generated).

Price and Contribution

RenoP is completely free for all users, whether individuals, teams, or businesses and non-profit organizations of any size.

RenoP guarantees no hidden data collection, no ads, no annoying pop-ups, no messy subscription tiers...

RenoP only has this one free community edition. If you'd like to contribute to RenoP, you can consider:

• Helping us find issues (submit valid Issues)
• Helping us fix issues (submit valid PRs)
• Helping us solve issues (support us via Patreon)
• Giving us motivation to solve issues (give us a Star)

If you want to maintain your own fork, you need to consider the following:

• Whether you can maintain it long-term
• Whether you can maintain a reasonable level of stability

Please be responsible for your own code, and also responsible for the community. Don't create a fork based solely on impulse or a fleeting interest.

A better choice is to open an Issue or submit a PR — we do our best to listen to everyone's voice.

Credits

RenoP was developed with Reposilite as a reference for a small, self-hosted Maven repository.

The project is built on:

• Fiber, Sonic, and go-yaml
• BigCache, fsnotify, ants, and gopsutil
• MinIO Go SDK for S3-compatible storage
• Feather for interface icons
• google/uuid, x/crypto, and x/time
• pb and unsafeConvert
• Testify for tests

These projects remain under their respective licenses.

License

RenoP is licensed under the Mozilla Public License 2.0 and is marked as incompatible with secondary licenses.