How it works
Scarf Gateway functions similarly to a link shortener like bit.ly, redirecting traffic as a domain gateway. However, it is specifically designed to be compatible with various APIs used by different services.
To use Scarf Gateway, create a route between it and your current packages, containers, or downloads, which directs the gateway to fulfill requests. Set up a custom domain that resolves to your gateway's location and update your documentation, readme, and other sources with the new domain. Users should then be able to use the same install, pull, or download commands as before.
Supported services include:
- Registries like Docker Hub Google Container Registry, RedHat Quay, Amazon Elastic Container Registry, and Azure Container Registry
- Package managers like Nix, homebrew, RPM, Apt, etc.
- Language specific package registries and managers like PyPI & pip, or npm
- Files coming via source control repos (GitHub or Gitlab)
- Or any file that is a direct download on the internet
Track installs by company, location, platform, versions, cloud providers, container runtimes, referral source - and anything else
Fully GDPR compliant out of the box. Scarf ensures all personally identifiable information is discarded so you'll never have to touch anything sensitive
Custom domain support for container hosting prevents vendor lock-in , even to Scarf itself
A static URL frees you to manage your own distribution strategy
Switch registries and hosts seamlessy with no impact to end users
Natively supports Docker/OCI containers , Python packages, file downloads , API endpoints, or any URL.