An insurance claims arbitration provider moves off Chef to commercially supported Ansible with Ascender Pro

This customer is a $50M+ nonprofit that resolves claims disputes for the insurance industry, serving thousands of member companies whose filings totaled almost $27 billion in 2025. Automation reliability underpins a member-facing service that insurers depend on.

A small internal team runs configuration management and automation for the fleet, working alongside an outside implementation partner, so the tooling has to give a lean team broad reach and clear control over what runs where.

The team ran Chef for configuration management. Over time it saw support quality and update cadence decline, and felt it directly every time a renewal came up. With the open source Chef Infra Server set to reach end of life in November 2026, and no new code, features, or security fixes contributed after the end of October 2026, the team decided to move its configuration management to Ansible on a supported platform while it still controlled the timing, rather than migrating under deadline pressure.

The search started with the open source Ascender project. The team found Ascender while looking for an Ansible-based automation hub, downloaded the open source version, and ran it in production on its own before ever talking to CIQ. When it evaluated the commercial options, it weighed self-managing the open source Ansible tooling against a platform with a commercial support model behind it. A lean team responsible for a mission-critical service chose the supported platform.

Three capabilities drove the decision. Ascender Pro adds role-based access, single sign-on, credential management, and audit logging to the open source foundation the team already knew, backed by premium 24/7 support and a monthly release cadence, with hotfixes for major CVEs.

The team started from its existing open source Ascender instance and upgraded in place by adding the Ascender Pro components, following the upgrade guide in CIQ’s documentation. CIQ provisioned the team in the CIQ portal for support tickets and repository access, granted the customer’s leads administrator rights, and opened a shared Slack channel for quick installation questions alongside the formal ticket queue. CIQ scheduled weekly syncs for the first month of operation.

The engineer who led the evaluation and drove the decision runs the platform day to day with his team. On the first onboarding call after purchase, he told CIQ the team expected to complete the conversion to Ascender Pro within the week.

The customer runs production automation with the controls and the support model its claims operation requires. The team operates one control plane across on-premises and cloud systems, with role-based access and an audit trail its auditors can rely on, and it has moved from scheduled bulk patching to targeted CVE remediation, all on a supported open source foundation.

CIQ supports Ascender Pro commercially and contributes upstream to the open source Ascender project. The customer runs on an open source foundation with a vendor that develops the project it commercializes, backed by a support model built for production. Multiple vendors support Ansible-based automation. This team chose CIQ for the depth of that support and the automation and audit capabilities Ascender Pro adds.

See how an insurance claims arbitration provider moved off Chef ahead of its end-of-life deadline, and what event-driven remediation and audit-ready reporting look like on a 650-node hybrid environment.