MULTI-CLOUD · SAME ROLE, DIFFERENT SEMANTICS
Cloud Service Matcher
Map a service category from one cloud to another across AWS, Google Cloud, Azure and OCI, and see which pairs differ in ways that break a straight migration.
Your experiment
Start with a private network moved from AWS to Google Cloud. Read the difference, then move it to Azure and OCI, and try serverless functions, message queues, secrets and access control between different pairs.
Every input recomputes the result immediately; there is no animation because nothing here unfolds over time. An input outside its allowed range is rejected with a message and the previous valid result stays on screen.
What to check
Computed data
Metrics
Service names are current to the author's knowledge in 2026 and were not re-checked against each provider's documentation for this page; providers rename and merge services, so confirm the names there before a migration. A category with no recorded difference is not a guarantee of compatibility: limits, pricing, regional availability and APIs still differ. The recorded differences are structural ones that change a design, not feature lists.
Same role, different names
Most cloud building blocks have a counterpart on each provider; the Service category control picks which one is mapped. Object storage is Amazon S3, Cloud Storage, Azure Blob Storage and OCI Object Storage. The table lists 17 categories across AWS, Google Cloud, Azure and OCI. Choose a category and a pair of providers, and the result says whether a structural difference recorded for that category applies to the pair. Object storage from AWS to Google Cloud gives NO RECORDED DIFFERENCE.
The network example
A private network from AWS to Google Cloud gives CHECK SEMANTICS. A Google Cloud VPC network is global, with subnets in each region, while an Amazon VPC is regional; a design with one network spanning regions on Google Cloud becomes several peered networks on AWS, with different routing and firewall rules. From AWS to Azure or OCI, all regional, the difference does not apply and the result is NO RECORDED DIFFERENCE.
Differences that change a design
Of the 17 categories, 8 have a recorded difference. Lambda runs one request at a time per execution environment while Cloud Run functions can serve several concurrently. Pub/Sub is a publish-subscribe service rather than a queue like SQS. Azure Key Vault and OCI Vault keep keys and secrets together, while AWS and Google Cloud split them. Access control models differ between every pair, and NoSQL databases differ in data model, so both are flagged for any pair.
Using the result
CHECK SEMANTICS does not mean the move is impossible; it means the straight one-to-one mapping will behave differently and the design needs a second look. NO RECORDED DIFFERENCE means only that this catalogue records no structural difference for the pair. Moving the same provider to itself gives SAME PROVIDER. For a real migration, list the features you depend on and test them on the target, starting with identity and networking.
Reading the tool and its limits
The lanes show the mapping, the difference that applies and the size of the catalogue, the table lists every category with its four services, and the text panel explains what to check. The catalogue is deliberately small and covers widely used managed services only; specialised services, regional availability, limits and prices are outside it, and product names change, so confirm them in each provider's documentation.