jsethi512

I apologize for not being clear. we have developed crypto using well-vetted and best practice crypto apis from android, iOS and web crypto apis available in the browser. some of the algos used for crypto operations involve ECC_NIST_P256, AES-GCM with HMAC-based KDF, RSA-OAEP, Shamir's secret sharing...

the plan is to support remote access (eliminating VPN) to cloud-hosted database (in AWS, GCP) and also self-hosted database in the on-premise infrastructure. we be be leveraging access management service (eg AWS IAM) for passwordless access to cloud-hosted and will be leveraging cert-based authentication for self-hosted database.

For kubernetes cluster, we will be delivering a kubernetes service that will facilitate to access the cluster remotely from the kubectl.

idemeum has been built from ground up with cloud-first principles of high availability, scalability, resiliency and observability. Currently we support multi-tenant and dedicated-tenant SAAS maturity models depending on the customer need for isolation.

we built on the principles of zero-knowledge cloud which means decentralizing identity + crypto on the client side. Keeping passwordless in context, we wanted to eliminate passwords completely which means not even a master password. we rolled out our own crypto for mobile, browser and desktop app.