Security and releases

Releases every two weeks, security patches outside that cadence.

Every version passes through four phases. We keep maintaining a superseded version, and you have a defined escalation path for incidents.

Releases

Release cadence.

We correct reported defects within a few weeks.

14 days

The rule

We ship fixes and small additions on a two-week cadence. Every one of our releases runs through the same checks, however small the change.

1× per month

The floor

If a cycle runs long, we still ship at least one release per month. That keeps the gap between two versions predictable for you.

Off cadence

Urgent fixes

When a defect affects your live operations, we do not make the fix wait for the next scheduled release.

Security

Testing runs alongside development.

We test security in parallel with development. We fix critical findings outside the release cadence.

Regular security reviews

We review Collabase for vulnerabilities on a regular basis. The review is a fixed part of our development cycle.

48 hours for critical findings

For critical findings we ship a security patch within 48 hours. In managed operation we install it without you doing anything; in self-hosted operation we make it available to install within the same window.

Annual external review

We plan to have Collabase reviewed for security once a year by a Swiss auditor. The result will be published here once the first report is in.

Planned
Lifecycle

We keep maintaining superseded feature versions for 6 months.

In self-hosted operation you install upgrades during a maintenance window. For a superseded version we keep shipping bug and security fixes for a further 6 months. In managed operation you always run the current version.

01

Early availability

We make this version available to organisations that want to adopt it early. In this phase we support you more closely than in regular operation.

02

Generally available

The current version. This is where we build new features, and every adaptation refers to it.

03

In maintenance

Superseded but still maintained: for 6 months we keep shipping bug and security fixes. We no longer build new features for this version.

04

End of life

We no longer ship fixes for this version. We help you with the upgrade for as long as someone is still running it.

Product lifecycle: each version with its phase per quarter.
20262027
Q2Q3Q4Q1Q2Q3Q4
Collabase 1.0
Early availability
Generally available
Generally available
Generally available
Generally available
Generally available
Generally available
  • Early availability
  • Generally available
  • In maintenance
  • End of life

We brought Collabase 1.0 into early availability in June 2026; the version has been generally available since August 2026.

Operation and upgrades can also be handled by a partner. See partners

Self-hosted operation

Upgrades in-house or through a partner.

If you run Collabase on your own infrastructure, we ship every version as a package and you choose when to install it. Alternatively, a partner takes on operation and upgrades for you.

Support

SLA and escalation.

Our Collabase support adds a direct path for product questions to your existing support.

Existing contracts

Existing support contracts and contacts remain unchanged.

Collabase support is added

For questions about the product, about releases and about security advisories you reach the team that builds Collabase directly.

One point of contact

Operation, development and support sit with us in the same place. When something breaks, you have one point of contact.

Tiers and response times in the quote

Which availability and response times apply to you depends on scope and operating model. We settle that before you sign.