ComposableStack.AI CDP
Back to agent
Constraintconstraint.aep-destinations-per-sandbox-100

AEP Maximum Destinations Per Sandbox — 100 (System-Enforced)

Adobe Experience Platform enforces a hard limit of 100 destination instances per sandbox. System-enforced — AEP blocks creation of the 101st destination. Organizations building multi-channel activation architectures with AEP Real-Time CDP must account for this ceiling when designing their destination catalog. Multi-sandbox strategies become architecturally necessary for enterprise organizations whose activation surface exceeds 100 distinct endpoint connections (e.g., regional separation, business unit isolation, channel diversification across email, paid-media, CRM, streaming, analytics, and personalization destinations).

confidence 85%v1reviewed May 27, 2026aep, destinations, sandbox, system-limit, multi-sandbox, activation-architecture

AEP Maximum Destinations Per Sandbox — 100 (System-Enforced)

What it is. Adobe Experience Platform enforces a hard limit of 100 destination instances per sandbox. Unlike performance guardrails (such as the 250-audience-per-destination recommendation), this is a system-enforced ceiling: the platform prevents creation of a 101st destination within a single sandbox.

Scope. Applies to all destination types in AEP Real-Time CDP — streaming destinations, file-based batch destinations, email destinations, paid-media destinations, analytics destinations, personalization destinations, and cloud storage destinations. Each configured destination connection counts against this limit regardless of its type or activation volume.

Architectural implication. For most mid-market organizations (10–30 active destinations), this limit is not binding. For enterprise organizations with complex, multi-channel activation stacks — regional separations (EMEA / APAC / AMER sandbox isolation), business unit siloing, or organizations with many specialized channel tools — the 100-destination ceiling requires deliberate destination catalog management and, in some cases, a multi-sandbox strategy.

Multi-sandbox note. AEP's sandbox architecture allows organizations to maintain multiple production sandboxes (depending on their contract tier). If the activation surface genuinely exceeds 100 destinations, the standard architectural response is to distribute destinations across sandboxes by region, business unit, or channel category — not to consolidate all destinations into a single sandbox and risk hitting the ceiling.

Where the agent should surface this. When a user describes a large AEP activation stack with 50+ active destinations, or when recommending AEP for an enterprise organization with complex multi-region or multi-brand activation requirements, surface this constraint as an architectural planning consideration. Ask: "How many distinct destination connections do you expect to maintain in production? AEP enforces a system limit of 100 per sandbox."

Sources

Related

← Referenced by

  • governed-byarchetype.aep-heavy-enterprise-evaluating-composable— OC-078. The 100-destinations-per-sandbox system-enforced limit is an enterprise-scale architectural constraint for AEP-heavy evaluators: multi-brand, multi-region, or highly diversified channel stacks — exactly the enterprise scale this archetype represents — can approach this ceiling. Multi-sandbox strategy is an architectural response that affects the evaluation of composable alternatives (which avoid the sandbox limit by activating from the CDW directly).