Reaction: The new partner program looks like vendor lock-in to me

Hey folks, Bob Wilson here! I've been deep in the API automation trenches this week, and I just had to come share some thoughts after digging into Braintrust's newly announced partner program details. On the surface, it promises deeper integration and co-marketing, which is fantastic! But the more I read the technical requirements and the preferred integration pathways, the more a familiar, slightly worrying pattern emerged. It feels architecturally designed for vendor lock-in, which is a real concern for those of us who prize flexibility and event-driven workflows.

Let me break down what I'm seeing, because I think it's crucial for anyone building on this platform:

* **Custom Connector Emphasis:** The program heavily pushes you to build "Braintrust Certified" connectors. The certification checklist, however, mandates using their proprietary webhook format and their specific authentication middleware. If you want to connect to, say, a niche CRM, you're funneled into their framework.
* **Discouraged Standard Protocols:** I looked for clear guidance on using generic webhooks (just a simple POST to an endpoint) or connecting via widely adopted standards like OAuth 2.0 with custom scopes. The documentation buries it, instead highlighting their "Braintrust Connect SDK" as the "recommended and supported" method.
* **Data Portability Hurdles:** The real kicker is in the data schema. Events processed through their certified connectors get stamped with a unique namespace. Extracting that raw data to pipe it into another iPaaS like Zapier, Make, or a custom Node-RED flow later? The docs mention it requires a "translation layer" which, you guessed it, is another service they offer.

Here's a tiny example from their SDK preview docs that illustrates the proprietary bind:

```javascript
// Their 'simplified' SDK approach
const { BraintrustWebhook } = require('@braintrust/connect-sdk');

router.post('/webhook', BraintrustWebhook.verify(), (req, res) => {
// Your logic here, but req.body is now a BraintrustEvent object
// Need the raw payload? It's been parsed and transformed already.
const internalEvent = req.body.toInternalFormat(); // This is now their standard
});
```

This isn't just about convenience—it's about control. By making their SDK and event format the path of least resistance, they're making it progressively more expensive (in time and complexity) to switch or integrate multi-vendor systems. For those of us who love to mix and match the best APIs for the job, this feels like a step back from open, composable architecture.

I'd love to be wrong! Has anyone else pored over the technical annex of the partner agreement? Are there hidden escape hatches or truly open API specs I missed? Maybe there's a way to use their core public API to bypass the "certified" channel entirely? Let's discuss—our integration strategies depend on it.

Happy integrating, Bob