Files stay put.
Pinned artifacts are retained by content hash. A cached package keeps its bytes, even if the upstream later changes.
Package delivery, by Elide
An accelerated package proxy for the tools you already use. Immutable files, cached close to your builds.
Public packages. Standard protocols. No account required.
01 / GET CONNECTED
Choose your ecosystem. These examples use public packages and leave your existing workflow in place.
Endpointnpm.pkg.st
npm install react --registry=https://npm.pkg.st --no-auditpnpm add react --registry=https://npm.pkg.stYARN_NPM_REGISTRY_SERVER=https://npm.pkg.st yarn add reactUse your own package name. npm audit requests are not proxied; the npm example disables audit for this install.
Endpointpypi.pkg.st
python -m pip install --index-url https://pypi.pkg.st/simple/ requestsuv add --default-index https://pypi.pkg.st/simple/ requestsUse pip in an active virtual environment, or run uv in your project. Both use the standard Python package index protocol.
Endpointmaven.pkg.st
<mirrors>
<mirror>
<id>pkgst</id>
<mirrorOf>central</mirrorOf>
<url>https://maven.pkg.st</url>
</mirror>
</mirrors>Merge this mirror into ~/.m2/settings.xml; keep your existing private repositories.
repositories {
maven { url = uri("https://maven.pkg.st") }
}Use this repository in place of mavenCentral(). Gradle Plugin Portal requests have a separate endpoint at gradle.pkg.st.
Endpointgo.pkg.st
GOPROXY=https://go.pkg.st go mod downloadRun from a project with a go.mod. Go keeps its normal checksum verification. Keep GOPRIVATE configured for private modules.
Endpointcrates.pkg.st
[source.crates-io]
replace-with = "pkgst"
[source.pkgst]
registry = "sparse+https://crates.pkg.st/"Merge into your project’s Cargo config, then run cargo build. The trailing slash is required for the sparse index.
Endpointesm.pkg.st
import React from "https://esm.pkg.st/react@19.0.0?target=es2022";https://unpkg.pkg.st/lodash@4.17.21/lodash.min.jshttps://jsdelivr.pkg.st/npm/lodash@4.17.21/lodash.min.jsPin the version and file for immutable delivery. Import esm.sh URLs in a module; use file URLs wherever you would use the upstream CDN.
Already using a private registry? Keep it configured separately. Pkgst serves public upstream packages and does not forward your credentials to those registries.
02 / BUILT FOR REPEAT BUILDS
Package files and package discovery need different treatment. Pkgst gives each the right kind of cache.
Pinned artifacts are retained by content hash. A cached package keeps its bytes, even if the upstream later changes.
Version lists, tags and mutable selectors use short cache lifetimes. Your client keeps making its own dependency decisions.
Use standard package protocols, ETags and byte ranges. Elide can opt into additional digest hints and already-held artifact reuse.
03 / FOR TOOLS & AGENTS
Readable instructions and versioned contracts, available without JavaScript. Start with llms.txt, then use the interface that fits your tool.
Resolve exact versions or the registry’s latest recommendation for npm, PyPI and Maven. Batch results keep their input order, with an error for each item that cannot resolve.
Public lookups need no token. Existing Elide tokens can unlock authorized limits and private preferences.
curl https://api.pkg.st/v1/resolve:batch \
-H 'Content-Type: application/json' \
--data '{"requests":[
{"platform":"npm","name":"react","version":"19.0.0"},
{"platform":"pypi","name":"requests","version":"latest"}
]}'THE REST IS IN THE DOCS
Explore Elide, package workflows and integration guides. Agents can start with the documentation index, use the documentation APIs, or connect through the Elide Docs MCP server.