The discussion around building integrations for SaaS applications often leads developers to consider whether to construct everything in-house or use an embedded Integration Platform as a Service (iPaaS). While technically feasible, creating the infrastructure necessary for integrations involves more than just coding; it requires significant attention to infrastructure, maintenance, and user interface aspects. Developers must consider compute resource provisioning, deployment processes, scaling, integration activation, and configuration experiences for customers. OAuth 2.0 management, webhook infrastructure, event scheduling, logging, monitoring, and alerting are crucial components that necessitate comprehensive infrastructure. Security, testing, versioning, and compliance with regulations like HIPAA or GDPR further complicate the process, adding to the operational and financial burdens. While a skilled team can build the necessary infrastructure, the costs and efforts associated with maintaining robust systems often make embedded iPaaS a more attractive option, offering pre-established frameworks that alleviate the extensive work involved in development and maintenance.