To ensure that our high trust, ultra-secure cybersecurity software is only available to trusted organizations, it is only offered through trusted marketplaces. Below is a brief review of the process once you purchase through a marketplace.
Your journey to strong security, confidentiality and integrity of data in transit begins with a purchase of our Free Forever plan. Order 1 unit of XTRA (for your internal workloads) and 1 Unit of K4C (for your public-facing workloads).
After the marketplace purchase occurs, a registration page will appear to register your purchase through our marketplace partner, Tackle.io. This step collects a little more information, but the important information is letting Hopr know who the technical point of contact is so we know with whom we will share deployment details.
While we're working with the technical point of contact, you will receive an email from Hopr.co inviting you to complete your sign up. This allows us to verify the purchaser email address with the least amount of friction. Clicking on the button in the invitation email verifies your email address.
You will receive a second Hopr.co email with a link to your account signup page. Create a strong passphrase (8-characters minimum) for your Hopr.co account. Save it and then sign in. If you are not the Technical Point of Contact, the following steps are not relevant to you.
On sign-in you will be automatically redirected to your account page. Follow the instructions in the guide boxes to complete account information. The guide boxes will bring you to the Onboarding pages where you will find a series of articles and videos that explain how to use Hopr Sidecars. We'll make sure your technical point of contact (if not you) has the same information.
While you are completing the onboarding 'course', our support team will be preparing the documents and credentials needed to obtain, configure, and deploy your Hopr Sidecars. We will provide this information to the Technical Point of Contact.
The Technical Point of Contact configures YAML files and deploys the sidecars into pods with a host workload at runtime.