2 ecosystems | one binary
Cache and host artifacts across ecosystems.
peryx is an MIT-licensed artifact service. It caches upstream indexes, stores published artifacts, and composes both through virtual indexes. Configuration selects ecosystem owners and availability mode.
$ peryx serve
peryx listening on 127.0.0.1:4433 · 6 indexes
$ curl http://127.0.0.1:4433/+status
Healthy · 6 indexes · 18 cached artifacts1binary, no database or broker
MITopen source, no seat tax
100%line & function coverage
2ecosystems: set me up
- Read-through cache. A miss streams verified bytes from an upstream while committing them to the content-addressed store. Concurrent misses share one transfer.
- Private artifacts. Hosted indexes accept writes through their ecosystem owner. Virtual indexes resolve an ordered list of cached and hosted members.
- One binary. Configuration selects each index owner and the availability mode at startup. The executable has no architecture-changing runtime flags.
- Configured composition. Each index names a registered ecosystem owner. The owner validates its settings and installs its supported capabilities.
- Bounded freshness. Upstream cache directives set freshness within operator limits. Stored data can remain available for a configured stale window during an outage.
- Availability choice.
availability.mode = "none"starts no distributed tasks, listeners, timers, or watchers. Distributed modes add replication, placement, and lifecycle services through neutral contracts. - Verification. CI checks documentation, supported platforms, client behavior, and complete source coverage.
Documentation
Core
Install, configure, and operate peryx. Core covers shared CLI, index, TLS, logging, monitoring, and web UI contracts.
PyPI
How PyPI maps to cached, hosted, and virtual indexes, the Simple API, and pip, uv, and twine configuration.
OCI
OCI index roles, the /v2/ distribution protocol, and client configuration.