CIQ announced that Ascender Pro now closes the loop between detection and remediation across an entire Enterprise Linux fleet, automatically routing the right fix to the right host in the right environment.
Operations teams get one system that watches for problems, decides what to do about them, and acts without a person in the middle, no matter how many environments they run. That same investment extends to the collections and containers teams depend on, and reaches beyond Ascender Pro entirely, with CIQ open sourcing the caching layer behind it for the wider Ansible community. Ascender Reaqt, Ascender Registry and Federated Inventories are available now for Ascender Pro customers, with Ascender Galaxy Proxy released today as open source.
With Ascender Reaqt, each rule set gets its own endpoint and its own authentication token, so a credential tied to one integration never exposes any other, and a companion web application gives administrators a full UI and API for managing users, teams, permissions, providers, rule sets and listeners, backed by dashboards and metrics. Built as independent Go services and written from scratch rather than adapted from an existing open source project, Reaqt gives CIQ full ownership of the codebase and lets the product evolve on its own roadmap.
Ascender Registry lets administrators create repositories, pull specific collections and versions down from Ansible Galaxy, and host them locally, restricting exactly which collections and versions users are allowed to run. Teams can publish their own private collections the same way, and Registry doubles as a container registry for execution environments, all served through the same API structure as upstream Galaxy, so existing Ansible tooling works without changes.
Federated Inventories solves a problem most teams have learned to work around by hand: a ticketing system, a monitoring tool or a vulnerability scanner typically knows a hostname, not which of a dozen inventories that host lives in. Federated Inventories groups existing inventories together while preserving each one's own variables and instance group assignments, then automatically determines which underlying inventory a target host lives in when a job runs, splitting one request across as many environments as necessary with no extra setup.
"Enterprises running Linux at scale have been stuck choosing between an automation platform that does everything and one they can actually own and trust. That's the problem we set out to solve with this release. Ascender Pro gives operations teams a way to detect a problem, control what's running in their environment, and get the fix to exactly the right host, automatically, all built from the ground up on our own roadmap. Galaxy Proxy solves a problem the entire Ansible community shares, so we're giving it back as open source. It's the same principle behind everything we build at CIQ: own your infrastructure, control your own destiny and never be at the mercy of somebody else's roadmap. Full ownership where it matters, real contribution back to the community that got us here, that's what building infrastructure the right way looks like," said Gregory Kurtzer, CEO and founder of CIQ and founder of Rocky Linux.
Ascender Galaxy Proxy started as a fix for a real problem: public Ansible Galaxy responses can be slow or unavailable, and that drags down CI/CD pipelines and project syncs that depend on them. Galaxy Proxy sits between Ansible and Galaxy and caches every response, not just collection downloads, cutting typical wait times by as much as 75 to 80 percent. CIQ is releasing it as open source for any Ansible user, including those running AWX or another Ansible-based platform, while Ascender Pro customers get the full Registry application on top of it.
"For our customers, this release isn't about matching a feature checklist; it's about giving operations teams their time back. Federated Inventories alone removes a routing problem that used to require its own tooling or a manual step, and paired with Reaqt's automatic remediation, a single alert can turn into a fix on exactly the right host without anyone standing in the middle," said Bjorn Hovland, President of CIQ.
Ascender Reaqt, Ascender Registry and Federated Inventories are available now to existing Ascender Pro customers. Ascender Galaxy Proxy is available now as an open source project.
The Latest
Production incidents rarely announce themselves as database problems. They appear as slow transactions, timeouts, rising response times, or an application struggling under a workload it previously handled. APM provides an essential starting point. It can identify a slow transaction path, highlight an affected service, and show that a database dependency is consuming more time than expected. But identifying the database as part of the problem is not the same as explaining what is happening inside it ...
Cloud teams are under constant pressure to reduce spend without slowing development or increasing operational risk. They are deploying autoscalers, rightsizing workloads, enforcing resource requests, reviewing utilization dashboards, and building FinOps processes around cloud-native environments. Yet the results often disappoint ...
Ask most IT leaders about their biggest concern with AI and you'll hear the same answer: hallucinations ... Today, however, the conversation has shifted ... As organizations move beyond chatbots and experiments, they are increasingly deploying AI agents that perform multi-step tasks. These systems retrieve documents, query databases, call APIs, generate reports, write code, and make recommendations. The issue is not whether the model can reason. The issue is whether the organization can see, verify, and govern the decisions being made along the way ...
While organizations want to take control of their telemetry, building telemetry pipelines from scratch can be a very daunting, complicated task, even when leveraging open-source standards like OpenTelemetry. It requires specialized knowledge across distributed systems, data engineering, and security. This fragmented approach across systems causes higher operational costs; it puts a strain on resources and reduces efficiency as teams have to work with different interfaces and processes ...
For decades, enterprise networks were designed around a simple assumption: work happened inside the office. Applications lived in centralized data centers, employees connected through internal infrastructure, and security focused on protecting the perimeter that surrounded everything ... But the way organizations operate today bears little resemblance to that environment. Cloud platforms host critical applications, employees connect from homes and airports as often as they do from offices, and partners collaborate through shared systems that exist far beyond corporate walls. In short, the corporate network no longer resembles the environment it was designed to protect ...
As an analyst who researches how IT organizations design, build, and operate their networks, I find that network data is a constant source of pain. Network teams struggle with data quality, fragmentation, authority, access, and trust. And these issues undermine everything they try to do. Here are the numbers: Only 45% of network teams are completely confident in the accuracy of their network source of truth, which documents the intent of their network ...
The 2026 Global Data Center Survey from Uptime Institute reveals an industry navigating workforce constraints, escalating outage expenses, even as rising costs remain the top concern for management teams ...
The next observability gap may not be in the code. It may be under the rack. That sounds strange until you think about how AI incidents actually feel in the middle of an investigation ... The application dashboard may be accurate. It may also be stopping at the wrong boundary. AI systems depend on software, but they also depend on a dense physical stack: racks, power paths, thermal margin, maintenance activity and, in many environments, liquid cooling. Those physical dependencies can change slowly before they look like a software incident ...
Certificate expiration is the rare outage you can see coming. Every TLS certificate carries the date it stops working, so the moment it will begin breaking connections is knowable in advance. That's what makes an expired certificate such a frustrating way to lose a service. What's changing now is how often that date comes around ...
Enterprises operate different combinations of workloads across cloud, hybrid and multicloud environments. For business-critical workloads, teams need to consider monitoring and observability early so they can detect health issues, investigate failures, and understand operational impact. Organizations place workloads on cloud platforms based on a combination of technical requirements, economics, existing dependencies, organizational standards, and business priorities. Their monitoring priorities therefore depend on what they operate and where those systems run. Those priorities will not look the same for every organization ...