3 ms·
exactly as any existing API, it's just that you would encrypt the prompt with the API public key before querying the API; since it's running in a secure enclave
by tony_codes 4y ago
exactly as any existing API, it's just that you would encrypt the prompt with the API public key before querying the API; since it's running in a secure enclave environment, it is highly secure. My idea is that this could be interesting for applications that are sensitive but would benefit from AI features. For example, providing sentiment analysis for a journaling application (private journal entries)
- qualudeheart 4y agoYes that’s hot stuff.
- toss1 4y agoWould this work in a way that could keep data on the customers' premises? I often use CUI (Confidential/Controlled Unclassified Information) or classified information, and I'm thinking this would be really big for such applications, but you'd need to be seriously secure to meet MIL standards. Then there is obviously a lot of corporate info or banking info with different but similarly high standards... This is certainly a great start securing the comms - good fortune putting it all together!
- tony_codes 4y agoI did not have in mind a way to keep data on the customer premise, it's more about a verifiable zero-knowledge architecture so the data never leaves unencrypted, and the decryption keys never leave the secure enclave which decrypts the data and runs the model on the data. This kind of secure enclave is exactly what AWS Nitro is designed to do, but it runs in the cloud, so the data is off premise.