IaCTranslate

Any inventory in.
Any cloud out.
A migration platform.

The AI migration platform that turns a company's existing infrastructure inventory — VMware, Hyper-V, Kubernetes, a CMDB, or an existing cloud fleet — into production-ready, provider-validated IaC (Terraform, Pulumi, CloudFormation, Bicep, CDK, or Kubernetes) for AWS, Azure, GCP, OCI, or DigitalOcean. It assesses the estate, recommends the cloud, enforces policy, and explains every decision.

VMwareHyper-VKubernetesCMDBCloud ──▶ IaCTranslate ──▶ AWSAzureGCP
Investor & client overview · figures marked ⚑ are illustrative placeholders
The problem

Cloud migration is manual, slow, and rigged toward lock-in.

Weeks of hand-work

Infra engineers hand-translate discovery reports into IaC, VM by VM. Expensive, error-prone, hard to audit.

Estates are messy

No company is only VMware. It's Hyper-V + physical + legacy + a CMDB + an existing cloud footprint.

Vendor tools lock you in

AWS/Azure/Google migration tools are single-cloud, emit no portable IaC, and will never recommend a rival cloud.

So teams either pay consultants for months, or accept whichever cloud the tool was built to sell.

The solution

Exported inventory → deployable IaC, plus an unbiased cloud recommendation.

  • Secure by design. Works entirely from exported files — never connects to the customer environment. Runs offline, no keys.
  • Not "an LLM writes Terraform." A deterministic engine: AI makes only structured decisions; templates emit the .tf; a validation layer re-checks everything — and the plan always records honestly which engine actually ran.
  • Reproducible & auditable. Output is provider-validated HCL — proven in CI, not a demo. Every decision carries a reason and a confidence score.
  • Days of engineering → minutes. Upload, assess, recommend, generate, download a ready-to-apply project.
How it works

One deterministic pipeline. Two swappable registries.

parsenormalize → agents(classify → rightsize → network) → validatepolicy → render → package

Sources (input) · 5

VMware · Hyper-V · Kubernetes · Generic CMDB · Cloud fleet — auto-detected. The generic reader ingests any spreadsheet with no bespoke parser.

Targets · 5 clouds × 6 IaC formats

AWS · Azure · GCP · OCI · DigitalOcean — each a catalog + tier mapping + templates. Terraform on all five; Pulumi/CloudFormation/Bicep/CDK/Kubernetes where built. New clouds slot in without touching the pipeline — OCI and DigitalOcean proved it, including one with a genuinely different network model.

The AI is optional and behind an interface — it defaults to a deterministic rule engine, so it runs offline with zero keys and is fully reproducible. Toggle it on per-run from the CLI, the API, or the web UI; an AI-written executive summary follows automatically when it does.

More than a translator

The whole migration — assess, recommend, plan, govern, ship.

Assess

A pre-migration readiness score (0–100) + risk / cost / data-quality findings — before a resource is provisioned.

Recommend

Unbiased 3-cloud ranking on cost, fit & OS — with a decisiveness call and annualized spend.

Explain

Every instance choice carries a reason and a confidence score — auditable, not a black box.

Govern

A policy engine blocks rendering on org rules — no public IPs, budget caps, approved families, naming.

Report

A client-ready executive report + architecture diagrams, generated with the project.

Ship

Brownfield import for existing fleets, GitOps CI/CD, infra diff, async jobs + audit trail.

Re-platform

Database tiers flagged as managed-DB candidates (RDS / Cloud SQL / Azure SQL); multi-instance tiers auto-fronted by a load balancer.

Sequence

Migration waves ordered by tier dependency and environment risk, with rollback strategy, validation checks, and LB-aware downtime estimates per wave.

AI, on demand

Claude-powered classification & sizing, toggled per-run from the CLI, API, or web UI — with an honest fallback record and an AI-written executive summary when it runs.

Why we win

Source-agnostic. Cloud-neutral. Unbiased.

CapabilityIaCTranslateAWS Migration HubAzure MigrateGoogle Migrate
Multi-source (VMware / Hyper-V / Kubernetes / CMDB / cloud) Yes ✓AgentsAgentsAgents
Portable IaC output (Terraform / Pulumi / CFN / Bicep / CDK / K8s) Yes ✓NoNoNo
Multi-cloud target AWS·Azure·GCPAWS onlyAzure onlyGCP only
Unbiased best-cloud recommendation Yes ✓NeverNeverNever
Assessment · policy governance · reports Built-inPartialPartialPartial
Works from a spreadsheet — no agents Yes ✓NoNoNo

