Abstract: Methods and apparatuses are described for generating and deploying customized application software containers. Software containers on a first server comprise an application software module and an end-user-specific data set. A second server receives input data from remote computing devices and stores the input data in a master data set. The second server determines end-user-specific data sets from the master data set. The second server encrypts each of the end-user-specific data sets with an encryption key. The second server generates the software containers by executing the application software module in separate processes and storing each of the encrypted data sets in a separate container. Client computing devices authenticate to the second server to access a software container. The client devices decrypt the end-user-specific data set stored in the software container using the encryption key, and use the application software module to interact with the end-user-specific data set.

Abstract: The Peer-to-Peer Decentralized Distributed Datastructure and Token Exchange Apparatuses, Methods and Systems (“P2P3D”) transforms consensus incentives inputs via P2P3D components into distributed datastructure commit outputs. The P2P3D includes a distributed datastructure token exchange apparatus, comprising: a memory, a component collection in the memory, and a processor disposed in communication with the memory, and configured to issue a plurality of processing instructions from the component collection stored in the memory. The P2P3D includes instructions to identify mutualized trading nodes within a peer-to-peer network topology, wherein the trading nodes include order management systems, and obtain a protocol message, wherein the protocol message includes a custom tag and a first hash of: symbol, side, size and price orders.

Abstract: Methods and apparatuses are described for generating and deploying customized application software containers. Software containers on a first server comprise an application software module and an end-user-specific data set. A second server receives input data from remote computing devices and stores the input data in a master data set. The second server determines end-user-specific data sets from the master data set. The second server encrypts each of the end-user-specific data sets with an encryption key. The second server generates the software containers by executing the application software module in separate processes and storing each of the encrypted data sets in a separate container. Client computing devices authenticate to the second server to access a software container. The client devices decrypt the end-user-specific data set stored in the software container using the encryption key, and use the application software module to interact with the end-user-specific data set.