cacheport

Security

A cache you can put in front of production builds

Cacheport sits in your supply chain, so it is built to change nothing it serves and to record everything it does.

Encryption in transit

Every endpoint uses TLS 1.2 or 1.3 with modern ciphers and HSTS. The only plain HTTP endpoints are for apt, where signatures are verified by the client and access is limited to IP ranges you allow.

Encryption at rest

Cached artifacts, pull logs and backups are encrypted at rest with AES-256. Keys are managed in a dedicated key management service and rotated regularly.

Artifact integrity

Artifacts are stored and served byte for byte. If an upstream ever serves different bytes for a version we already hold, the pull is flagged and the original is kept.

Tokens and access

Tokens are scoped by service and permission, can expire, and are stored as salted hashes. OIDC lets CI jobs authenticate without long-lived secrets. SAML SSO and SCIM are available on Business and Enterprise.

Isolation

Each workspace has its own storage namespace. Private upstream credentials are encrypted separately and never exposed in responses or logs.

Audit logging

Every pull, token change, policy change and purge is logged with actor, time and outcome. Logs can be exported to S3 or streamed to a SIEM.

Data residency

A workspace is stored in the region you choose. We do not replicate it to other regions unless you add them.

Responsible disclosure

Report vulnerabilities to security@cacheport.cc. We acknowledge reports within two business days, keep you informed while we fix them and credit you if you wish.

Reporting a vulnerability

Email security@cacheport.cc. Our security.txt lists the current contact and policy. Please give us reasonable time to fix an issue before disclosing it, and do not access data that is not yours.

Start on the free plan

20 GB of cache, every registry, unlimited users. Upgrade when your pipelines outgrow it.