Documentation overview

Where to start

Start the service and complete first-run setup, then connect one package manager. Check Admin Access logs to confirm requests reached Depsilo; a successful install alone does not prove that.

Quick startRun the pinned Docker image, complete the protected first-run setup, and verify the instance is ready.

Connect package managersRoutes, client configuration, and verification for 14 ecosystems plus Docker OCI.

Find a task

• Do you need a shared cache?Compare local and CI caches, use cases, and maintenance costs.
• Verify cache reuseSeparate request routing from artifact hits and measure your project’s savings.
• ccache and sccacheSet up compiler caching and machine credentials, then verify remote hits.
• Deployment and configurationPersistence, readiness checks, backup, and recovery.
• Supply-chain securityPolicy defaults, denial reasons, and enforcement boundaries.
• TroubleshootingRequests bypassing Depsilo, 451 responses, or upstream failures.
• Set up with AICopy a prompt to read the docs or configure your project with an AI assistant.
• Agents and MCPProject instructions and read-only MCP access.

What is Depsilo?

Depsilo is an open-source, self-hosted dependency proxy and cache. It sits between package managers and upstream registries, caches dependencies, and applies enabled supply-chain policies to requests passing through the instance.

You can keep using your existing package managers, lockfiles, and installation commands. Only the dependency registry or index URL needs to point to Depsilo.

Version and scope

This documentation applies to the stable v0.11.0 release.

Depsilo is currently designed for single-instance deployments used by individual developers, homelabs, and small teams. It stores state in SQLite, while cached content can be stored on a local filesystem or in S3.

Depsilo is not a general-purpose artifact repository and does not provide multi-node high availability.