Gemfury vs pypiserver

Gemfury is a hosted repository for public and private software packages. It supports RubyGems, npm, PyPI, Go Modules, Composer, Maven, DEB, RPM, Bower, and NuGet. Packages can be uploaded through a web interface or command line, with transfers to the repository over SSL. Private packages can be deployed through a Gemfury Repo URL using existing package-management tools and workflows. Gemfury says a secret token in the URL protects packages, and uploads, deployments, and installations use SSL. Users can share an account with coworkers; business plans add separate billing, multi-ownership, and fine-grained permission control. The Free plan costs nothing and includes unlimited collaborators, public packages, and versions, but no private packages. Personal 1C costs $9 a month for one collaborator; Team 10P costs $25 a month for unlimited collaborators and 10 private packages. Gemfury offers a 14-day trial without a credit card and says trial use has no limits. Packages are deleted one month after account cancellation and cannot be recovered.

pypiserver is a minimal, self-hosted package index for uploading and downloading Python packages with tools such as pip and easy_install. It serves packages from regular directories, including wheels, bdists, eggs and PGP signatures, and scans those directories recursively. Packages can be uploaded with pip, setuptools, twine or pypi-uploader, or copied to the server with scp. Upload access can be protected with an Apache htpasswd file; API users can configure custom authentication callables. The maintainers advise password protection for uploads, and the documentation recommends a reverse proxy to provide HTTPS. pypiserver can run as a WSGI application, with documented integrations for Docker, nginx, Apache, gunicorn and Paste. It provides a health endpoint that returns HTTP 200 when the service is running, with an option to configure the endpoint. The current version supports Python 3.10+ and PyPy3. It is free at free and is listed for Linux, macOS, Windows, API and self-hosted use. Its API covers the operations needed by common package tools rather than the full PyPI API; documentation uploads are accepted but not saved to disk.