FedRAMP-hosted Red Hat Lightspeed reaches retirement date October 30

Red Hat says it will retire the FedRAMP-hosted deployment of Red Hat Lightspeed on October 30, 2026. As of this article’s October 24 publication date, six days remain before that deadline. The release-notes notice points organizations that need an on-premises deployment to Red Hat Satellite; it does not name a successor hosted FedRAMP service.

What changes

The change is specific to the FedRAMP-hosted deployment. Red Hat’s notice does not say that the wider Red Hat Lightspeed service is ending. The same documentation describes Lightspeed as a software-as-a-service application included with almost every Red Hat Enterprise Linux, OpenShift Container Platform and Ansible Automation Platform subscription. It says the service is delivered through the Red Hat Hybrid Cloud Console and updated regularly.

That distinction makes this a deployment-boundary retirement rather than a general product withdrawal. For organizations using the FedRAMP-hosted environment, however, the date is explicit: the notice says that deployment “will be retired” on October 30.

Who is affected

The immediate audience is any team whose Lightspeed workflow depends on Red Hat’s FedRAMP-hosted deployment. The documentation says Lightspeed discovers operational insights, recommends next actions and supports task automation, so the affected dependency may sit inside platform-operations processes rather than appear as a standalone application.

The notice does not describe migration sequencing, data-transfer behavior or a grace period. It also does not identify a replacement hosted FedRAMP endpoint in the release notes.

What Red Hat says, and what teams should verify

Red Hat explicitly directs organizations seeking an on-premises deployment to its documentation for administering Red Hat Satellite. The release note does not say that Satellite is an automatic migration target, and it does not claim that existing configuration or service data will transfer.

The practical next step is therefore an editorial recommendation, not a quoted vendor instruction: affected platform owners should confirm whether their organization uses the FedRAMP-hosted deployment, inventory integrations and operating procedures that depend on it, and evaluate the Satellite path against their requirements before October 30. The source supports Satellite as the documented on-premises option; any migration mechanics or additional support path must be established separately.