Activator 3 Releases

Release Types, Cadence & Definitions

Activator is continuously growing, with new product versions introduced on a recurrent basis. Each new product release delivers a combination of innovation, industry best practices and regulatory-related improvement.

The following table summarizes the release model, cadence, and notes:

Release Notes

Release Notes are the main way we communicate what is new in Activator.

They are published for all minor releases (once a month) and for larger major releases. Patch updates are handled differently: they are applied silently in the background without release notes, although a maintenance update will always appear on our Status Page.

Release Notes explain new features, improvements, and deprecations. Each note includes enablement information, clearly labelled as either AUTO‑ON (enabled automatically for all tenants) or CONFIGURATION (requires setup by Anthill). Links to deep‑dive documentation are included when relevant.

Release Notes never contain deployment dates. They are published well in advance of a release entering staging (STG), so clients can prepare for enablement discussions. Deployment scheduling is managed separately through the Status Page.

Release Lifecycle

A release goes through a structured path before it reaches production:

1. First, the release is deployed to STG.
   This is announced with a maintenance update on the Status Page, and Anthill validates the release internally.

2. Once staging is complete, the release enters the Preview Period.
   During this time, Champion Users can access their staging tenants with the new release, test with tenant‑specific configurations, and participate in enablement sessions or feature deep dives hosted by Anthill.

3. After validation and client preview, the release is promoted to PROD.
   A new maintenance update is posted on the Status Page well in advance of this step, specifying the start and end of the production deployment window.

Status Page

All operational updates about deployments, incidents, or maintenance are communicated through the Status Page. Clients can subscribe for notifications.

• Maintenance updates are posted before both STG and PROD deployments.

• Each update includes a defined start and end time window.

• If problems are found during staging, new maintenance windows will be announced when the production deployment is rescheduled.

Maintenance Windows

All deployments occur Monday through Thursday mornings in Central European Time. We never deploy on Fridays, and we never deploy after 14:00 CET on weekdays.

Maintenance updates on the Status Page specify the exact start and end times for each window.

Release Schedule & Deployment Status