683 karma · joined July 15, 2011
Credal is a security first data platform for enterprises building AI Apps. We have point & click connectors to your data sources (like GDrive, Slack, Confluence, O365 etc), but unlike other offerings we automatically enforce the permissions you setup in the source systems, mask any sensitive data like people's SSNs, audit log every interaction, and automatically enforce company acceptable use policies for AI tools like ChatGPT/Claude/LLama etc.
We serve enterprises from 100 person startups to Fortune 20 behemoths, and our team is comprised entirely of people who do truly exceptional things. You'll get to work at the cutting edge of making AI actually work in the real, messy but extremely impactful world of our customers: healthcare, sustainability, industrial robotics, finance and more.
Ruby ended up 'specializing' in web dev, because of Rails. But when Node and React came out, Ruby on Rails had to compete with Nodejs + React / MERN as a way of building a web app. Since people first learning programming to build a web app would usually start with javascript anyway (since a lot of very first projects might not even need a backend), it was a lot easier for the Nodejs/React route to become the default path. Whereas if you were a data scientist, you started on python, and as you got better, you basically just kept using python.
Potential for Data Breaches: - The idea that third parties have inherently higher breach risk is pure FUD.
Data Sovereignty and Compliance Risks/Limited Overside: - Having every single company solve all of these problems for every single part of their software stack is obviously very inefficient. That's why we have SOC II, Pen Testing, etc, as other commenters point out. The process of reviewing vendor SOC II reports is way, way easier than having to manage the cost of managing compliance for the hundreds of little productivity apps your team want to use!
Shared Responsibility Model: I think its pretty typical at this point for companies to take ownership over the behaviour of their sub-processors from a risk perspective.
Its not bribery, by any means, but I think its definitely noteworthy that these pressures / considerations may be involved
1. We support using Credal with your own, open source LLM, which can of course be fully on prem in every sense
2. We also support using Credal with your own Azure OpenAI instance. As you say, OpenAI aren't giving us the weights, but many of our customers have procured Azure OpenAI from Microsoft and then we point GPT 4 usage at their Azure instance, meaning that the data never goes to Open AI at all.
One of the things that's going to be really interesting to see moving forward is whether the open source models are going to be able to compete with the blistering pace and funding that the closed source ones - Bard, Claude, and GPT-X are going to be able to attract (and maybe Mistral?). For the sake of the industry, I really hope that the OS models catch up but given the amount of funding (and now in OpenAI's case, revenue) the closed source models are generating, its hard to see how that happens
1. Manage the permissions of making sure the self hosted LLM is only reading from the documents, slack channels, e.t.c. that the end user should actually have access to
2. Generate an audit log of exactly who did what when
So we actually see self hosted LLMs being a big part of how Credal is used! In the long term, we think Credal will actually become a tool for AI app developers to safely request access to data & embeddings from the enterprise on the fly, and make sure the data they get is appropriately controlled and the audit logs exist in a single place for the enterprise to see what data went to whom/when/why etc
Yup so a few thoughts here - we're exploring using embeddings to allow a description of what you want to hide, that will actually immediately show you what of the data you have synced already would be caught by that (or which previous requests).
On the API side: yes ABSOLUTELY! the API is already live and used intensely by some of our startup customers like Sourceful. The API docs for using the OpenAI models here: https://credalai.notion.site/OpenAI-Drop-in-API-0ef7cfd18a7c...
and the Anthropic models here: https://credalai.notion.site/Anthropic-Drop-In-API-ad298f6f7...
On SOC 2, we used Drata, and spoke to Vanta, Laika and a few others. The price Vanta initially quoted us was waaaay higher than the other two, and between Laika and Drata we went with Drata mostly because there seemed to be more automation in Drata. In the end, the Drata live support was incredible and hard to imagine how we would have gotten the certification so fast without. We started our infra on DO, and so the most painful part of SOC 2 for us was the migration we did to AWS to take advantage of AWS' many security features. My main advice would be take full use of the Drata live support (I'd guess Vanta have something similar), but maybe on a deeper level - when you're doing SOC 2, don't focus on the certification: focus on the policies and technology that actually makes your company secure. In the end, that's what enterprises really care about, especially for the ones that have given us 300 question long questionnaires!
One thing I'm curious about is what you think of the recent OpenAI announcement about not training models on data submitted via OpenAI?