Middleware turns connector maintenance into product
Isaac Nassimi, SVP of Product at Nylas, on the market for developer middleware
This is the core reason universal APIs become real businesses, they turn a messy, never ending maintenance job into a one time integration so product teams can spend their best engineers on the product customers actually buy. In Nylas’s case, connecting to Gmail or Outlook is not just one API call. It means OAuth, webhook endpoints, sync logic, thread handling, token management, and provider specific edge cases that keep changing underneath the app.
-
The hidden work is not the first connector, it is the upkeep. Nylas describes handling authentication, synchronization, data normalization, and webhooks across 250 plus providers, while Microsoft and Google style integrations require public endpoints, subscriptions, and ongoing event handling to stay in sync.
-
This pattern shows up across universal APIs. Finch exists because payroll sellers otherwise build 40 to 50 connectors and still need large ops teams for the rest. Rutter’s customers often start with native integrations, then switch when provider changes and long tail maintenance become more painful than the abstraction cost.
-
The strategic value is that middleware graduates from connector layer to workflow layer. Once the base integration is stable, Nylas can sell higher level features like scheduling UI, email parsing, signature extraction, and cleaned conversation data, which are much harder for a customer to recreate than raw access alone.
The direction of travel is clear. Basic connector work keeps getting cheaper and more expected, while the winning platforms move up the stack into opinionated workflows and intelligence. For Nylas, that means owning more of the communication feature set inside software products, not just the pipe into Gmail and Outlook.