Astro is Astronomer's managed Apache Airflow service, a data orchestration platform for teams writing pipelines in Python, billed by usage per deployment hour.
Astro runs Apache Airflow for data teams that would rather write pipelines than operate the scheduler, workers and clusters underneath them. Astronomer, Inc., based in New York, builds and operates the service. Teams keep their Dags as Python files in Git, and Astro hosts the environment that code deploys into. On top of Airflow it adds observability, alerting, support and access controls. A deployment is the unit Astro manages: a hosted Airflow environment that can hibernate when idle and roll back to an earlier version. Workers scale to zero between runs, and Dedicated clusters give deployments single-tenant network isolation. The Astro CLI starts the same project on a laptop with astro dev start, and the GitHub integration deploys code when a pull request merges into a mapped branch. Preview Deployments create a separate environment for each feature branch. Astro Observe draws a lineage graph of Dags, tasks, datasets and tables and tracks freshness SLAs, while Remote Execution runs tasks on a customer's own Kubernetes. Astro fits data engineering teams already running Airflow in production who want hosting, support and monitoring without maintaining the cluster themselves. Platform teams facing security reviews get SSO enforcement, SCIM provisioning, custom RBAC, IP access lists and audit logs. Teams whose tasks must stay inside their own infrastructure keep execution there through Remote Execution while Astro hosts orchestration. Organizations that cannot accept a regional outage can add cross-region disaster recovery. Typical work on Astro is ETL and ELT, MLOps pipelines, analytics refreshes, AI workflows and moving jobs off a legacy scheduler. Through Cosmos, Astronomer's open-source package, a dbt project runs as Airflow tasks on the same schedule as the loads feeding it. Code travels from a branch to production through GitHub Actions or GitLab CI, and AI-assisted authoring helps draft and debug Dags along the way. When a run fails, Astro posts to Slack or PagerDuty with a link back to the run, so the on-call engineer can open the failed task's logs and retry history directly.
Pricing
View plans-
Developer
Custom pricing
- Deployments from $0.35 an hour on monthly billing, workers billed on top
- For teams building and testing pipelines
- AI-powered Dag authoring and debugging
- Flexible, scale-to-zero compute
- Hibernating deployments
- API access
- Deployment rollbacks
-
Team
Custom pricing
- Deployments from $0.42 an hour on monthly billing; annual terms by quote
- For teams running production pipelines that need support and observability
- Everything in Developer
- End-to-end observability and data quality
- Network isolation with Dedicated clusters
- High availability deployments
- Audit logging with 7-day retention
- 24x5 support
-
Business
Custom pricing
- Price on request, annual terms
- Everything in Team
- SSO enforcement
- CI/CD enforcement
- Audit logging with 90-day retention
- 24x7 support
-
Enterprise
Custom pricing
- Price on request, annual terms
- Everything in Business
- Remote execution agents
- Custom RBAC
- SCIM provisioning
- IP access list
- Organization dashboards
Features
- Included: Pipelines defined as Python code
- Included: DAG graph view of task dependencies
- Included: Cron and interval schedules
- Included: Sensors and event-driven triggers
- Included: Per-task retries with backoff
- Included: Partitioned backfills
- Included: Asset-level lineage across pipelines
- Included: Local development environment with parity
- Included: Branch deployments per pull request
- Included: Git-driven deploys
- Included: Run failure alerts to Slack and PagerDuty
- Included: Task-level run history and logs
- Included: Dynamic task mapping at runtime
- Included: Hybrid execution on your own compute
- Included: Managed serverless workers
- Included: Freshness and asset checks
- Included: Open source orchestrator core
Additional Features
- Astro CLI local Airflow environment
- GitHub integration deploys on merge
- Preview Deployments per feature branch
- Deployment rollbacks
- Hibernating deployments
- Scale-to-zero workers
- Dedicated clusters with network isolation
- High availability deployments
Best for
- Data engineering teams running Apache Airflow in production
- Teams replacing a self-managed Airflow install with a hosted one
- Platform teams that need SSO, SCIM and audit logs on Airflow
- Organizations that must run tasks on their own Kubernetes
- Analytics teams orchestrating dbt projects with Airflow
- Machine learning teams running MLOps pipelines
- Companies buying through AWS, Azure or Google Cloud marketplaces
Use cases
- Running ETL and ELT pipelines on a schedule
- Orchestrating MLOps training and scoring pipelines
- Running dbt projects as Airflow tasks with Cosmos
- Moving jobs off a legacy scheduler onto Airflow
- Orchestrating AI workflows
- Refreshing analytics tables
- Backfilling historical Dag runs
- Testing Dag changes in a preview deployment before merge
- Alerting on-call engineers when a Dag run fails
- Tracing a broken table upstream through the lineage graph
- Monitoring data freshness against an SLA
- Running tasks inside a private Kubernetes cluster
Screenshots & Videos
Explore Astro in action
User Reviews
Compare with Similar Software
Click to compare side by side with Astro