Ché Wijesinghe
130 posts

Ché Wijesinghe
@CheWijesinghe
CEO at Cape. Passionate about building great teams with great technology. 🇬🇧🇺🇸







Nobody can compete with OpenAI. If you want to integrate a Large Language Model with your application, OpenAI wins every day. But the problem is that companies can't justify using OpenAI's API with their customer's private information. Here is a solution: The @capeprivacy team shared with me their new API. They redact private information from your content, so you don't have to worry about it. There are two ways you can use the API: First, you can de-identify your content. De-identification removes any Personally Identifiable Information from the input. You can use the redacted content with OpenAI's API or any other model. Second, you can use their Completions API, which handles de-identification and re-identification. It removes sensitive information, sends the redacted query to OpenAI, and re-identifies the content. The attached image shows how simple it is to use the API. If you are working with any sensitive information, this is a must. By the way, @capeprivacy tells me they detect and redact 50 types of sensitive entities, like emails, names, credit cards, and addresses. They use secure enclaves to do this so they can’t see any of the information. Here is a link to their documentation: docs.capeprivacy.com/getting-starte… Thanks to @capeprivacy for sponsoring this post.



Exciting update! 🎉 The Cape API now includes a confidential Llama 2 7B Chat, securely hosted within a dedicated enclave for added privacy. Enclaves preserve the confidentiality of both prompts and model responses during processing, making them invisible to all.







