alliewithane

Sounds like it's exactly what I need. Thank you!

They are not comfortable with the fact that I can look at their code base whenever I want.

It's the latter. It's pretty much an agent for their GitHub repo. The agent needs access to their code and keeps some kind of knowledge that it generated in a tree database. Wouldn't it be considered a red flag that I can access their data whenever I want? If I used at-work encryption that just means that I have the ability to access to data whenever I want. However if they did some sort of self-hosting then I can only access it temporarily via APIs and thus I can only access the data temporarily when &they want.

How is that possible?

That is very valid. My problem is that a large portion of my possible clients seemed to be happy with the idea of the solution I provided. I was looking in it tech wise because I somewhat validated it for my current client-space.

Self-hosting seems like the most reliable option for the time being (or executing functions on the encrypted data without decrypting it) however, is it standard practice that I use Kubernetes to give them a preconfigured database that they can deploy on my own cloud? I wouldn't access the code except temporarily through a little script that talks to my cloud that comes along the database in the pod that they "self host." Would that be considered standard practice?

This is an option but it's too much of a hassle. You can't store the company data all on one single computer. An alternative would be to create some sort of intranet inside the company only for this data. This would also mean that we can only process the data if the computer was open.

The main problem is that I need to process their private data frequently. This means end-to-end encryption is not really an option.

Thank you!

That makes sense, I could add some code in the container that can communicate with private APIs in my servers. Is this standard practice or just an adhoc solution?

The problem is that I cannot do that. I need to run code on the data which means I can access the data theoretically any time and thus my client is super uncomfortable with that considering I need to access their code base.

My main problem is that I need to do operations on the data while it's in the DB. This means that I cannot leave it encrypted end-to-end there.

I see, I heard about "fully homomorphic encryption" which is faster to implement and allows you to run code on encrypted data but the time complexity is O((10^6) * n) which is insane.