Skip to content
Aether Platform

Aether Gateway

The Entrance to Aether Build

Aether Gateway is the gateway that forms the entrance to Aether Build. It installs into an organization as a GitHub App (RE-X Aether Gateway), receives webhooks, verifies signatures, routes and normalizes events, handles retention and redelivery, and passes them to the system side (Zuul). Installing it into an organization completes the connection; no per-repository webhook setup is required on the user side.

The receiving point sits on a public relay while the actual systems connect outward, so no inbound holes need to be opened into the customer’s network.

A Two-Layer Split

  • Component side (each repository): GitHub Actions, as today. A component’s responsibility ends at its own PR going green.
  • System side (Zuul + Gateway): Managing change sets, verifying future states, cross-repository testing, and Permit-based landing decisions.

The boundary is the landing decision. Green on the component side comes from Actions; whether a change enters the system is decided on the system side.

What It Does

  • Webhook entrance — Receives webhooks from multiple organizations and projects; verifies signatures, routes, normalizes, retains and redelivers, and passes events to Zuul.
  • Tenant onboarding — Starting from the App installation, issues per-tenant accounts, credentials, signing keys, and connection bundles.
  • Change-set management — Keeps the ledger of Topics (the human-named side) and Bundles (sets of changes connected by dependencies). The source of truth stays on GitHub; Gateway’s held state is a hint, kept in step by reconciliation.
  • Dependency closure and freezing — Closes a set from dependency declarations (whose source of truth is on GitHub) and hands the frozen unit to Zuul.
  • Permit-based landing decisions — Ties verification results on future states to Permits and required checks, expressing the landing decision.

Two delivery shapes are supported: a central shape (installing our App is all it takes) and a customer-dedicated shape (issuing a customer-named App through the App Manifest flow, pointed at a customer-side relay).

Status

Event relaying and tenant onboarding are running in trial. Change-set management (Topic ledger, dependency closure, Bundle freezing and submission) is in design and verification, and includes parts not yet implemented. Progress for each item is updated as verification results return.

Pricing is undecided.