---
title: "Deploy to Fly using a Depot builder"
description: "!https://depot.dev/blog/how-to-build-with-depot-on-fly"
date: 2024-12-25
published: true
tags:
  - cloud
  - containers
  - fly-io
  - infra
  - thought
template: link
---


<div class="embed-card embed-card-external">
  <a href="https://depot.dev/blog/how-to-build-with-depot-on-fly" class="embed-card-link" target="_blank" rel="noopener noreferrer">
    <div class="embed-card-image">
      <img src="https://depot.dev/images/banner/depot-fly-builder-banner.png" alt="Deploy to Fly using a Depot builder — Using Fly.io&#39;s new Depot builder, we&#39;ll walk you through how to deploy a TypeScript service globally with speed." loading="lazy">
    </div>
    <div class="embed-card-content">
      <div class="embed-card-title">Deploy to Fly using a Depot builder</div>
      <div class="embed-card-description">Using Fly.io&#39;s new Depot builder, we&#39;ll walk you through how to deploy a TypeScript service globally with speed.
</div>
      <div class="embed-card-meta">Depot &middot; depot.dev</div>
    </div>
  </a>
</div>


Here the integration to depot appears to be opt in using the `--depot` flag on `fly deploy`.  This must have changed over time though because today it was giving me issues and I had to opt out using `fly deploy --depot='false'`.  Looks like a great service and I just learned about them on their bad day.