Skip to main content

How your code is handled

This page covers what happens to your game code when you run shipthis game ship.

Key points
  • Your game code is uploaded to private storage and only accessed via temporary signed URLs
  • Build machines are ephemeral - your files are deleted from the machine after each build
  • All uploaded game code and build outputs (APK/AAB/IPA) are automatically deleted after 30 days

Uploading your game files​

The CLI asks the ShipThis backend for a temporary upload URL. Your game files are then packaged locally:

  • Files matching shippedFilesGlobs in shipthis.json are included
  • Files matching ignoredFilesGlobs are excluded

The resulting archive is uploaded directly from your machine to a private DigitalOcean Space using the temporary URL.

Where files are stored​

Uploaded files live in a private DigitalOcean Space. The space is not public and cannot be browsed.

Files can only be accessed using signed URLs that expire after a short time. These URLs are generated on demand.

This storage holds:

  • Your uploaded game code
  • The resulting build outputs (APK/AAB/IPA)

How build machines access your code​

Build machines do not have general access to stored game files or credentials.

When a machine picks up a job, it receives a temporary signed download URL for your game code. It downloads the archive, extracts it, runs the build, and uploads the results using signed upload URLs from the job metadata.

Build machines cannot browse files or access anything outside the job they are running.

Cleanup after the build​

Once a job completes, a cleanup routine deletes:

  • Downloaded and extracted game files
  • Build intermediates
  • Temporary files

Build machines do not keep any of your files after a job finishes.

Retention and deletion​

  • Uploaded game code and build outputs (APK/AAB/IPA) are kept for 30 days
  • A lifecycle policy on the storage automatically deletes them after that