Data and AI releases

548 this month · 176 companies

Cross-region disaster recovery for GCP dedicated clusters is generally available

Generally availableNot yet verified

Self-service cross-region disaster recovery (DR) for GCP dedicated clusters is now generally available. You can configure a primary and a secondary dedicated cluster in different GCP regions, and fail over with minimal downtime and data loss.

Regions

Read on astronomer.io

Also shipped Jul 29, 2026Astronomer in July 2026 →

More from AstroEvery Astro release →

Task-level utilization metrics

Astro now shows CPU and memory utilization at the Dag, task, and task instance level in a new Resource Metrics tab in the Airflow UI, with task-to-worker mapping that ties resource use back to the Dag, task, task run, and time window.

Update
Source ↗

Try the new Astro experience

Astro's navigation now gives you a single view across your entire Organization instead of a single Workspace. Deployments, Dags, and Astro IDE projects all appear across Workspaces in one view, with Workspace context on every row. Filter to a specific Workspace when you need to, or work from the full picture across your Organization.

Update
Source ↗

Billing API added to the Astro v1 Labs API

Enterprise+ Organizations can now query Astro cost and usage data programmatically through the new List daily usage endpoint on the Astro v1 Labs API , which returns per-Deployment resource cost data with a FOCUS-formatted response option.

Pricing
Source ↗

Test against an existing Deployment in the Astro IDE

You can now test code in the Astro IDE against an existing Astro Deployment in your Workspace, instead of only an ephemeral test Deployment. Testing against an existing Deployment reuses its configuration, connections, and resources, and skips provisioning a new environment.

Update
Source ↗

New Deployment analytics experience

Astro now offers a new version of the Deployment analytics experience with expanded Airflow visibility, including API server and webserver metrics, Dag processor coverage, Kubernetes executor and KubernetesPodOperator coverage, parse time, and richer per-status and per-component breakdowns.

Preview
Source ↗