I Built Mantis, to unify Terraform and Helm using CUE

#1

Post by pdasika » Thu, Oct 24, 2024, 5:50 PM UTC

I Built Mantis, to unify Terraform and Helm using CUE
mantis.getaugur.ai

Re: I Built Mantis, to unify Terraform and Helm using CUE

#2

Post by pingali » Thu, Oct 24, 2024, 6:05 PM UTC

TF is currently the most popular framework (along with OpenTofu). Can the heavy TF users/engg here share a quick assessment of TF and Mantis for managing complex deployments?

Re: I Built Mantis, to unify Terraform and Helm using CUE

#3

Post by Rohitjjw » Thu, Oct 24, 2024, 6:16 PM UTC

TF are super complex and that why Pulumi and CDKs exists. They have their own complexities. Would be nice to see how Mantis deals with those issues.

Re: I Built Mantis, to unify Terraform and Helm using CUE

#4

Post by pdasika » Thu, Oct 24, 2024, 7:05 PM UTC

Rohitjjw wrote: post #3

TF are super complex and that why Pulumi and CDKs exists. They have their own complexities. Would be nice to see how Mantis deals with those issues.

Mantis takes a unique Makefile-style approach to task setup and execution. It addresses a key challenge: infrastructure-as-code (IaC) often does not need a Turing-complete language like TypeScript or Go, which tools like Pulumi and cdktf rely on. These languages, while powerful, can add unnecessary complexity to infrastructure management.

With Mantis, the focus is on simplicity and correctness through CUE, a superset of JSON, which is easy to learn and use. It offers templating, modularity, and policy enforcement within a single language, eliminating the need for separate tools like OPA or Rego for policy assertions. Mantis enables users to build task graphs with clear dependencies and ensures infrastructure consistency without introducing multiple abstraction layers.

By simplifying the IaC workflow while still maintaining flexibility, Mantis provides a lightweight yet powerful alternative to Pulumi and cdktf—one that reduces complexity without sacrificing expressiveness or control.