GOG Free Games Claimer

GOG Free Games Claimer is a minimal self-hosted Docker container that lets homelab users claim the current free GOG.com giveaway by sending an authenticated…

  • Automation
  • Game Servers
  • Productivity
  • Tools & Utilities
GOG Free Games Claimer is a minimal self-hosted Docker container that lets homelab users claim the current free GOG.com giveaway by sending an authenticated request to GOG's claim endpoint, using a single pasted session cookie instead of a full browser, so it can run on a schedule without headless Chromium.

Platform availability

Available on 1 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

37/100 Low

Maintained
57last commit 181 days ago
Popular
61 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

Availability: platform listings confirmed today, links checked 29 days ago

GitHub stars
1
Open issues
0
Last commit
2026-05-23
License
MIT
Activity
stale

Checked 9 days ago - source: GitHub (mecharmor/gog-free-claimer)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Getting your GOG session cookie Retrieve your GOG session cookie once (again whenever it expires, typically every few months): log in to gog.com in a browser, open DevTools (F12), go to the Network tab, refresh the page, click any request to gog.com, find the Cookie: header under Request Headers, and copy its entire value into the container's GOG Cookie field. Claim history is stored at /app/data/claims.json. source

Fetched 39 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I provide my GOG session cookie?

Log in to the GOG site, open your browser's network panel, copy the entire Cookie request header from an authenticated request, and paste that full value into GOG_COOKIE. You only need to do this until your session expires, which is typically every few months.

Can I test the cookie before making a real claim?

Yes. Run the claimer with --dry-run to validate the cookie without claiming the game.

Where is claim history stored and what should I persist?

Claims are saved to data/claims.json. Mount a host directory to /app/data so the history persists between runs.

Does it need a reverse proxy or published ports?

No. The container makes an outbound authenticated HTTP request, and the provided Docker run command publishes no ports. There is no web service that needs to be exposed.

Does the container keep running after a claim?

No. The Docker instructions use --rm for a one-shot claim, so the container does not need to remain running.

Can it send notifications when it runs?

Set DISCORD_WEBHOOK_URL to an optional Discord webhook to receive run updates. If it is omitted, webhook notifications are skipped.

Answers sourced from github.com

Community

Collected 53 days ago - public community threads