Where you can ship today
One canvas, swap the target cloud. ICE is built around a graph engine that does not know about specific clouds. Each provider has its own deployer.
Most mature deployer. Create, update, delete with live progress streaming for every service.
Major primitives deploy today. The rest is moving in pieces.
Major primitives deploy today. AWS-parity gaps are the next push.
Blocks render on the canvas. The deployer is the next slice.
Droplets, App Platform, Managed DBs, Spaces.
OCI compute, OKE, autonomous DB.
CVM, TKE, COS, Pulsar.
Helm charts and raw manifests as a deployer target.
20 service handlers across 9 categories. All of them support create, update, and delete, with live progress streamed back to the canvas.
| Category | Services |
|---|---|
| Compute | Cloud Run (services + jobs), Cloud Functions, GKE |
| Database | Cloud SQL (PostgreSQL, MySQL), Firestore, Memorystore Redis |
| Storage | Cloud Storage |
| Messaging | Pub/Sub, Cloud Scheduler |
| AI / ML | Vertex AI (LLM endpoints, Vector Search, ML models) |
| Analytics | BigQuery, Discovery Engine |
| Security | Secret Manager, Identity Platform |
| Networking | API Gateway, Load Balancer, Domain Mapping |
| Observability | Cloud Logging |
Concepts compile to high-level resources, then per-provider handlers translate those into native SDK calls. The graph engine never imports a cloud SDK. That separation is what makes provider migration mechanical instead of a rewrite.
Implement the deployer interface in packages/providers/<cloud> with create / update / delete handlers per service. The blocks layer is shared. Open an issue or PR to coordinate.