Back to agent
Tradeofftradeoff.data-egress

Data Egress

How freely data can leave the CDP/CDW. Packaged CDPs govern egress by license terms; composable stacks govern only by raw infrastructure cost.

confidence 95%v1reviewed Apr 26, 2026packaged-vs-composable, data-liquidity, governance

Data Egress

Packaged end. Egress is strictly governed by KB limits tied to licensing (e.g. AEP's 500 KB and 1500 KB caps). Exceeding the limits requires renegotiating contract terms.

Composable end. Egress is governed only by raw compute and network egress costs. Pay for what you query.

What it determines. Whether the customer can confidently treat the CDP as the upstream source for their wider data ecosystem (analytics, ML, finance), or whether they must architect around the CDP as a destination only.

The honest framing. Packaged vendors aren't acting capriciously — they're protecting compute and storage economics by preventing pass-through use. But for a customer who's already paid the platform license, the limits feel like a toll on accessing their own customer data (source.packaged-vs-composable-md).

Sources

Related

This node →

← Referenced by