giftReleases

Updates to AppControl are included as part of your annual subscription fee. Updates can be downloaded from the Blue Storm customer portalarrow-up-right by the contacts that have been authorized for your organization.

AppControl evolves continuously. We deliver improvements on a regular cadence while maintaining stability for enterprise environments.


Release Cadence

AppControl follows a 4–6 week release cycle.

Rather than fixed calendar dates, we operate a release train model:

  • New features and improvements are bundled into a release

  • Each release is shipped once it meets stability and quality criteria

  • The next release is typically delivered within 4–6 weeks

This approach allows us to:

  • Fix bugs quickly

  • Improve features incrementally

  • Avoid rushed or unstable releases


Versioning Scheme

AppControl uses a simple, transparent versioning model:

Major Release Format:

YYYY.N

Examples:

  • 2026.1

  • 2026.2

  • 2026.3

Where:

  • YYYY = calendar year

  • N = sequential release number


Patch Releases

When needed, we deliver patch updates:

YYYY.N.P

Examples:

  • 2026.2.1

  • 2026.2.2

Patch releases:

  • Contain bug fixes or small stability improvements

  • Do not introduce major feature changes

  • May be delivered between regular release cycles


What to Expect in Each Release

Each release typically includes:

  • Governance improvements

  • Security or quality enhancements

  • Bug fixes

  • Minor feature evolutions

  • Performance optimizations

Release notes are published with each version.


Stability Commitment

Features are never announced as “released” until they are fully available.

If a feature is not ready for the current release cycle, it moves to the next one — without compromising stability.


Roadmap Transparency

We maintain an evolving roadmap. However:

  • Roadmap items are directional

  • Timelines are estimates

  • We prioritize stability and customer impact over fixed dates


Summary

AppControl is designed to improve steadily — not in large disruptive jumps, but through consistent, high-quality iterations.

Last updated