A hosted secrets management transport method for managing secrets at one or more offsite locations, the method comprising: defining boundaries for two or more sovereignties that are larger functional groupings of components, each sovereignty having an independent master record, wherein each sovereignty includes two or more regions; defining a primary region within the two or more regions; accessing, within the primary region, a master record hardware security module that is a primary storage of secrets for that sovereignty, wherein the master record hardware security module is a truth record for all actions on secrets within its corresponding sovereignty, the actions on the secrets including one or more of creation actions, update actions, and deletion actions; defining one or more secondary regions that are not the primary region; accessing, within the one or more secondary regions, a backup record hardware security module that is where data backups of the secrets from the master record hardware security module are created; executing live replication from the master record hardware security module to the backup record hardware security module that supports multi-tenancy secret management of multiple distinct companies at the same time; accessing, in each of the two or more regions, a primary cache hardware security module that receives live replication from the backup record hardware security module; accessing, in each of the two or more regions, a hardware security module cache pool, wherein the hardware security module cache pool is scalable to replicate from the primary cache hardware security module depending on traffic needs within a region; accessing, in each of the two or more regions in a sovereignty, a cluster of software containers and a software container management system that ensures the software containers are available and operating properly; and receiving a request for values at a software container, wherein the request for values from the software containers in a cluster of a region are load balanced amongst the primary cache hardware security module and the hardware security module cache pool for all read actions; wherein, when a value is requested that is not present, the system looks up an originating sovereignty of the value and, if different than the request originating sovereignty and permissible, makes a request to the originating sovereignty for the value, which is then cached in the primary cache hardware security module of the region in which the request originated, wherein the value is then distributed to the hardware security module cache pool via live replication. defining boundaries for two or more sovereignties that are larger functional groupings of components, each sovereignty having an independent master record, wherein each sovereignty includes two or more regions; defining a primary region within the two or more regions; accessing, within the primary region, a master record hardware security module that is a primary storage of secrets for that sovereignty, wherein the master record hardware security module is a truth record for all actions on secrets within its corresponding sovereignty, the actions on the secrets including one or more of creation actions, update actions, and deletion actions; defining one or more secondary regions that are not the primary region; accessing, within the one or more secondary regions, a backup record hardware security module that is where data backups of the secrets from the master record hardware security module are created; executing live replication from the master record hardware security module to the backup record hardware security module that supports multi-tenancy secret management of multiple distinct companies at the same time; accessing, in each of the two or more regions, a primary cache hardware security module that receives live replication from the backup record hardware security module; accessing, in each of the two or more regions, a hardware security module cache pool, wherein the hardware security module cache pool is scalable to replicate from the primary cache hardware security module depending on traffic needs within a region; accessing, in each of the two or more regions in a sovereignty, a cluster of software containers and a software container management system that ensures the software containers are available and operating properly; and receiving a request for values at a software container, wherein the request for values from the software containers in a cluster of a region are load balanced amongst the primary cache hardware security module and the hardware security module cache pool for all read actions; wherein, when a value is requested that is not present, the system looks up an originating sovereignty of the value and, if different than the request originating sovereignty and permissible, makes a request to the originating sovereignty for the value, which is then cached in the primary cache hardware security module of the region in which the request originated, wherein the value is then distributed to the hardware security module cache pool via live replication.