Skip to content

Why Blueprints?

Securely deploying Kubernetes application networks can be a complex and error-prone process that frustrates many DevOps and Developers. It requires implementing code for Public Key Infrastructure (PKI) certificates, managing keys, setting up Transport Layer Security (TLS). Then there is weeks of troubleshooting to get the networking and communications between apps worked out. And if the apps are in different clusters, it is even more difficult and complex.

Hopr's Korvette-S WoSP removes the complexity and friction while improving overal application and data security. Blueprint taken 'security by design' to a new level of simplicity for DevOps and Platform Engineers. Blueprins pre-configuring apps with WoSP sidecars to create "ready to deploy" kubernetes manifests bundled with apps and documentation so that a multi-pod app network can be implemented in <30 minutes. Blueprints simplify WoSP deployments and ensure the application layer (Layer 7 of the OSI stack) benefits from:

  • Restricted access to every app (workload) to allow only other trusted workload to connection
  • Secured data in transit between workloads using Synchronous Ephemeral Encryption (SEE™) a protocol that creates a continuous secure lane between communicating workloads
  • Rejecting all access attempts by untrusted workloads
  • "Hopping" (rotating) access credentials at a high frequency, preventing crdential theft and Man-in-the-Middle attacks
  • Meeting Zero Trust principles of frequent identity trust verification of workloads
  • Eliminating the "secret zero" problem
  • Eliminating the architectural ovehead and cost of managing and storing keys by central cloud services
  • Eliminating the risk of post-quantum encryption failure or AI-driven cyber attacks

Available Blueprints

US Export Controls Limit Availability Blueprints utilize patented security technologies built in the USA and controlled by US Export Administration Regulations (EAR), which governs and limits their availability in other countries. Hopr must comply with these regulations.

Free Trial Blueprints

Two blueprints are offered on a free trial basis. They represent the basic messaging patterns of relay, fan-out, and fan-in that form the building blocks of larger app networks. Only one free trial blueprint is permitted per user.

Bi-pod Blueprint

Two (2) HTTP Apps (Python) with Korvette-S WoSPs in separate pods in a single cluster 

graph LR
    A["Pod-1"] --> B["Pod-2"]
    B --> A

    style A fill:#428cf6,stroke:#fff,stroke-width:2px,color:#fff
    style B fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000

Tri-pod Fan-out Blueprint

Three (3) HTTP Apps (Python) with Korvette-S WoSPs in separate pods in a single cluster The message pattern 'fans-out" from Pod-1 to Pods-2 and -3

graph LR
    A["Pod-1"] --> B["Pod-2"]
    A --> C["Pod-3"]

    style A fill:#428cf6,stroke:#fff,stroke-width:2px,color:#fff
    style B fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000
    style C fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000

Tri-pod Fan-in Blueprint

Three (3) HTTP Apps (Python) with Korvette-S WoSPs in separate pods in a single cluster The message pattern 'fans-in" from Pod-1 and Pod-2 to Pod-3

graph LR
    A["Pod-1"] --> C["Pod-3"]
    B["Pod-2"] --> C

    style A fill:#428cf6,stroke:#fff,stroke-width:2px,color:#fff
    style B fill:#428cf6,stroke:#0000b4,stroke-width:2px,color:#000
    style C fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000

Quad-pod Fan-out-in Blueprint

Four (4) HTTP Apps (Python) with Korvette-S WoSPs in separate pods in a single cluster The message pattern 'fans-out" from Pod-1 to Pods -2 and -3, and then 'fans-in from Pods -2 and -3 to Pod-4

graph LR
    A["Pod-1"] --> B["Pod-2"]
    A --> C["Pod-3"]
    C --> D["Pod-4"]
    B --> D

    style A fill:#428cf6,stroke:#fff,stroke-width:2px,color:#fff
    style B fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000
    style C fill:#f5b63e,stroke:#0000b4,stroke-width:2px,color:#000
    style D fill:#428cf6,stroke:#fff,stroke-width:2px,color:#fff