Skip to content
Products
Platform
Developer Tools
Portal

Welcome to the STACKIT Docs

Everything you need to build, deploy, and scale your applications. The Docs offer comprehensive guides, technical references, and practical tutorials to help you make the most of the STACKIT cloud services.

Discover

Getting started

Learn the essential first steps to get started within the cloud, creating and managing your STACKIT resources.

Products

Explore our cloud-based products and services, including databases, computing, AI and more.

Platform

Understand the essentials of cloud management and governance, from IAM and billing to resources, and regions.

Developer Tools

Leverage our developer tools to build, automate, and scale your cloud infrastructure.

Products

Featured Pages

First MongoDB Flex Instance

Set up a first MongoDB Flex instance with a step-by-step guide. Learn to create an instance, connect to it, and perform basic database operations.

STACKIT CLI User Guide

Manage STACKIT services with the command-line interface. The guide covers installation, configuration, and authentication to start automating cloud infrastructure.

STACKIT University

Explore cloud enablement training for STACKIT Cloud and the sovereign ecosystem. Access an extensive range of courses on the learning platform.

STACKIT Calculator

Get full cost transparency for your cloud services. Calculate cloud architectures quickly and receive meaningful cost indications without hidden surprises.

Developer Tools

STACKIT CLI

Configure and manage services from the command line.

STACKIT Go SDK

Accelerate development by interacting with APIs in Go.

STACKIT Python SDK

Simplify daily development work using APIs in Python.

STACKIT Java SDK

Integrate APIs into your Java development workflow.

STACKIT Terraform Provider

Define, reuse, and share infrastructure as code.

STACKIT API

Access the fully integrated API ecosystem.

For partners

STACKIT Marketplace

Explore ready-to-use third-party solutions hosted on STACKIT Cloud. Access modern applications and services to extend your cloud capabilities seamlessly.

STACKIT Partner Portal

Expand your business opportunities through the STACKIT Partner Program. Build successful collaborations and leverage our cloud platform to grow together.

Latest Updates

  • announcementlogging-and-monitoring

    STACKIT Logs is now available in region eu02

    Section titled “STACKIT Logs is now available in region eu02”

    STACKIT Logs is now available in the eu02 region.

    You can now provision and manage STACKIT Logs directly in eu02 to keep log aggregation close to your regional workloads.

    Key highlights

    Section titled “Key highlights”
    • Multi-region deployments: Deploy logging infrastructure across multiple regions to support high-availability architectures and disaster recovery strategies.
    • Lower latency: Ingest and query logs within the same region as your compute and application workloads in eu02.
    • Local data residency: Store and process log data in eu02 to meet compliance and data locality requirements.
    • Full feature parity: Access all STACKIT Logs capabilities in eu02, including access policies, pattern extraction, custom retention periods, and integrations with Grafana, Grafana Alloy, Fluent Bit, and OpenTelemetry.

    Get started

    Section titled “Get started”

    You can select the region when creating an instance in the STACKIT Portal, using the STACKIT CLI, or through the API.

    To learn how to set up an instance, refer to Create your first STACKIT Logs instance.

    Our Help Center is always at your disposal if you have any questions.

  • featurelogging-and-monitoring

    Access policies are now available for STACKIT Logs

    Section titled “Access policies are now available for STACKIT Logs”

    You can now configure access policies on your STACKIT Logs instances to manage read and write access.

    What are access policies?

    Section titled “What are access policies?”

    Access policies let you control who can access your Logs instance. Instead of creating and sharing separate access tokens, you can directly grant your existing service accounts permission to read or write logs.

    Key benefits

    Section titled “Key benefits”
    • Reduced operational overhead: Removes the need to create and manage separate, instance-specific access tokens. You can reuse your existing service accounts.
    • Improved security: Replaces static, long-lived instance access tokens with short-lived access tokens obtained through your service account keys.

    Availability and usage

    Section titled “Availability and usage”

    Access policies are available through the HTTP API and the STACKIT SDK. Support in the STACKIT Portal, the STACKIT CLI, and the STACKIT Terraform Provider will soon follow.

    For step-by-step instructions on how to use a service account to send logs to an instance, refer to our OpenTelemetry Collector guide.

    Our Help Center is always at your disposal if you have any questions.

  • changeddeveloper-platform

    Forgejo Runner v13: changes that can break your workflows

    Section titled “Forgejo Runner v13: changes that can break your workflows”

    We have upgraded the runners of STACKIT Git to Forgejo Runner v13. This release makes expression evaluation stricter, removes legacy workflow commands, limits registry credentials to the job that declares them, and removes the remaining Gitea compatibility. Several cases that used to log a warning now fail the run, so check your workflows for the changes below.

    Invalid expressions and matrices fail the run

    Section titled “Invalid expressions and matrices fail the run”

    An expression that cannot be evaluated, such as a format() call with fewer arguments than its format string references, now fails the step or job instead of logging a warning. Attempting to exclude a value from a matrix that was never defined in that matrix now causes an error and prevents the workflow from running.

    Check the expressions and matrix definitions in your workflow files.

    Legacy workflow commands are removed

    Section titled “Legacy workflow commands are removed”

    The ::set-output, ::set-env and ::add-path commands no longer have any effect, and ACTIONS_ALLOW_UNSECURE_COMMANDS does not enable them again. Write to the environment files instead:

    • Replace echo "::set-output name=var::value" with echo "var=value" >> "$FORGEJO_OUTPUT".
    • Replace echo "::set-env name=VAR::value" with echo "VAR=value" >> "$FORGEJO_ENV".
    • Replace echo "::add-path::/custom/bin" with echo "/custom/bin" >> "$FORGEJO_PATH".

    Registry credentials are declared per job

    Section titled “Registry credentials are declared per job”

    The runner no longer logs in to registries with the DOCKER_USERNAME and DOCKER_PASSWORD secrets, because these credentials could be sent to a registry they were not meant for. If a job uses an image from a private registry, declare the credentials in that job:

    jobs:
      build:
        container:
          image: private.registry.example/app:latest
          credentials:
            username: ${{ secrets.REGISTRY_USER }}
            password: ${{ secrets.REGISTRY_TOKEN }}

    Gitea compatibility is removed

    Section titled “Gitea compatibility is removed”

    The ${{ gitea.* }} context is no longer supported. Replace it with ${{ forgejo.* }} in your workflows.

    Steps no longer run in a terminal

    Section titled “Steps no longer run in a terminal”

    The runner no longer attaches a terminal to the output of a step. Commands that print colors only when they detect a terminal now print plain text. To get colored output again, set FORCE_COLOR=1. Commands that require a terminal will now fail. For example, replace docker run -it with docker run -i.

    If you operate your own runners

    Section titled “If you operate your own runners”
    • Docker Engine 25.0 or later is required. We recommend 28.0.1 or later, because earlier versions can fail to create IPv6 networks with Forgejo Runner v13.
    • The GITEA_DEBUG, GITEA_TRACE, GITEA_RUNNER_CAPACITY, GITEA_RUNNER_FILE, GITEA_RUNNER_ENVIRON and GITEA_RUNNER_ENV_FILE variables are ignored. Remove them from your runner configuration and environment.
    • The container.network_mode option is removed. Use container.network instead.

    For more details, see the release announcement of Forgejo Runner v13.0 and the release notes of Forgejo Runner.

    If you have any questions, feel free to contact our Help Center.

See all release notes