ICE building blocks
The 28-concept palette. Provider-neutral primitives you drop on the canvas. Each one compiles to a real service per cloud.
A long-running service that auto-scales on load.
Background worker that consumes a queue.
Single-purpose function billed per invocation.
Server-side rendered site with auto-scaling compute.
Pre-built static assets behind a CDN.
Managed PostgreSQL.
Managed MySQL.
Document database.
In-memory cache and pub/sub.
Bucket for files, media, backups.
Embeddings store for retrieval and search.
HTTPS load balancer or edge router.
VPC, subnets, internal routing.
Auth, throttling, routing for HTTP APIs.
DNS, TLS, hostname binding.
Each concept advertises what it needs. A Scalable Backend wants a GitHub Repo or Object Storage for code, plus Public Traffic if it serves the open internet. The canvas validator surfaces a badge on any block whose requirements are unmet, and blocks the deploy when something hard is missing.
A new concept is six files: definition, blueprint, info, a high-level resource mapping, a per-provider handler, and a node renderer. Use static-site as a reference and open a PR.