Skip to main content

Astro Runtime architecture

Astro Runtime is a production ready, data orchestration tool based on Apache Airflow that is distributed as a Docker image and is required by all Astronomer products. It is intended to provide organizations with improved functionality, reliability, efficiency, and performance.

Deploying Astro Runtime is a requirement if your organization is using Astro. Astro Runtime includes the following features:

  • Timely support for new patch, minor, and major versions of Apache Airflow. This includes bug fixes that have not been released by the open source project but are backported to Astro Runtime and available to users earlier.
  • Exclusive features to enrich the task execution experience, including smart task concurrency defaults and high availability configurations.
  • The astronomer-providers package. This package is an open source collection of Apache Airflow providers and modules maintained by Astronomer. It includes deferrable versions of popular operators such as ExternalTaskSensor, DatabricksRunNowOperator, and SnowflakeOperator. See Astronomer Providers documentation
  • The openlineage-airflow package. OpenLineage standardizes the definition of data lineage, the metadata that forms lineage data, and how data lineage data is collected from external systems. This package enables data lineage on Astro. See OpenLineage and Airflow.
  • A custom logging module that ensures Airflow task logs are reliably available to the Astro data plane.
  • A custom security manager that enforces user roles and permissions as defined by Astro. See User permissions.
  • A custom Airflow UI that includes links to Astronomer resources and exposes the currently running Docker image tag in the footer of all UI pages.

For more information about the features that are available in Astro Runtime releases, see the Astro Runtime release notes.

Runtime versioning

Astro Runtime versions are released regularly and use semantic versioning. Astronomer ships major, minor, and patch releases of Astro Runtime in the format of major.minor.patch.

  • Major versions are released for significant feature additions. This includes new major or minor versions of Apache Airflow as well as API or DAG specification changes that are not backwards-compatible.
  • Minor versions are released for functional changes. This includes API or DAG specification changes that are backwards-compatible.
  • Patch versions are released for bug and security fixes that resolve unwanted behavior. This includes new patch versions of Apache Airflow, astronomer-providers, and openlineage-airflow.

Every version of Astro Runtime correlates to an Apache Airflow version. All Deployments on Astro must run only one version of Astro Runtime, but you can run different versions of Astro Runtime on different Deployments within a given cluster or Workspace. See Create a Deployment.

For a list of supported Astro Runtime versions and more information on the Astro Runtime maintenance policy, see Astro Runtime versioning and lifecycle policy.

Astro Runtime and Apache Airflow parity

This table lists Astro Runtime releases and their associated Apache Airflow versions.

Astro RuntimeApache Airflow version

Each Runtime version in a given minor series supports only a single version of Apache Airflow. For specific version compatibility information, see Runtime release notes.

Provider packages

All Astro Runtime images have the following open source provider packages pre-installed:

Provider package versioning

If an Astro Runtime release includes changes to an installed version of a provider package that is maintained by Astronomer (astronomer-providers or openlineage-airflow), the version change is documented in the Astro Runtime release notes.

To determine the version of any provider package installed in your current Astro Runtime image, run:

docker run --rm {image} pip freeze | grep <provider>

Python versioning

Astro Runtime supports Python 3.9. This is the only version of Python that Astro Runtime supports. If your data pipelines require an unsupported Python version, Astronomer recommends that you use the KubernetesPodOperator. See Run the KubernetesPodOperator on Astro.


In Airflow, the executor is responsible for determining how and where a task is completed.

In all local environments created with the Astro CLI, Astro Runtime runs the Local executor. On Astro, Astro Runtime exclusively supports the Celery executor.

Soon, Astronomer will provide a new executor with intelligent worker packing, task-level resource requests, improved logging, and Kubernetes-like task isolation.


Astro Runtime is distributed as a Debian-based Docker image. Runtime Docker images have the following format:


An Astro Runtime image must be specified in the Dockerfile of your Astro project. Astronomer recommends using non-base images, which incorporate ONBUILD commands that copy and scaffold your Astro project directory so you can more easily pass those files to the containers running each core Airflow component. A base Astro Runtime image is recommended for complex use cases that require additional customization, such as installing Python packages from private sources.

For a list of all Astro Runtime Docker images, see

System distribution

The following table lists the operating systems and architectures supported by each Astro Runtime version. If you're using a Mac computer with an M1 chip, Astronomer recommends using Astro Runtime 6.0.4 or later.

Astro RuntimeOperating System (OS)Architecture
4.1.xDebian 11.3 (bullseye)AMD64
4.2.xDebian 11.3 (bullseye)AMD64
5.0.xDebian 11.3 (bullseye)AMD64
6.0.0 - 6.0.3Debian 11.3 (bullseye)AMD64
6.0.4 - 6.0.xDebian 11.3 (bullseye)AMD64 and ARM64

Astro Runtime 6.0.4 and later images are multi-arch and support AMD64 and ARM64 processor architectures for local development. Docker automatically uses the correct processor architecture based on the computer you are using.