Airlock as a Service Knowledge Base
API Reference Service Status Airlock Console
airlock.com
Header image

December 2025 Changelog

Features

Getting started - minimal Auth flow setup (Business improvement)

completed: 16.12.2025

The Getting started configuration now supports several minimal authentication flow options for a first Tenant IAM setup. SaaS Admins can start with username / password using an email address as username, passwordless authentication, or email OTP. This makes it faster to configure and test a basic sign-in experience for an application.

For details see:

Restrict Egress Network Traffic (Security improvement)

completed: 04.12.2025

Tenant IAMs can now restrict egress traffic by explicitly allowing only the external destinations they need. This reduces the risk of unintended data exposure while still supporting required integrations. SaaS Admins can define these destinations more precisely for the relevant modules of a Tenant IAM.

For details see:

Operations

PostgreSQL service-level backup and restore (Operation improvement)

completed: 05.12.2025

Airlock SaaS now has stronger service-level backup and restore capabilities for PostgreSQL databases used by the Management Platform and runtime services. This improves resilience by making recovery from failures more controlled and auditable. It also adds tested restore procedures and safeguards around critical database infrastructure.

MongoDB service-level backup and restore (Operation improvement)

completed: 18.12.2025

Airlock SaaS now includes service-level backup and restore capabilities for MongoDB-based configuration data. Backups can be created regularly, monitored, and validated so recovery is more reliable when needed. This improves resilience and strengthens operational readiness for configuration data handling.

Secure Environment for PII processing (Operation improvement)

completed: 08.12.2025

Airlock SaaS operations for sensitive data now run in a tightly controlled environment with audited access and hardened handling processes. This improves traceability and reduces the risk of mistakes or unauthorized interference during critical work by Airlock DevOps staff. The result is a more secure operating model for data-processing activities.