Activator 3 Releases
Quick links:
Release Notes: Functional – features, improvements, enablement (subscribe for updates)
Status Page: Operational – deployments, maintenance, incidents (subscribe for updates)
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 type | Frequency | Definition | Notes |
|---|---|---|---|
Major | As needed | Introduces significant new capabilities or potential breaking changes | Always published with full release notes and enablement details |
Minor | Monthly | Regular functional improvements and new features | Published with full release notes; always scheduled in advance |
Patch | Ongoing | Small fixes, security updates, or backend optimisations | Applied silently, no release notes, but always announced on Status Page |
Release Principle
Multi‑tenant SaaS: All clients share the same infrastructure; updates roll out platform‑wide once validated.
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
Release Principle
Stability first: No production deployment without passing validation gates; features are production‑ready, never experimental.
A release goes through a structured path before it reaches production:
First, the release is deployed to STG.
This is announced with a maintenance update on the Status Page, and Anthill validates the release internally.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.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
Release Principle
Transparency: All deployment windows and incidents are visible on the 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
Release Principle
Minimal disruption: We aim for no downtime and backwards‑compatible changes.
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
FAQ
When will my tenant receive an update?
All tenants are updated once a release has passed staging validation and completed the Preview Period. The exact timing of staging and production deployments is always communicated via the Status Page.
Why don’t Release Notes include deployment dates?
Because Release Notes are designed to explain what has changed, not when it changes. Deployment is managed separately to keep information clear and consistent.
What is the Preview Period?
The Preview Period is the time between a release being deployed to staging and its rollout to production. In this period, Anthill will test the release with client-specific tenants, and Anthill hosts enablement conversations and feature deep dives.
How often are releases made?
Minor releases are published every month. Major releases happen less frequently, when major new functionality or breaking changes are introduced. Patch updates are applied behind the scenes whenever needed, with maintenance updates posted to the Status Page.
What happens if issues are found on staging?
If problems appear during the Preview Period, production deployment will be delayed until they are fixed. New maintenance windows are then announced on the Status Page.
How can I request a new feature?
Clients can raise feature requests through Support or by contacting their Account team. The Product team reviews these requests when shaping the roadmap.