Overview
The Humanitec products play a well-defined role in the context of an Internal Developer Platform. At the same time, they are extremely flexible and can be used to solve many different problems, from deployment to infrastructure provisioning to security, governance, observability, and more.
There are a number of existing tools and technologies that overlap with, or complement, the capabilities of the Humanitec products. In this section, we offer a comparison to a range of well-known tools. You will find that, as a rule, the Humanitec products are not mutually exclusive with other technologies.
The tooling classification is based on the Platform Engineering tooling landscape .
See how the Humanitec products relate to:
What Humanitec is not
The Humanitec products focus on orchestrating the deployment of workloads and their associated infrastructure. This means:
-
Humanitec is not a Platform-as-a-service (PaaS). It does not run your workloads. It helps you get them running in your infrastructure along with any required resources. The Humanitec Platform Orchestrator is operated as a cloud-based SaaS solution.
-
Humanitec is not a Kubernetes cluster management tool. It relies on existing clusters to be available as a target for workload deployments, and to run resource provisioning jobs. It can manage cloud-based resources which are bound to the lifecycle of applications to facilitate full developer self-service.
-
Humanitec is not an Internal Developer Portal, it may complement one. Its own Humanitec Portal is designed for working specifically with the Humanitec Platform Orchestrator, with the Orchestrator being the backend of your Internal Developer Platform. See the comparison with Developer Portals for a deeper discussion.
-
Humanitec is not a CI/CD system. It integrates with your existing CI/CD setup at well-defined extension points. Its own deployment capabilities for workloads and accompanying cloud resources are ususally triggered externally, driven by your overarching CI/CD flow.