Buy information about the storage-to-compute adjacency through a capacity- and loss-capped beta, while preserving the ability to stop before broad fixed commitments.
Confidence
Moderate
What happened
Amazon launched EC2 in beta as external compute, later opened the beta to all developers and added instance types, and moved EC2 to general availability with a regional service-level commitment.
The cutoff recommendation favored a bounded compute beta because S3 and developer-interest signals justified learning while standalone economics and fixed-capacity requirements remained unknown. The observed beta-to-open-beta-to-general-availability sequence is directionally consistent with that process. Later segment success supports the plausibility of the platform mechanism but does not prove that the exact initial capacity, pricing, timing or investment envelope was optimal.
Launch a bounded beta with explicit cohort, contribution, reliability, support and capital gates; expand access and scope only as evidence clears those gates.
A limited launch converts an adjacency thesis into customer and operating evidence while preserving the option to stop before broad fixed commitments.