Holger guards your artifacts at rest.
An immutable artifact repository in pure Rust. Airgap-first, content-addressed, and an order of magnitude faster than the JVM incumbents. Measured, not claimed.
Artifact repositories are stuck in 2010
The incumbents are JVM heavyweights: gigabytes of RAM to serve static files, mutable state under your supply chain, and an airgap story that amounts to 'export a zip and hope'.
Mutable repositories: artifacts can be overwritten, and you find out during an audit
JVM repository managers that need more resources than the services they feed
Airgap transfer as a manual, error-prone export/import ritual
Metadata queries that get slower as the repository grows
Full OS, shell and scripting runtimes in the trusted computing base
Nothing that can run at the edge, next to the device being updated
Immutable, airgap-first, 2 MB light
Immutable by design
Every artifact is content-addressed with BLAKE3 and written in atomic, versioned transactions. What you stored is what you serve: bit for bit, forever.
Airgap-first
Pull from the internet or your existing repository manager on the connected side. Carry one immutable archive across the gap. Serve it on the dark side. That workflow is the product, not an afterthought.
O(1) random access
Any file in an archive is reachable in constant time without unpacking, with Apache Arrow zero-copy metadata throughout.
Zero dependencies
No OS packages, no shell, no Python, no JVM. Even the decompressors were rewritten from C into Rust. One static binary is the whole install.
Embeddable
Roughly 2 MB resident memory. Holger runs on bare-metal, OS-free devices as comfortably as on a 32-core server.
Built for all cores
One all-core engine with zero-copy, multi-core parallel I/O, designed to saturate the hardware it runs on instead of a garbage collector.
Measured against the JVM incumbents
The two most widely deployed JVM-based repository managers, served over HTTP on the same 32-core host and measured identically. Each competitor got every core and ~75% of RAM as heap. No throttled rivals.
| Server | Requests / s | p50 (ms) | p99 (ms) |
|---|---|---|---|
| Holger | 181,863 | 0.15 | 0.46 |
| JVM repository A | 20,578 | 1.10 | 6.11 |
| JVM repository B | 15,832 | 1.40 | 7.96 |
Holger v0.1.0, 32-core host, measured July 2026. Competitors are anonymised here, but the run is not: every number is rendered from the benchmark run itself by our tooling, nothing is typed by hand, and numbers from one host are never compared with another. Full methodology, named configurations and every metric ship with the product documentation, and we will re-run the comparison on your hardware on request.
Built for the places software has to be trusted
Regulated & airgapped environments
Defense, energy, healthcare, industrial OT: anywhere software must cross a gap and be provably untampered on the other side.
Platform teams
Teams tired of feeding a JVM repository manager gigabytes of RAM to serve static files slowly, and of backup stories built on mutable state.
Embedded & edge fleets
A 2 MB-RSS repository that runs on the device itself changes what an update pipeline can look like.
Status: early access
Holger is at v0.1 and moving fast. We're looking for a handful of pilot users with real airgap or artifact-integrity requirements. You get direct access to the team that wrote every line, and your constraints shape the roadmap.
Talk to us about a pilot
Tell us about your environment, connected, airgapped or embedded, and we'll show you Holger running on it.