From running cloud to canvas
Point ICE at a real cloud account, an IaC repo, or a docker-compose file. Get a canvas that reflects what is actually running, ready to edit, redeploy, or migrate.
45+ importers covering compute, data, networking, AI, observability.
Authenticate with a service account, pick a project, and ICE crawls the resource graph. You get a canvas that reflects what is actually running, including dependencies between services.
Major primitive importers landing in pieces.
Scoped to the resources AWS deployer already understands. Expanding alongside the deployer.
Following AWS, paced by the deployer.
Same shape: every resource type the deployer handles can be imported.
Point ICE at a Terraform state or .tf directory.
Parse providers and resources. Map known resource types to ICE concepts. Surface unmappable resources for manual review.
Same idea as Terraform import, against a Pulumi stack.
Same translation layer in front of a different state format.
docker-compose.yml to canvas, then deploy to any cloud.
Services become Scalable Backends, volumes become Object Storage, depends_on becomes edges. Useful for moving local-dev stacks to production.