descant.cloud vs Terraform

It's hard to compare with Terraform, as descant.cloud is de facto a control plane and not only infrastructure as a code tool.

Terraform allows you to define reusable modules that other teams or end-users can use, but even if module is reusable, it's up to to end consumer to establish proper provider settings, manage the state and perform change management process.

descant.cloud being a control plane doesn't require end users to worry about the state or provider configuration. By design, when devops/infrastructure team develops a set of blueprints, they provide all required settings and entities that end users can use to provision cloud sources they desire.

Moreover, descant.cloud continuously monitors the state of resources and entities, and if any change is detected, it will automatically apply the desired state, avoiding drifts and ensuring that resources are always in the desired state.

This way it saves you time and effort on developing end-to-end release process that is needed when using Terraform.

Use Terraform... in descant.cloud

If you have a large codebase of existing Terraform modules, don't worry - you can still use them in descant.cloud, as blueprints can include a special Terraform resource.

By using that resource you can paste a Terraform code and descant.cloud will execute it as a part of the blueprint. This way you can reuse your existing code and benefit from descant.cloud features like relations between entities, monitoring, and self-service capabilities, as well as smoothening the migration process.