Show HN: Setup your Company Brain in minutes(connai.dev)
connai.dev
Show HN: Setup your Company Brain in minutes
https://connai.dev
2 comments
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.
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.
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.
I've been working on a company brain project for fun so engineers like myself can stop rebuilding the same context retrieval, memory management, and app integrations for each job or project they start on. I started by building a context retrieval system like prism-coder and GBrain for my local agents. When I connected 10+ apps, the dedicated MCP servers at each project would work fine, but the agent itself would struggle to find and understand cross-application context when trying to take a meeting transcript of the product + engineering decisions -> jira ticket -> PR and using that to help it debug or enhance it through an end to end epic. Then I started toying with the idea of ingesting individual app data into a centralized DB but I was still having to create a custom ingestion solution for each app I integrated with which sucks up so much time getting an OAuth client + secret set up for each app so that all of my teammates and I could use the same DB for their agents.
It's been a fun project to try and figure out these memory management and context retrieval problems like ensuring that query responses are grounded in some truth and citations, but you also don't just get every piece of data you have returned on every query.
I figured developers could save some time and effort in building this stuff themselves (or with their Software Factories) and should just be able to pull it off the shelf and reduce the idea -> building time frame so they can focus on making their agents actually do things to help them at work. Since then, I've been able to expand on it and connect mine and my friends' Paperclip agent teams to it via an MCP server to really test out the shared intelligence aspect of a swarm of agents.
Thinking about open sourcing it or making it self hostable since companies probably don't want their entire company data synthesized and stored into one third-party SaaS offering, but it's still the easiest way to make it something you can play around with. Would love feedback on it for why it's dumb.