Scarf Gateway
Advanced download metrics for your open-source software, anywhere on the internet.
Gain insight and freedom of choice.
Advanced analytics
Track installs by company, location, platform, versions, cloud providers, container runtimes, referral source - and anything else
Privacy focused
Fully GDPR compliant out of the box. Scarf ensures all personally identifiable information is discarded so you'll never have to touch anything sensitive
Customizable
Custom domain support for container hosting prevents vendor lock-in , even to Scarf itself
All your artifacts in one place
A static URL frees you to manage your own distribution strategy
Eliminate lock-in
Switch registries and hosts seamlessy with no impact to end users
Distribute anything
Natively supports Docker/OCI containers , Python packages, file downloads , API endpoints, or any URL.
How it works




Frequently asked questions
Everything you need to know about Scarf Gateway
First, create an account on Scarf, if you haven’t already done so. Once you’ve registered, you’ll be prompted to create a new package. If you’re already using Scarf, you’ll be able to click “New Package” in the navigation bar. Scarf gateway currently supports two package types: Docker, and Files.
Hosting packages on your custom domain via Scarf has no impact on your existing users; your domain adds a new path for users to download your package. You can encourage end-users to switch their pull commands over to your new domain, but they can continue pulling directly from your registry provider with no negative impact.
Should you decide to switch registries later on, current users will have to update their pull commands to either your custom domain or to the new registry URL. If they go straight to the registry, they would need to update every time you decide to switch registries. If they use your custom domain, they will never need to update it again.
Generally, no. Your package continues to be hosted on your current registry. Scarf Gateway is simply a thin layer on top. Since the gateway acts as a static entry point to your containers, you will always have the freedom to host your container on any registry you choose.
For enterprise customers, Scarf Gateway can cache your artifacts to improve global performance and even keep your artifacts online in the event of an outage from your origin hosting provider. Contact sales@scarf.sh to learn more.
No. Scarf Gateway does not store any personally identifiable information.
Scarf looks up IP address metadata, but the raw IP addresses are discarded and never exposed. IP metadata may contain:
• Coarse-grained location
• Company information, cloud providers, etc.
Additionally, Scarf sees metadata about the client and artifacts being downloaded such as:
• Container tags/versions
• Client container runtime information
• Basic device/OS information
We’d love your input to help us prioritize support for additional package types. Java, Apt, RPM, and others are planned.
Scarf Gateway is free to use! To gain access to additional features like our developer API, raw data export, integrations, availability & support SLA's contact our sales team.
Scarf Gateway is managed by the Scarf team. We plan an open-source release of the Gateway for self-hosting when it's out of beta and into general availability.