potiuk commented on code in PR #1457: URL: https://github.com/apache/airflow-site/pull/1457#discussion_r2929636346
########## landing-pages/site/content/en/blog/airflow-registry/index.md: ########## @@ -0,0 +1,93 @@ +--- +title: "Introducing the Apache Airflow Registry" +linkTitle: "Introducing the Apache Airflow Registry" +author: "Kaxil Naik" +github: "kaxil" +linkedin: "kaxil" +description: "The Apache Airflow Registry is a searchable catalog of 99 providers and 1,600+ modules — operators, hooks, sensors, triggers, and more — now live on airflow.apache.org." +tags: [Community] +date: "2026-03-16" +--- + +Today we're launching the **[Apache Airflow Registry](https://airflow.apache.org/registry/)** — a searchable catalog of every official Airflow provider and its modules, live at [airflow.apache.org/registry/](https://airflow.apache.org/registry/). + +Need an S3 operator? A Snowflake hook? An OpenAI sensor? The Registry helps you find, compare, and configure the right components for your data pipelines — without digging through docs or PyPI pages. + + + +## By the Numbers + +| | | +|---|---| +| **99** | Official providers | +| **1,614** | Modules (operators, hooks, sensors, triggers, transfers, and more) | +| **329M+** | Monthly PyPI downloads across all providers | +| **125+** | Integrations with cloud platforms, databases, ML tools, and messaging services | + +## Search Everything + +Hit **Cmd+K** from any page and start typing. Results show up instantly, grouped by Providers and Modules, with type badges so you can tell a hook from an operator at a glance. + + + +## Provider Pages + +Each provider gets a dedicated page with everything in one place: install command with copy-to-clipboard, version selector, extras dropdown, compatibility info, connection types, and the full module listing organized by type. + + + +The Amazon provider, for example, has **372 modules** across operators, hooks, sensors, triggers, transfers, and more. Module type tabs let you filter to exactly what you're looking for, and a category sidebar groups modules by AWS service (S3, Lambda, Glue, Step Functions, etc.). + +## Connection Builder + +Click any connection type badge on a provider page, fill in the fields, and the builder generates the connection in three formats — **URI**, **JSON**, and **Env Var** — ready to copy into your configuration. + + + +No more guessing URI encoding or JSON structure. + +## Explore by Category + +Not sure which provider you need? The **[Explore page](https://airflow.apache.org/registry/explore/)** organizes providers into categories: Cloud Platforms, Databases, Data Warehouses, Messaging & Notifications, AI & Machine Learning, Data Processing, and more. + + + +## Statistics + +The **[Stats page](https://airflow.apache.org/registry/stats/)** breaks down the ecosystem: **853 operators**, **300 hooks**, **164 triggers**, **157 sensors**, **83 transfers**, and more — plus top providers by downloads and module count. + + + +## JSON API + +Every piece of data in the Registry is available as structured JSON — providers, modules, parameters, connections, versions. An **[API Explorer](https://airflow.apache.org/registry/api-explorer/)** lets you browse all endpoints interactively. + + + +This makes the Registry accessible to IDE extensions, AI coding assistants, and automation tools. + +## Light & Dark Mode + +Full theme support with dark mode as the default. One click to switch. + + + +## Standing on Shoulders + +The Airflow Registry is a community-owned successor to the [Astronomer Registry](https://registry.astronomer.io), which [Astronomer](https://www.astronomer.io) and Josh Fell built and maintained for years as the go-to place to discover Airflow providers. Their work proved the value of a searchable provider catalog and shaped what this new registry is. + +The Apache Airflow Registry lives at `airflow.apache.org`, is built from the same repo as the providers, and updates automatically when new versions are published. + +## What's Next + +This is the first release of the Registry. Here's what's coming: + +- **Third-party provider support** — list community-built providers alongside the official ones Review Comment: I am not sure if that is coming and would be allowed by ASF rules. I would rather say that we are exploring the options for it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
