Gemstash

What it does

Access controls

Gemstash API keys can be given specific permissions for pushing, yanking, and fetching gems.checked 5 Oct 2026

Authentication caveat

Private gems and specs are accessible without authentication by default; protected fetching can be enabled in setup.checked 5 Oct 2026

Bundler integration

Bundler can be configured to mirror gem sources through Gemstash, with the simpler mirror setup requiring Bundler 1.11.0 or later.checked 5 Oct 2026

Caching

Gem files are cached indefinitely, while dependency metadata is cached for 30 minutes by default.checked 5 Oct 2026

Caching backend

The default in-memory cache can be replaced with a Memcached server or cluster.checked 5 Oct 2026

Intended users

The project suggests Gemstash for teams using Bundler across machines, publishing private gems, or repeatedly bundling the same gems.checked 5 Oct 2026

License

The project is available under the MIT License.checked 5 Oct 2026

Maintainer

Gemstash is maintained by Ruby Central, which describes itself as a nonprofit supporting Ruby infrastructure.checked 5 Oct 2026

Monitoring

Gemstash provides a /health endpoint that reports status for its heartbeat, storage, and database.checked 5 Oct 2026

Private gems

Users can push, fetch, and yank private gems using API keys and the RubyGems command line.checked 5 Oct 2026

Purpose

Gemstash is a cache for remote gem servers such as RubyGems.org and a private gem source.checked 5 Oct 2026

Server limitation

Gemstash uses Puma and Rack, and its server configuration is not customizable, although the bind address and Puma thread count can be configured.checked 5 Oct 2026

Storage and database

Gemstash stores files under ~/.gemstash by default, and supports SQLite, PostgreSQL, MySQL, and MySQL2 database adapters.checked 5 Oct 2026

Upstream sources

Gemstash can fetch from multiple gem sources, and its default source can be changed in its configuration.checked 5 Oct 2026