Overview
Modern software delivery no longer runs at human speed. CI/CD pipelines, Kubernetes clusters, build farms, AI agents, and GPU workloads pull dependencies, containers, source, and model assets continuously. Every install, container pull, and dependency update adds latency, saturates backends, and runs up cloud egress. The more concurrency and the larger the artifacts, the more pressure lands on the registries underneath. The usual answer is to scale the infrastructure beneath the traffic: a bigger Artifactory or Nexus, more backend capacity, more egress. Yet every pull still hits the backend. Latency, egress, and spend keep rising with demand.
Varnish Virtual Registry takes a different position. It sits in front of the registries you already run as a single, vendor-neutral access layer. Acceleration happens at the point of consumption: a cache lookup, a single upstream fetch, and repeated pulls served without touching the origin. Performance scales without the systems behind it. Control and resilience stay with you, not your repository vendor. It caches container layers, package files, binaries, Git LFS objects, and AI model artifacts, while revalidation keeps metadata, manifests, and indexes fresh. Private artifact traffic is accelerated without bypassing registry security: requests are validated against upstream authentication, and approved users share cached private artifacts. Varnish Virtual Registry does not bypass registry authentication, entitlements, or metering - it reduces the number of redundant requests your registry is asked to serve. In production, teams have seen 90%+ reductions in backend repository traffic, 50%+ lower server load, and 40%+ faster dependency resolution. The result is faster builds, lower cloud egress, and less backend infrastructure to scale. Deployed alongside Varnish Artifact Firewall, the same access layer can also enforce package policy at request time.
Virtual Registry works in front of JFrog Artifactory, Sonatype Nexus, Cloudsmith, GitHub Packages, GitLab Package Registry, Docker Hub, npm Registry, PyPI, Maven Central, Amazon ECR, Google Artifact Registry, Azure Container Registry, and S3-backed artifact stores, and it accelerates Docker/OCI images, Helm charts, npm, PyPI, Maven, NuGet, Cargo, Go modules, Ansible, Conan, Debian, RPM, Git, Git LFS, and other HTTP-delivered immutable assets.
This listing is the Core tier of Varnish Virtual Registry, designed for single-location deployments. It includes the complete caching, routing, and observability feature set, and covers 450 TB of delivered traffic per year in one location. The Core tier does not include cache clustering or failover between locations; both are available in the Pro and Enterprise tiers, along with additional locations, higher traffic entitlements, and Standard or Premium Support. To find the right fit for your workload, contact sales@varnish-software.com .
What counts as a location. A location is one place you run Virtual Registry to serve artifacts - an AWS region, another cloud region, a data centre, or a site. Run as many nodes in it as you need: node count is not limited and is not counted. Your Kubernetes and container clusters are not locations and are never counted separately. Additional locations are available in the Pro and Enterprise tiers, each bringing its own traffic entitlement.
How delivered traffic is measured. Delivered traffic is the volume of data Virtual Registry serves to your clients, measured on a trailing twelve months. Uploads, transfers between your own locations, and stored data are not counted, and there is no storage limit. Exceeding the entitlement does not interrupt or throttle service: it is reviewed at renewal and never billed retrospectively.
Highlights
- Accelerate the platform: Serve repeated artifact pulls from cache instead of the backend: request coalescing turns thousands of concurrent pulls into a single upstream fetch, persistent caching keeps frequently used artifacts close to your builds, and cached artifacts keep serving through registry slowdowns, outages, and migrations. Teams report 90%+ reductions in backend repository traffic and 40%+ faster dependency resolution.
- Vendor-neutral by design: Varnish Virtual Registry presents your repositories, registries, object stores, and cloud artifact services through one logical endpoint, with no lock-in to a backend platform and no changes to developer workflow. Requests are validated against upstream authentication before serving, so private artifacts are accelerated without bypassing registry security.
- Core tier, deployed in minutes: Point your package managers and clients at a Virtual Registry endpoint and it does the rest. Deploy as a Docker image, Helm chart, or Linux package, and monitor hit rate, latency, and backend load through OpenTelemetry logs, metrics, and traces. The Core tier covers one location and 450 TB of delivered traffic per year, with as many nodes in that location as you need. Cache clustering, failover, and Premium Support are available in the Pro and Enterprise tiers.
Details
Features and programs
Financing for AWS Marketplace purchases
Pricing
Dimension | Description | Cost/12 months |
|---|---|---|
Varnish Virtual Registry Core | This is the Core package, for single-location deployments, which includes 450 TB of delivered traffic per year and unlimited nodes in that location. Pro and Enterprise tiers add cache clustering and failover, additional locations, higher delivery entitlements, and enhanced support. Please reach out to sales@varnish-software.com for more information and pricing. | $30,000.00 |
Dimensions summary
Top-of-mind questions for buyers
Vendor refund policy
All fees are non-cancellable and non-refundable except as required by law.
How can we make this page better?
Legal
Vendor terms and conditions
Content disclaimer
Delivery details
Software as a Service (SaaS)
SaaS delivers cloud-based software applications directly to customers over the internet. You can access these applications through a subscription model. You will pay recurring monthly usage fees through your AWS bill, while AWS handles deployment and infrastructure management, ensuring scalability, reliability, and seamless integration with other AWS services.
Resources
Support
Vendor support
Varnish Virtual Registry Core includes email support. Varnish Virtual Registry Pro includes Standard Support: business-hours coverage by email, with telephone support for critical issues, and access to the Varnish knowledgebase and software repositories. Premium Support, with 24/7/365 availability, unlimited support requests, faster response times, and guaranteed SLAs for critical issues, is available as an add-on to Pro or as part of the Enterprise tier. Support reviews and on-site consultancy are available as paid options.
AWS infrastructure support
AWS Support is a one-on-one, fast-response support channel that is staffed 24x7x365 with experienced and technical support engineers. The service helps customers of all sizes and technical abilities to successfully utilize the products and features provided by Amazon Web Services.