Arcane Releases

Quick links:

• Release Notes: Functional – features, improvements, enablement (subscribe for updates)

• Status Page: Operational – deployments, maintenance, incidents (subscribe for updates)

• Support: Tenant-specific enablement and assistance

Release Types, Cadence & Definitions

Arcane 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 improvements.

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 Arcane.

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, so clients can prepare for enablement discussions. Deployment scheduling is managed separately through the Status Page.

Release Lifecycle

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:

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

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

Status Page

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

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

This table is updated as each release progresses through staging and production. Subscribe to the Status Page for real-time deployment updates.

FAQ

When will my tenant receive an update?
All tenants are updated once a release has passed staging validation. The exact timing 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.

How often are releases made?
Minor releases are published every month. Major releases happen less frequently, when significant new functionality or breaking changes are introduced. Patch updates are applied behind the scenes whenever needed, with maintenance updates posted to the Status Page.

How can I request a new feature?
Clients can raise feature requests through Support or by contacting their Customer Success Manager. The Product team reviews these requests when shaping the roadmap.