Tested so far
Automated backend, frontend, Helm and API-contract gates; PostgreSQL and worker integration; restart and outage recovery; tunnel HA; database failover; browser qualification; local single-node acceptance.
ASTRONOMER RESOURCES / EARLY ACCESS
Astronomer is in alpha. Evaluate it with us.
Astronomer runs today, and we want it tested on real clusters by teams who run them. If you operate more clusters than you would like to manage one at a time, we would like to hear from you.
Alpha · actively in development · not yet for production01 / WHAT ALPHA MEANS
Real software, early evidence.#
Adoption, the agent, the explorer, Flux delivery, the catalog, RBAC and SSO, audit, security posture, observability and backup all exist in code and are covered by automated tests. Single-node acceptance has passed for the current release line.
Cloud-provider acceptance, production-scale certification, multi-host HA and DR, and human accessibility acceptance are still open. Interfaces can change between releases, and we do not recommend production clusters yet.
See the full status and known limitsNot yet tested enough
Managed cloud providers at scale, large fleets on production-like infrastructure, multi-host failure and recovery, and real-world identity providers beyond the test matrix.
Why that matters to you
The fastest way to close those gaps is real clusters and real workflows. That is what we are asking early users for.
02 / WHO SHOULD TRY IT
Teams with clusters already running.#
Astronomer is for clusters that exist. You keep provisioning them your way.
Many clusters, one team
Adopt a handful of non-production clusters, deliver a platform component through Flux with a canary rollout, and tell us where it saved work and where it got in the way.
GitOps deliveryClusters you cannot reach inbound
Put the outbound agent behind your NAT, proxy or private network and see whether the explorer, logs and delivery work for you without opening a path in.
Fleet & adoptionTeams on the same clusters
Set up projects with quotas, scoped roles and your identity provider, then push on the edges of the access model.
Governance & access03 / HOW IT WORKS
Simple, and honest about the stage.#
Contact AlphaBravo with a short note about your clusters and what you want to prove. We will follow up to talk through fit, the current release and a useful test for your environment.
Getting in touch does not create an account, start a trial or commit you to anything.
- Tell us about your clusters
Distributions, versions, networks, identity provider, and what you want to prove.
- Agree a small test plan
Adopt a few clusters, roll out a component, connect SSO, run a restore drill.
- Run it together
On your non-production clusters, with a direct line to the people building Astronomer.
- Share what you found
Results feed the known limits, the status page and what we build next.
FAQ
Early access questions.#
Can we run production clusters on Astronomer today?
We do not recommend it. Astronomer is in alpha: scale, cloud-provider and multi-host HA acceptance remain open, and interfaces may still change. Use non-production clusters. #
What do we need to run it?
A Kubernetes cluster for the management plane with Gateway API, PostgreSQL and a Redis-compatible queue (bundled for evaluation, external or CloudNativePG and Valkey for production), and adopted clusters on Kubernetes v1.33 to v1.35. #
What does it cost?
Astronomer is licensed under the AGPL-3.0. Talk to AlphaBravo about support and access to releases during alpha. #
Can we evaluate it with Constellation?
Yes. Constellation installs from Astronomer’s catalog. Both products are in alpha; see the joint page for what connects today. #