Deprecation Policy

This page describes our policy in the event of removal of customer-usable functionality from WarpStream services.

Potential customer impact

• Large: could prevent use of service if the customer relies on the feature.

• None: totally transparent, depending on customer usage of the service.

Examples

• Complete removal of a feature from the UI.

• Shutting down api/v1/foo.

Frequency

Rare (~1 or fewer per year)

Communication before the change

• Guaranteed: multiple email notifications to all registered WarpStream users, starting at least 180 days before the deprecation date, with details about the change and available alternatives.

• May also include: in-app messaging; updated documentation and release notes; communication from Sales and customer support.

Timing of the change for each customer

100% at Confluent’s discretion.