Release Pipeline Overview
Learn about Release Pipelines for sophisticated, multi-stage rollout strategies across environments
Release Pipelines enable multi-stage rollout strategies that respect your infrastructure boundaries, providing greater control over feature deployments.
When to use Release Pipelines
Consider using Release Pipelines when you need to:
- Implement infrastructure-aware deployment strategies beyond what traditional feature flags offer
- Safely roll out changes in complex, distributed systems with minimal risk
- Deploy progressively across environments (dev → staging → prod)
- Target specific infrastructure segments with precision (e.g., prod-us-west → prod-us-east → prod-eu)
- Control progression between stages with time intervals or manual approvals
- Monitor each deployment stage before proceeding to the next
- Enable instant rollbacks if issues arise during any phase
Especially valuable for:
- Platform engineering teams managing multi-environment, multi-region infrastructure
- DevOps practitioners implementing progressive delivery strategies
- SREs responsible for maintaining system reliability across complex deployments
- Organizations with mission-critical services that can't afford downtime
Key concepts
| Concept | Description |
|---|---|
| Release Pipeline | Defines the complete release strategy for a feature gate or dynamic config change |
| Phase | A distinct stage in the pipeline with specific conditions targeting designated release segments |
| Trigger | An event that starts when a feature gate or dynamic config begins using a Release Pipeline |
| Action | Controls you can apply to an active Trigger to manage the release process |
Get started with release pipelines
Release Pipeline is currently only supported in Statsig's Server Core SDKs. Legacy SDKs continue to work but won't get the full features of release pipelines.
Follow these tutorials to begin implementing Release Pipelines:
Current limitations
- Experiments aren’t supported in release pipeline
- Resalt/Disable/Delete/Archive/Launch actions won’t trigger a release pipeline
- Scheduled rollouts aren’t supported to work in conjunction with release pipeline
Was this helpful?