Skip to content
Beta

STACKIT Workflows

In 1 trail

Last updated on

STACKIT Workflows provides a managed Apache Airflow platform for orchestrating Directed Acyclic Graphs (DAGs) without managing underlying servers.

Service Overview

Section titled “Service Overview”
  • Noops Airflow Operations: Handles deployment, security updates, and maintenance automatically.
  • Pipelines as Code: Author pipelines in Python with full Git version control integration.
  • Isolated Execution: Executes pipeline tasks inside dedicated, isolated Kubernetes pods for maximum security.

Technical Details

Section titled “Technical Details”
  • Scaling Architecture: Automatically scales execution pods based on workload demands.
  • Identity & Observability: OIDC identity provider integration and native connection to STACKIT Observability.
  • Digital Sovereignty: Operates entirely within European data centers ensuring full GDPR compliance.

Roles

Section titled “Roles”

The values below come from the STACKIT documentation and update themselves.

From the STACKIT docsConcepts › STACKIT Portal rolesSource updated 03.06.2026 · copied 05.10.2026

The following roles are available in the STACKIT Portal for managing Workflows instances:

  • Workflows Admin: Full administrative access to all STACKIT Workflows resources.
  • Workflows Editor: Permissions to create, modify, and manage STACKIT Workflows sub-resources (DAGs repository, identity provider configuration, etc.).
  • Workflows Reader: Read-only access to all STACKIT Workflows resources.

These permissions are managed through the STACKIT Portal and STACKIT API.

What is this?

This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.

From the STACKIT docsConcepts › Airflow UI rolesSource updated 03.06.2026 · copied 05.10.2026

The permissions inside the Airflow UI are separate from the access control in the STACKIT Portal. Access to the Airflow UI is managed through Role-Based Access Control (RBAC) using your connected Identity Provider (IdP).

When users log in, their roles are extracted from the authentication token provided by the IdP. These roles determine what users can access and perform within the Airflow interface. For detailed configuration instructions, see the Identity Provider section.

The following roles are available within Airflow:

  • Admin: Complete access to all Airflow features, settings, and configurations.
  • User: Can view and trigger DAGs, but cannot modify system settings or configurations.
  • Viewer: Read-only access to view DAGs and their running statuses.
What is this?

This section is copied from the STACKIT docs automatically, several times a day. It cannot be changed here. Changes belong in the STACKIT docs.

Limitations & Constraints

Section titled “Limitations & Constraints”
  • Fixed Role Models: Custom internal Airflow RBAC roles cannot be defined.
  • Flavor Scaling Boundaries: Task concurrency and DAG worker limits are capped by the chosen instance flavor size.
  • Deployment Mechanics: Direct SSH or manual file uploads are blocked; DAG code must be synced via Git or storage.
STACKIT documentation docs.stackit.cloud STACKIT Workflows Overview Open the documentation
Asset historyActive 2 of the last 12 weeksTMUpdatedNo updates · 1 bar = 1 week i
Maintainers
  • ?Name not public?Name not publicThe Cloud Framework team knows who this is. The name is not shown on the site.
TMTobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 12 of the last 12 weeks · 168 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172??Name not publicThe Cloud Framework team knows who this is. The name is not shown on the site.Contributed in STACKIT

  • Tobias M.Tobias M.Head of STACKIT Cloud Framework · STACKITOwnerActive 12 of the last 12 weeks · 168 updatesSTACKITwww.linkedin.com/in/tobias-müller-011304172 · Oct 5, 2026

  • Name not public?Name not publicThe Cloud Framework team knows who this is. The name is not shown on the site. · Sep 9, 2026