Aurora Composable: Three Parts, No Fourth

Field notes

Aurora Composable divides its proposed system into a client, a backbone of small cloud functions over key-value storage, and key collections that hold operational decisions. The homepage specifically places tiers, entitlements, governors, limits, and quotas in data rather than code paths, with both client and backend reading those collections at runtime. It also links to separate development and behavior tracks, a key-collections section, methodology comparisons, and a reference platform, though no implementation or pricing is visible in the supplied extract.