For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
      • AstroFully-managed data operations, powered by Apache Airflow.
      • Astro Private CloudRun Airflow-as-a-service in your environment.
      • Professional ServicesExpert Airflow services for your enterprise's success.
    • Tools
      • Cosmos
      • Orbiter
      • CLI
      • AI SDK
      • Agents
      • Blueprint
      • UpdatesThe State of Airflow 2026See the insights from over 5,800 data practitioners in the full report. Download Now ➔
  • Customers
  • Docs
    • Insights
      • Blog
      • Webinars
      • Resource Library
      • Events
    • Education
      • Academy
      • What is Airflow?
  • Pricing
Get Started Free
    • Overview
      • Overview
      • Deploy a project image
      • Deploy DAGs
      • Deploy code with GitHub
      • Deploy a dbt project
      • Deploy history and rollbacks
    • Book Office Hours

Product

  • Platform Overview
  • Astro
  • Astro Observe
  • Astro Private Cloud
  • Security & Trust
  • Pricing

Tools & Services

  • Cosmos
  • Docs
  • Professional Services
  • Product Updates

Use Cases

  • AI Ops
  • Data Observability
  • ETL/ELT
  • ML Ops
  • Operational Analytics
  • All Use Cases

Industries

  • Financial Services
  • Gaming
  • Retail
  • Manufacturing
  • Healthcare
  • All Industries

Resources

  • Academy
  • eBooks & Guides
  • Blog
  • Webinars
  • Events
  • The Data Flowcast Podcast
  • All Resources

Airflow

  • What is Airflow
  • Airflow on Astro
  • Airflow 3.0
  • Airflow Upgrades
  • Airflow Use Cases
  • Airflow 2.x End of Life

Company

  • Our Story
  • Customers
  • Newsroom
  • Careers
  • Contact

Support

  • Knowledge Base
  • Status
  • Contact Support
GitHubYouTubeLinkedInx
  • Legal
  • Privacy
  • Terms of Service
  • Consent Preferences

  • Do Not Sell or Share My Personal information
  • Limit the Use Of My Sensitive Personal Information

Apache Airflow®, Airflow, and the Airflow logo are trademarks of the Apache Software Foundation. Copyright © Astronomer 2026. All rights reserved.

LogoLogo
On this page
  • See also
Deploy code

Deploy code to Astro

To run your code on Astro, you need to deploy it to a Deployment. You can deploy part or all of an Astro project to an Astro Deployment.

There are several options for deploying code to a Deployment:

  • Project deploys: Run astro deploy to build every non-dag file in your Astro project as a Docker image and deploy the image to all Airflow components in a Deployment. This includes your Dockerfile, plugins, and all Python and OS-level packages. Dags are deployed separately to each Airflow component through a sidecar container. See Deploy a project image.
  • Dag-only deploys: Run astro deploy --dags to deploy only your dag files to Astro. If you only need to deploy dag changes, running this command is faster than running astro deploy since it does not require installing dependencies. See Deploy Dags.
  • Image-only deploys: Run astro deploy --image to build and deploy your Astro project configurations as a Docker image without deploying your dags. This is useful you have a multi-repo CI/CD strategy, and you want to deploy your dags and project configurations from different repositories or storage buckets. See Image-only deploys
  • dbt deploys: Run astro deploy --dbt to deploy only a dbt project to Astro. See Deploy dbt projects to Astro. You must use this command to deploy dbt projects to Astro.
  • Remote Execution project deploys: For Deployments configured for Remote Execution, use astro deploy to build and deploy the Runtime (orchestration plane) image, and use astro remote deploy to build and push client images for your Remote Execution Agents. See Initialize and deploy Remote Execution projects for full instructions.
  • GitHub integration deploys: The Astronomer GitHub integration allows you to map a branch from your GitHub repository to directly deploy to Astro after you merge pull requests to the mapped branch. See Deploy code with the Astro GitHub integration.

For each deploy option, you can either trigger the deploy manually or through CI/CD. CI/CD pipelines can include both image deploys and dag-only deploys, and they can deploy to multiple different Deployments based on different branches in your git repository. See CI/CD overview.

If multiple deploys are triggered simultaneously or additional deploys are triggered while a deploy is still processing, whether manually or through CI/CD, the first deploy is processed and then the subsequent deploys are completed. This behavior is different from how Astro processes simultaneous code deploys with the GitHub integration, which cancels the first deploy, and applies the most recent.

See also

  • Create an Astro project
  • Develop your Astro project
Edit this page
Built with