This is an interesting problem to take on. I think basically all teams that are adopting AI heavily right now are trying to solve this problem for themselves. I've been building something to fill this gap for my Technical Operations team. This gives me the advantage of handling sensitive information how I see fit in our documentation and creates a single source of all truth that cascades out to our other documentation.
So my question would be: what's the pitch for teams that have the engineering bandwidth to roll something custom out themselves? I think teams that are early adopters for heavy agentic AI use are also typically pretty security conscious. We do heavy sec reviews before we even consider another vendor in the space. I think, for us, that puts the barrier to adopting this over building and tweaking internally just too high.
And ultimately, the thing that would keep us from reaching for a third-party app for this gap is exactly the concern you flag at the end. I wouldn't want my company's full context (and it would have to be very full for this to be effective) sitting in someone else's single-point data layer. A breach could level our entire business.
Is self-hostable high up on the road map? Personally I think this idea lives and dies by it.
I agree, it's a core piece of infra and has to be self-hostable. I launched this site just to get the idea out there for people to play around with, but can definitely ship self-hosting this weekend.
Self-hostable is actually in development right now, but I'm struggling with deciding the path forward:
1) PKCE for OAuth so connai.dev owns the oauth client setup for each app
2) Another connection mechanism for each of these apps like storing creds
For now I've just moved to having the self hosting user own the OAuth setup too, but that's a terrible setup experience.
This is an interesting problem to take on. I think basically all teams that are adopting AI heavily right now are trying to solve this problem for themselves. I've been building something to fill this gap for my Technical Operations team. This gives me the advantage of handling sensitive information how I see fit in our documentation and creates a single source of all truth that cascades out to our other documentation.
So my question would be: what's the pitch for teams that have the engineering bandwidth to roll something custom out themselves? I think teams that are early adopters for heavy agentic AI use are also typically pretty security conscious. We do heavy sec reviews before we even consider another vendor in the space. I think, for us, that puts the barrier to adopting this over building and tweaking internally just too high.
And ultimately, the thing that would keep us from reaching for a third-party app for this gap is exactly the concern you flag at the end. I wouldn't want my company's full context (and it would have to be very full for this to be effective) sitting in someone else's single-point data layer. A breach could level our entire business.
Is self-hostable high up on the road map? Personally I think this idea lives and dies by it.
I agree, it's a core piece of infra and has to be self-hostable. I launched this site just to get the idea out there for people to play around with, but can definitely ship self-hosting this weekend.
Self-hostable is actually in development right now, but I'm struggling with deciding the path forward:
1) PKCE for OAuth so connai.dev owns the oauth client setup for each app 2) Another connection mechanism for each of these apps like storing creds
For now I've just moved to having the self hosting user own the OAuth setup too, but that's a terrible setup experience.