Frequently Asked Questions
Key questions about Release Brief.
Is Release Brief publicly available in Azure DevOps Marketplace?
No. The extension is currently shared privately with selected Azure DevOps organizations.
Does Release Brief have its own backend?
No. Release Brief runs in the browser as an Azure DevOps extension and does not have its own backend for release data analysis.
Is Azure DevOps data sent outside the organization?
No. Release Brief does not send data to external analytics systems or AI models. Analysis is performed based on rules defined in the extension.
Does Release Brief collect telemetry?
No. Release Brief does not use external telemetry or analytics tools.
Can flags and templates be adapted to our own process?
Yes. You can configure flags, classification thresholds, release note templates, email subjects, and message content.
Who is Release Brief for?
Primarily for Release Managers, DevOps Engineers, Product Owners and Engineering Managers working in Azure DevOps.
How does license purchase work?
The purchase is handled directly through contact. Once the number of Release Brief users is agreed and payment is received, the extension is shared with the designated Azure DevOps organization.
How do the named-seat license and seat assignment work?
The standard licensing model is based on named Release Brief users. The license is assigned to a specific Azure DevOps organization, and seats are not floating or concurrent. A user can activate only their own seat if the license is valid and a seat is available. For larger organizations or processes that require access across the whole organization, an individual organization-wide license may be arranged.
Where are the license and seats managed?
The panel is located at Organization Settings → Release Brief Admin → License. Updating or removing the license and managing seats are available only to an Azure DevOps organization administrator / Project Collection Administrator. A regular user cannot edit the license or remove other users from seats.
How is access controlled without a backend?
Access is controlled through the validity of the signed offline license, its expiry date, grace period, and renewals. After expiry, a customer who does not renew receives no new key. When reducing the seat count, the customer receives a new license and the organization administrator removes excess users.
Are there services other than the license itself?
Yes. In addition to the license itself, there is also deployment process analysis, improvement recommendations, tool configuration, and a workshop.
How long is the pilot?
The pilot lasts 14 days.
How does support work?
Support is provided by email.