Hi Pipedream Team,
We are currently architecting an advanced integration layer within our product, designed to serve as a “Super App” trigger experience for our end users. Our goal is to provide seamless, user-specific integrations (mapped to External User IDs) where we programmatically provision and manage dedicated event listeners—such as “New Email” triggers—on behalf of our customers.
We have been successfully prototyping with the standard API and CLI, specifically focusing on custom component publication and source instantiation. However, as we move from basic registry components to dynamic, custom-wrapped sources designed for this multi-user orchestration, we are encountering persistence and instantiation errors that suggest we are hitting the limits of the standard API’s intended scope.
Given that we aim to scale this to manage thousands of isolated, user-specific triggers programmatically, it appears our requirements align more closely with an Enterprise or Embedded Partner solution. We are effectively building an orchestration layer that leverages Pipedream as the robust underlying infrastructure.
Could you please connect us with the right team to discuss the architectural best practices and licensing requirements for this level of programmatic, white-label usage? We are looking to move past these initial friction points and establish a stable, scalable foundation for our integration features.