3 ms·
Most of the companies I work with are actively putting in place policies to prevent employees from using OpenAI's service because nobody wants to send their pro
by bane 3y ago
Most of the companies I work with are actively putting in place policies to prevent employees from using OpenAI's service because nobody wants to send their proprietary IP to them.
Almost all of these companies have the technical ability, desire, and means to self-host for their employee community. Imagine the internal coup for CTO/CIOs everywhere to buy whatever is the latest Nvidia GPU cluster box, stick it in the on-prem datacenter, load a licensed GPT model and provide "AI as a service to our employees".
Except what's happening is everybody is looking at buying the box from Nvidia, and sticking a large actually open model on it and simply ignoring OpenAI.
- f6v 3y ago> Almost all of these companies have the technical ability, desire, and means to self-host for their employee community. Well, one of companies I worked for could have hosted a canary service for cron jobs. But we bought it instead of building because we were focused on building features. And here you’re talking about hosting an entire LLM.
- tirpen 3y agoThe cron job canary was probably not a service that employees were uploading tonnes of company confidential material into, was it? So I fail to see how the comparison makes sense. The reason companies shun OpenAI and want a self hosted alternative isn't related to costs, it's becasue they don't want their code, internal emails, documentation etc to be uploaded to Microsoft and thus also directly to the NSA.
- f6v 3y ago> The cron job canary was probably not a service that employees were uploading tonnes of company confidential material into, was it? But they do to Slack and MS Teams. Also go mail services and other places.