Common questions

Question 1

What is an embedded iPaaS?

Accepted Answer

An embedded iPaaS is an integration platform that a B2B SaaS company embeds in its own product, so its customers connect the other apps they rely on without leaving that product.

A modern embedded iPaaS is the foundation for product extensibility. It handles what breaks at scale, gives your developers the tools to build fast, lets your customers extend your product through embedded workflows, and gives their AI agents the tools to take action across connected systems. Productized integrations, embedded workflows, and agentic interaction all run on one platform.

Question 2

How does building integrations in-house differ from using an embedded iPaaS?

Accepted Answer

Building in-house means your team must create not only the integration logic, but also all the infrastructure for each integration and customer. This includes compute resources, integration activation UI for customers, auth management, webhook infrastructure, configuration tools, monitoring tools, and deployment systems. An embedded iPaaS provides all this out of the box so your team can focus on integration logic and the customer experience.

Question 3

Can't we just use AI coding agents to build integrations in-house?

Accepted Answer

AI changes what it costs to write an integration, not what it costs to run one. A capable coding agent will scaffold a connector against an API's docs in an afternoon, which simplifies the work. What it does not create is the platform underneath: compute resources, auth management, webhook infrastructure, configuration tools, monitoring and alerting, deployment systems, and an activation UI your customers use without filing a ticket.

Those are design and operations problems that persist for years after the code is written. Prismatic supplies that layer and points AI agents at the parts they do best, which is why our own connector library is open-source, and our AI tooling builds against it.

Question 4

Why might an in-house integration strategy fail?

Accepted Answer

As integration volume and complexity increase, devs are pulled away from core product work to build new integrations and maintain an ever-growing tech debt stack.

Question 5

What are key benefits of using an embedded iPaaS like Prismatic?

Accepted Answer

Reduced development time and overhead.
Faster time-to-value for customers via onboarding and new integration activations.
Better UX/support self-service since non-devs and customers can handle many integration tasks.
Successful scaling because of the "build-once, deploy many" approach.

Question 6

When might building in-house integrations make sense?

Accepted Answer

If your integration needs are very limited (you have a handful of simple integrations), or your product’s core value is the integration itself, and it makes sense for you and your team to handle the infrastructure and maintenance load of building in-house today and as you scale.

Question 7

Can I keep my existing in-house integrations if I adopt Prismatic?

Accepted Answer

Yes. Prismatic lets you display existing in-house integrations alongside new Prismatic-built integrations in the embedded marketplace. You can maintain those integrations indefinitely, replace them gradually, or adopt another approach based on your needs and resources.

Question 8

How does using Prismatic impact my product roadmap and team focus?

Accepted Answer

With Prismatic, engineering can spend less time on the integration plumbing and more time on core product features and market differentiators. This improved focus leads to better resource alignment, faster innovation, and a product roadmap that includes integrations instead of getting derailed by them.

Question 9

What should I look for when choosing an embedded iPaaS?

Accepted Answer

Key factors include: a vendor focus on customer-facing integrations rather than internal automation; strong developer experience, meaning code-first development with APIs, SDKs, a CLI, and AI tooling that understands the platform; support for low-code and non-developer builders; ability to write custom connectors; an embedded workflow builder your customers can use themselves; multi-tenant deployment; customer self-service; integrations that are callable by AI agents; and extensive monitoring, logging, and operations tooling.

Question 10

How does Prismatic help with customer acquisition, retention, and product differentiation?

Accepted Answer

By enabling you to deliver integrations faster (reducing deal blockers), offer more off-the-shelf integrations, provide self-serve and configurable workflows (enhancing UX), and free up your team to focus on features that differentiate your product. All of that improves win rates, time-to-value, and customer retention.

Question 11

Does Prismatic support customer-specific configurations?

Accepted Answer

Yes. Prismatic enables you to build productized, reusable integrations that can be tailored for each customer. You can deploy a single integration to multiple customers with customer-specific settings, without creating a separate integration for each customer.

		In-House
Number of devs needed	Initially, 1 to 2. Ongoing, 0 to 1. This is common, but will grow for large orgs.	Initially 1 to N. Ongoing, 1 to N.
Time-to-market	Weeks or days.	Months.
AI across the integration lifecycle	AI assistants use Prismatic Skills to scaffold, build, deploy, and test integrations against the platform. Your customers get an AI copilot, and their agents can call your flows as tools.	AI writes integration code faster, but the infrastructure, tenancy model, and customer-facing experience still have to be designed, built, and maintained by your team.
Maintenance ownership	Prismatic handles updates, security, and scaling.	1 or more dedicated DevOps engineers.
Costs	Predictable pricing tied to platform subscription and usage.	Substantial up-front dev, DevOps, and cloud costs. Variable ongoing costs (but usually still substantial).
Reliability	99.99% uptime per SLAs	Varies from really good to not-so-good.
Customer self-service	Marketplace (search and activate), dashboards (configure and troubleshoot), and workflow builder (create one-off workflows).	Usually not a priority. Seen as unnecessary in most instances.
Infrastructure scaling	Autoscaling infrastructure to handle the highs and lows without hiccups.	Varies greatly based on what's been pulled together to support integrations.
Connector library	Pre-built connectors and a custom connector SDK for building more	Custom, from scratch connectors for each system
Support tools	Built-in monitoring logging and alerting tools that are accessible to non-devs and customers.	Not usually included, unless as an afterthought. Engineering bears the support load.
Customization	Provides flexibility (custom connectors, code-first integrations, white-labeling) but encourages standard patterns for efficiency.	Full control, so you can make whatever you wish. But it comes with a steep price and added complexity.
Productized integrations	Focus on making integrations product features. Build once, deploy many.	Integrations often treated as services (one customer, one custom integration) and not usually optimized for reuse or scalability.
Security and compliance	Offloads much of this infrastructure by design.	You are directly responsible for building and maintaining auth, establishing compliance, and implementing security.
Role of non-devs	Can build (low-code designer), deploy, and manage integrations.	Can forward onboarding and support emails to engineering.
Customer onboarding	You can build new integrations for new customers in short order.	If a new integration is required, development timeframes may significantly delay deal closing.
Innovation vs tech debt	Frees up engineering to focus on the core product instead of integration infrastructure and support.	Tech debt is a reality of creating custom integrations as fast as you can.
Churn and retention	Faster onboarding, reliability, and visibility lead to less churn.	When integrations are slow to deploy, unstable, or take much hand-holding, churn risk increases.
Maintenance load	Much lower since integration infrastructure is pre-built and managed.	As integrations mature, your maintenance burden increases (usually in a linear fashion).
Usage and metrics	Provides visibility into usage, logs, and performance, enabling better data-driven decisions.	Usually lack accessible metrics for usage, customers, and issues.
Risk exposure	The platform is outsourced, so you have less control of details, but substantially less risk overall. Compliance with standard frameworks like HIPAA, GDPR, and CJIS are baked in.	You own everything and have complete control, but all the risk is also yours.

Prismatic vs In-House: Build Product, Not Plumbing

Overview

Proven impact at scale

Common questions

Ready to make your product extensible?