Rutter chooses infrastructure over merchant workflows
Peter Zhou, CEO of Rutter, on building the Plaid for ecommerce
This line shows that Rutter is choosing the infrastructure layer, not the merchant workflow layer. Rutter sells to fintechs and commerce software vendors that need one API for orders, customers, payouts, and accounting data across Shopify, Amazon, WooCommerce, NetSuite, and more. Alloy started from merchant automation, where brands build multi step workflows and app to app logic, then added embedded tools for software companies. Same ecosystem, different buyer, product surface, and money flow.
-
Rutter is used when a lender, card issuer, insurer, or commerce app wants a merchant to connect data once, so the software can read clean commerce records or write back into systems. Its core job is standardizing schemas and maintaining connectors, not giving merchants a screen to design automations.
-
Alloy grew up with merchant operators and ecommerce managers building custom flows like routing orders, syncing subscriptions, exporting profitability data, or triggering support and marketing actions across many apps. Forge and embedded iPaaS extend that engine to SaaS companies, but the product DNA is still workflow orchestration and configurability.
-
The practical boundary is where customization lives. Universal APIs are fastest when a software company needs a common read and write schema across many systems. Embedded iPaaS becomes more useful when end users need to map custom fields, set logic, and configure workflows themselves. That makes partnership more natural than direct rivalry.
As commerce stacks keep fragmenting, the market should separate more cleanly into pipes and control panels. Rutter can move upward into more commerce infrastructure for fintech and enablement platforms, while Alloy can deepen the workflow layer for software vendors and complex merchant operations. The more apps merchants use, the more both layers matter, and the more complementary they become.