
Hopr offers a suite of cybersecurity products that deliver a Cloud Native AMTD for enterprise architectures.
Click on a card below to learn more about each product.
























































































Yes. Hopr Connect Gateway establishes trust of workloads at your partner organizations with Hopr K4C WoSPs at each endpoint (client and server). Your partner organization's client endpoint is protected by its WoSP.
Yes. The "Kerberos for the cloud" protocol assures that connections to your APIs from outside parties are high trust with Hopr validating that trust before the connection occurs.
Yes. API keys are static, easily stolen, and difficult to replace. Bulk resets on a suspected breach are expensive and penalize users. Hopr ensures that stolen API keys are ineffective and only legitimate trusted workloads can use their API key.
Hopr Connect Gateway can be used with a variety of popular cloud container systems and even virtual machines. Contact us to learn about solutions for specific architectures.
Hopr's security innovations were built in the USA and are subject to export control regulation of the USA. They are intended for responsible commercial use to benefit civil society. The licensing process ensures we comply with these regulations.
A session is a period of time in which two WoSPs are connected and exchange data or messages. Typically, these are time periods of hours or more and allow for many APIÂ calls and responses between two apps. For each WoSP deployed, Hopr counts the number of communication sessions performed. Each communication session has 2 endpoints and, therefore, 2 WoSPs, each of which incur a usage fee.
Blueprints utilize Korvette-S WoSPs and pre-configure them with a basic app. They are pre-configured application networks with customizable business logic. A variety of blueprints with different communication patterns and protocol choices are available in the Lane7 catalog to accelerate and scale the deployment of application networks.
