General availability
JEN-er-ul uh-vay-luh-BIL-ih-tee
The official release of a product or feature to all customers, indicating it is production-ready and fully supported.
GA means a product or feature is officially released and available to all customers. It is production-ready, fully supported, and covered by the company's SLA. Before GA, a feature might be in beta (limited release) or preview (available but not fully supported).
The GA milestone matters because it signals commitment. A beta feature can change or be removed. A GA feature is something customers can depend on, build their workflows around, and expect to be maintained. GA announcements often appear in the release notes and changelog.
For enterprise customers, GA is often a requirement for adoption. They will not build production workflows on beta features because those features lack the stability guarantees they need.
Examples
A feature moves from beta to GA.
After 6 weeks of beta testing with 100 customers, the team fixes all critical bugs, finalizes the API, and updates documentation. The feature is announced as GA in the changelog. Support SLAs now apply. The beta label is removed from the UI.
An enterprise customer waits for GA before adopting.
The customer's engineering team tested the feature during beta and liked it. But their compliance policy prohibits production use of beta features. They wait for the GA announcement, then roll it out across their organization.
A company staggers the GA rollout.
The feature goes GA for self-serve customers first. Enterprise customers get it two weeks later, after additional stability monitoring. This staged approach reduces risk while still delivering the feature to the majority of users quickly.
In practice
Read more on the blog
Frequently asked questions
What is the difference between GA and a product launch?
GA is a technical milestone: the feature is production-ready and supported. A product launch is a marketing event that may coincide with GA. Some features go GA quietly (added to the changelog). Major features get a full launch campaign.
Can a GA feature be changed?
Yes, but with care. Breaking changes to GA features require a [deprecation](/glossary/deprecation) period and migration path. Non-breaking improvements can be added at any time. The GA label is a promise of stability, not a promise of no further changes.
Related terms
A pre-release version of a product or feature made available to a limited audience for testing and feedback before general availability.
The process of phasing out a feature, API, or product version with advance notice so users can migrate to alternatives.
The second major version of a product or feature, typically a significant overhaul that incorporates learnings from V1.
Want the complete playbook?
Picks and Shovels is the definitive guide to developer marketing. Amazon #1 bestseller with practical strategies from 30 years of marketing to developers.