Capability matrix
velodex is a (role × ecosystem) server: every index is one of three roles paired with
an ecosystem. This page is the coverage map. ✓ means shipping today; planned
means the architecture reserves it but no driver is built yet.
Roles per ecosystem
| Role | PyPI | OCI | npm |
|---|---|---|---|
| cached (proxy) | ✓ | planned | planned |
| hosted (uploads) | ✓ | planned | planned |
| virtual (layers) | ✓ | planned | planned |
Features per ecosystem
| Feature | PyPI | OCI | npm |
|---|---|---|---|
| Read-through caching with streaming | ✓ | planned | planned |
| Content-addressed artifact store | ✓ | planned | planned |
| Shadowing / virtual resolve | ✓ | planned | planned |
| Publish / upload API | ✓ | planned | planned |
| Yank and delete | ✓ | planned | planned |
| Metadata fast path (PEP 658/714) | ✓ | n/a | n/a |
velodex mirror sync + offline | ✓ | planned | planned |
| Policy filters (allow/deny, versions, size) | ✓ | planned | planned |
| Signed webhooks | ✓ | planned | planned |
| Web UI, search, archive inspection | ✓ | planned | planned |
Rows marked n/a are PyPI-specific protocol features that do not translate to another ecosystem; the OCI and npm
columns will grow their own equivalents. Cross-cutting subsystems (metrics, rate limits, logging, backup/restore) are
ecosystem-neutral and apply to every index regardless of role or ecosystem.
Related
- What the roles mean: the index model
- Per-ecosystem setup: ecosystems
- The terms in one place: glossary