Infrastructure as Code

Click to provision.Terraform written, reviewed and kept in sync.

Codeface gives every engineer a visual control plane for cloud infrastructure — and gives your platform team clean, reviewable code in the repository they already trust.

100%
changes backed by IaC
0
Terraform expertise required
Git
native code & state
codeface.aezona.com
Designer
Provider
AWS · us-east-1
main.tf · generated
required_version = ">= 1.8.0"
required_providers {
aws = {
source = "hashicorp/aws"
version = "~> 5.84"
}
}
region = "us-east-1"
environment = "prod"
managed_by = "codeface"
resource "aws_db_instance" "app" {
engine = "postgres"
PR #418 opened · infra/prod

What Codeface does

Design and change resources through the UI. Codeface generates clean Terraform, keeps it in Git, detects drift, and reconciles the real world back to code.

Visual resource designer

Compose VPCs, clusters, databases and networking across AWS, Azure and GCP on one canvas — with provider-aware validation before anything is written.

Terraform written for you

Every UI action produces formatted, idiomatic HCL using your module conventions. The code is the artefact — Codeface never holds state you cannot read.

Pull-request workflow

Changes land as a branch and a PR in your own repository, with a plan output attached. Existing review and CI gates apply unchanged.

Drift detection

Continuously compares real infrastructure against committed code, flags what diverged, and offers to reconcile in either direction.

Scoped access and approvals

Developers request, operators approve. Role-based permissions decide who can plan, who can apply, and which environments they can touch.

Curated module library

Publish your organisation's hardened modules as one-click templates so a compliant EKS cluster is the default path, not the difficult one.

How it works

01

Point Codeface at your repository

Connect the Git repository that holds your infrastructure code and the cloud accounts it manages. Codeface imports existing resources and reads your module structure.

02

Design or change a resource in the UI

Pick a provider, choose a template or start from a blank resource, and fill in the fields. Validation runs live against provider constraints and your own policy.

03

Review the generated code and plan

Codeface writes the HCL, opens a branch and attaches the Terraform plan. Nothing has touched your cloud yet — you are reviewing code, as usual.

04

Merge to apply

Approve the pull request and your pipeline applies it. Codeface records the resulting state and starts watching that resource for drift.

Developer self-service

Engineers spin up compliant staging environments through the UI without learning HCL or waiting on a platform team ticket.

Adopting IaC on a live estate

Import resources that were created by hand, generate the code that describes them, and take ownership of it incrementally.

Governed production change

Every production change arrives as a reviewable pull request with a plan attached — approval gates enforced by the platform, not by convention.

Common questions

Does Codeface lock me into its own format?

No. Codeface writes standard Terraform into your repository. If you stop using it tomorrow, you keep working code and state exactly as they are.

What happens to resources someone changed in the console?

Drift detection catches them. Codeface shows the difference between the live resource and the committed code, and lets you either import the change or revert it.

Can it manage all three clouds at once?

Yes — AWS, Azure and GCP resources can live side by side in the same workspace, with per-provider credentials and per-environment access rules.

See Codeface against your own cloud.

Open the live workspace. A demo estate is already connected — design a resource, watch Terraform appear, and reconcile drift without a canned video.

Launch the workspace