A model you might look at if you are a majority or 100% shareholder is to have a separate AWS account that you control 100%. You can have write-only S3 buckets

A model you might look at if you are a majority or 100% shareholder is to have a separate AWS account that you control 100%. You can have write-only S3 buckets that another AWS account can post to. You should be able to do this with other cloud systems as well. You can then use replication rules to copy data from your production AWS account to this backup one. Although I am the technical co-founder in this situation, I am protecting myself against mistakes made by senior technical staff. It would also protect to a measure against malicious action. I certainly hope I never have a dispute with my business partner. If I did, I would try to resolve it amicably and if necessary resort to the courts. At no point would I even dream of cutting off my nose to spite my face by damaging production systems for example or deleting code. That just gives the other side ammunition at best and at worst the consequences can be very serious [0] As others have noted, there is little you can do to stop a trusted director-level partner or employee if a switch flips and they suddenly become evil. Setting up a write-only backup system is about the best you can do... but if you're non-technical who are you going to trust to do this? [0] https://www.theregister.co.uk/2008/12/29/terry_childs_trial/ https://www.theregister.co.uk/2008/12/29/terry_childs_trial/