Cloud.gov Deprecation Policy

Policy Overview

When Cloud.gov must retire a service, feature, or API—for reasons such as security, compliance, or platform reliability—we follow a structured, transparent process. If there’s a replacement, it’s made available before any deprecation begins.

Customers can rely on a predictable notification and shutdown sequence, unless an elevated risk requires an accelerated timeline. In those cases, we’ll clearly explain what changed and why.

Deprecation Timeline

Phase	Timing	Customer Impact
Announcement	Day 0	Email sent to all customers
Stop new instances	Day ≥ 30	New creations disabled; existing instances continue
Reminder cadence	Every 14 days ≥ Day 30	Emails to remaining users of the deprecated service
Shutdown existing	Day ≥ 150	All remaining instances terminated
Accelerated exceptions	As needed (risk-based)	Modified dates with justification communicated clearly

info

Customer Responsibility: You must monitor notifications, plan migrations, and act promptly on reminders.

Visual Timeline

info

Customer Responsibility: Monitor your usage, plan and migrate to replacement services promptly, and stay responsive to reminder emails.