Middleware as 80% Base Layer
Isaac Nassimi, SVP of Product at Nylas, on the market for developer middleware
The key strategic point is that the best developer middleware stops being a full replacement and becomes a shortcut to 80% of the work. Nylas is describing a product that handles the ugly infrastructure, OAuth, sync, webhooks, thread state, and normalization across Gmail, Microsoft, IMAP, and calendar, while still leaving room for a customer to add custom workflow logic or niche provider features on top. That makes buying feel less like giving up control and more like buying a strong default base layer.
-
This is how universal APIs usually win. Customers rarely start from zero. They often already have one or two native integrations, then use the middleware for the long tail, and later migrate their core integrations too when maintenance gets painful. Rutter describes that path directly, especially when platform APIs keep changing.
-
The product trick is abstraction with escape hatches. Rutter exposes native tokens for edge cases, and Alloy separates a unified API from a more configurable embedded integration layer. Nylas is making the same design choice, one clean interface for common use cases, plus enough access for teams to tweak opinions without rebuilding the whole stack.
-
This matters because pure connector businesses tend to commoditize. In the universal API market, the durable value shifts upward into standardized data models, reliability, permissions, workflows, and higher level features like deductions at Finch or conversation cleanup and data extraction at Nylas. The raw connection is the wedge, not the whole business.
Going forward, developer middleware will keep moving toward opinionated building blocks with selective flexibility, not blank toolkits. The winners will be the companies that let a team launch fast with one integration, then keep enough openness that customers can layer on their own product logic instead of graduating away once they hit edge cases.