A system for generating a digital signature comprising: a first backend server; a second backend server; a frontend server configured to: receive a signature request from a remote application server, the signature request including a first total public key with a cryptographically embedded first server identifier and a second total public key with a cryptographically embedded second server identifier; extract the cryptographically embedded first server identifier from the first total public key; forward the signature request to first backend server that corresponds to the first server identifier; in response to determining that the first backend server is unavailable, extract the cryptographically embedded second server identifier from the second total public key, and forward the signature request to the second backend server that corresponds to the second server identifier; forward a second signature to the application server; and wherein the first and second backend servers are each configured to: forward the signature request to a plurality of remote security devices associated with the total public key; receive a first signature from each of the plurality of remote security devices; generate a combined signature based on the first signatures; generate the second signature based on the combined signature and a finalizing key, the finalizing key being cryptographically generated based on the server identifier of the backend server; and forward the second signature to the frontend server. a first backend server; a second backend server; a frontend server configured to: receive a signature request from a remote application server, the signature request including a first total public key with a cryptographically embedded first server identifier and a second total public key with a cryptographically embedded second server identifier; extract the cryptographically embedded first server identifier from the first total public key; forward the signature request to first backend server that corresponds to the first server identifier; in response to determining that the first backend server is unavailable, extract the cryptographically embedded second server identifier from the second total public key, and forward the signature request to the second backend server that corresponds to the second server identifier; forward a second signature to the application server; and receive a signature request from a remote application server, the signature request including a first total public key with a cryptographically embedded first server identifier and a second total public key with a cryptographically embedded second server identifier; extract the cryptographically embedded first server identifier from the first total public key; forward the signature request to first backend server that corresponds to the first server identifier; in response to determining that the first backend server is unavailable, extract the cryptographically embedded second server identifier from the second total public key, and forward the signature request to the second backend server that corresponds to the second server identifier; forward a second signature to the application server; and wherein the first and second backend servers are each configured to: forward the signature request to a plurality of remote security devices associated with the total public key; receive a first signature from each of the plurality of remote security devices; generate a combined signature based on the first signatures; generate the second signature based on the combined signature and a finalizing key, the finalizing key being cryptographically generated based on the server identifier of the backend server; and forward the second signature to the frontend server. forward the signature request to a plurality of remote security devices associated with the total public key; receive a first signature from each of the plurality of remote security devices; generate a combined signature based on the first signatures; generate the second signature based on the combined signature and a finalizing key, the finalizing key being cryptographically generated based on the server identifier of the backend server; and forward the second signature to the frontend server.