Introduction
Depot lets your studio sell and ship its game directly to players, from your own store page, with verified updates.
Depot is game distribution for small studios. You push a signed build, write a store page, and share the link. Players claim your game or redeem a key, install it with the Depot launcher, and get fast, verified updates. Your game can check that a player owns it, even offline, with the Depot SDK.
There's no marketplace in between. The link is yours, the players are yours, and so are the keys.
Depot is in staging. Every example here uses the staging service at https://api.staging.depot.games. Production isn't launched yet.
Start here
Quickstart
From a build folder to a playable link in a few commands.
Concepts
Games, releases, channels, packages and who can get your game.
How players get your game
What happens between your link and their Play button.
Everything works from the CLI and the API
The dashboard is one client of a public API. Anything you do there, you can do with the depot CLI or a plain HTTP request, so your CI pipeline or an AI agent can publish a game end to end.
depot game create --slug lantern-keep --name "Lantern Keep"
depot push --game lantern-keep --platform macos-arm64 --release 1.0.0 \
--input ./build --channel stable --note "The first release."
depot game page --game lantern-keep --tagline "Keep the lantern lit." \
--access free --publish publicPublishing builds
Push, channels, release notes, rollbacks and signing keys.
Store pages
Write your page, brand it with your art, and choose who can get the game.
Depot SDK
Check ownership and DLC in your game, online or off.
CLI reference
Every command and flag.
API reference
Every endpoint, with a playground against staging.
For agents
This site publishes /llms.txt and /llms-full.txt, and every page has a Markdown version. The API's own OpenAPI document is at https://api.staging.depot.games/v1/openapi.json.