A vendor's own tool will never emit portable IaC or send a customer to a competitor. That structural conflict is our moat.

Proof, not slideware

The product is built — and the output actually validates.

5→5sources → clouds, live
403automated tests
7/7CI jobs green
tofu ✓real provider validate
  • Generated Terraform passes real tofu validate against the actual AWS, azurerm, and google providers — enforced continuously in CI.
  • Shipping today: a CLI, a hardened FastAPI service (sync + async jobs + audit + bearer-token auth + Prometheus metrics), and a Next.js web app — plus assessment, confidence, executive reports, diagrams, infra diff, a policy engine, an Infrastructure-Graph IR, load-balancer topology, managed-DB re-platforming advice, migration wave planning, a persistent SQLite project store, and six IaC formats (Terraform, Pulumi, CloudFormation, Bicep, CDK, Kubernetes).
  • Engineered like a platform: 32 architecture decision records, deterministic + offline + reproducible, non-root Docker, streamed upload caps.
The value, quantified

Same estate, four clouds — cost swung 31%.

OCI · recommended

$3,864/mo

GCP

$4,320/mo

Azure

$4,919/mo

AWS

$5,051/mo

From our 7-VM sample estate — full monthly cost: compute, block storage, Windows licensing and load balancers, at on-demand list price with no committed-use discount assumed. The recommender scores every cloud on cost, sizing fit and OS affinity with published weights — an inspectable number, not a black box. DigitalOcean prices lower still and is excluded: it publishes no Windows image, so it cannot host part of this estate, and a cloud that can't run the workload isn't a cheaper option. On a real 5,000-VM estate that swing is life-changing money — and we surface it before a single resource is provisioned.

Why now

Every enterprise is mid-migration — and multi-cloud is the default.

VMware in flux

Post-acquisition licensing shocks are pushing huge VMware estates to re-platform — right now.

Multi-cloud & repatriation

Teams want portability and leverage, not lock-in. Terraform is the lingua franca.

IaC is standard

Migrations that don't end in version-controlled IaC are no longer acceptable to modern platform teams.

86%actively reducing their VMware footprint
4%have actually finished migrating
73%run hybrid cloud

Almost everyone has started; almost nobody has finished. That gap — 86% moving, 4% done — is the market, and it is measured in estates that still need translating. Gartner puts 2026 public-cloud end-user spend at $850B, up 21% year over year: that is where these workloads are landing, not our addressable slice of it.

Sources: CloudBolt Software survey of 302 North American IT decision-makers, Feb 2026 (86% reducing VMware footprint, 4% fully migrated) · Flexera 2026 State of the Cloud Report, n=753 (73% hybrid cloud) · Gartner, worldwide public cloud end-user spending forecast, 2026 ($850B, +21.3%).
Who buys · how we charge

Sold to the people who run migrations for a living.

Ideal customers

  • Cloud consultancies & MSPs
  • Enterprise IT & platform teams
  • Cloud-migration specialists · SIs

Beachhead: US mid-market consultancies

Business model ⚑

  • SaaS — per-project & per-seat tiers
  • Enterprise — self-host, SSO, audit, volume
  • Land with a single migration, expand across the portfolio

⚑ Pricing to be validated with design partners

Where we are · where we go

Platform shipped. The next slices make it enterprise-operable.

Done — today

  • 5 sources → 5 clouds · 6 IaC formats (TF · Pulumi · CFN · Bicep · CDK · K8s)
  • Assessment · recommendation · confidence · reports · diagrams · diff
  • Load-balancer topology · managed-DB re-platforming advice · migration waves
  • Policy engine · brownfield import · GitOps · async jobs + audit
  • Persistent SQLite store + audit trail (survive restart) · bearer auth · Prometheus /metrics

Next

  • Postgres + object storage + durable job queue (Redis/Celery)
  • OIDC/SSO + orgs/teams + RBAC roles
  • Notifications, ticketing (Jira/ServiceNow)

The runtime seams for scale — jobs, events, audit, a store behind one interface — already exist, and a SQLite-backed store + bearer auth are shipped stopgaps proven with a live kill-and-restart. v2.1/v2.3 swap them for Postgres · Redis · object storage · OIDC without an API rewrite.

The ask

Let's translate the enterprise to the cloud — on the customer's terms.

⚑ Raising: seed / pre-seed Seeking: design-partner MSPs US-first

See it live: the product, the code, and the full documentation are ready to demo today — read the docs · code on request.

⚑ Insert round size, use of funds, and contact details before sharing externally.