Introduction

Welcome to Humanitec’s documentation. This section explains how to interact with and operate platforms built with Humanitec. If you are a developer and your platform engineering team has built a platform, this is the optimal starting point; otherwise, if you are evaluating or tasked to set up your platform using Humanitec’s products, check see Build a platform.

Why Humanitec

If you are building cloud native applications, a platform built using Humanitec’s products allows you to configure and ship confidently, independently, and fast. Humanitec applies the approach of dynamic configuration management. This means that application and infrastructure configurations are generated with every git-push by applying abstract requests (workload specifications) to baseline configurations provided by the platform engineering team.

This means that as a developer, you only have to maintain and operate one configuration file per workload. The “localization” to the Environments you deploy into is done at deployment time.

This provides a number of benefits to you as an individual contributor:

  • Reduces configuration overhead, no need to maintain varying formats, including local and cloud configurations.
  • Reduces likelihood of deploying workloads with faulty dependencies or unsecure, non-compliant configs.
  • End to end self-service capabilities to reduce dependencies from other teams and waiting times, such as the ability to add resources like databases, file storage, or DNS.
  • Full visibility into what’s running where and in what Environment.
  • A magnitude of new functionalities made possible with dynamic configuration management, including:
    • The ability to spin up ephemeral or PR environments.
    • Diff functionality to understand and debug deployment changes.
    • Precise, on-point rollbacks.

This approach does add a layer of abstraction in comparison to traditional ways of working. Those abstractions are however, “opaque”. Assuming individual contributors have the authority to do so (depending on your organization’s RBAC settings). Your platform team can configure both application and infrastructure configurations down to the lowest level.

Top