iacmpOne codebase. Three clouds.

Describe the infrastructure you need — get TypeScript constructs that synthesize to CloudFormation, Bicep and Terraform, with real deploy, diff, audits and diagrams in a single CLI.

Get started in 5 minutes

Use with Claude Code

GitHub

☁️

One construct, three clouds

Database.SQL becomes RDS on AWS, PostgreSQL Flexible Server on Azure and Cloud SQL on GCP — with the correct network, password and SSL wiring on each.

✅

Validated by real deploys

Every provider went through 20 end-to-end scenarios (deploy → runtime test → destroy) on real AWS, Azure and GCP accounts — not just synth.

🛡️

Synth-time guards

A dozen validations catch, in seconds, mistakes that would cost you a deploy — missing env vars, Lambda in a VPC without endpoints, SQL without SSL, undeclared GSIs.

🤖

Claude Code out of the box

iacmp setup registers an embedded MCP server — your agent writes stacks, synthesizes and deploys through structured tools, all local.

Architecture

iacmp architecture and system flow

30 seconds of iacmp

typescript

import { Stack, Fn, Database, ref } from '@iacmp/core';

const stack = new Stack('ApiStack');

new Database.DynamoDB(stack, 'ItemsTable', { partitionKey: 'id' });

new Fn.Lambda(stack, 'ItemsFn', {
  runtime: 'nodejs20',
  handler: 'index.handler',
  code: 'dist/handlers/items',
  environment: { TABLE_NAME: ref('ItemsTable', 'Name') },
});

export default stack;

bash

iacmp synth --provider aws      # → CloudFormation
iacmp synth --provider azure    # → Bicep
iacmp synth --provider gcp      # → Terraform (tf.json)
iacmp deploy                    # deploys for real, to your account