Skip to content

Reference

Release model

How Breqwatr changes the platform: how releases are made, how they're numbered, and how they reach each kind of deployment.

Breqwatr runs and upgrades the platform: the cloud APIs, the Breqwatr Cloud Portal (Strata) and the services behind them. There is nothing on the platform for you to upgrade. The operating systems and software inside your instances stay yours to update: see Shared responsibility.

Releases
Cadence Regular, scheduled releases, each carrying a small set of changes
Fixes In the next release. Fixes aren't back-ported to earlier releases
End of life None: every deployment moves forward to a current release, so none is left on an unsupported version

How a change is made

  • Every change is peer reviewed, including a security review, before it's merged.
  • Every change is tested automatically.
  • Third-party dependencies are scanned for known vulnerabilities, and upgraded monthly.
  • Independent penetration tests run periodically.

Version numbers

Releases are numbered by date, YYYY.MM.N, where N counts the releases in that month.

Version Meaning
2026.10.1 The first release in October 2026
2026.10.2 The second release in October 2026
2026.11.1 The first release in November 2026

Upgrades by deployment

Deployment Upgraded by Breqwatr
Public cloud To each release
Private hosted Quarterly, or on request
On-premises Quarterly, or on request