Buyer

Overview

In Tensor9's model, a Buyer represents an end customer who purchases and runs a vendor’s App in their own infrastructure. Buyers are organizations such as enterprises, financial institutions, healthcare providers, and other regulated industries that require applications to run securely within their own controlled environments.

Each buyer is associated with metadata that defines their organization, preferences, and any custom configurations related to their appliances.

Motivation

1. Customer Identity: Buyers are identified by their organization’s name and domain.
2. App Deployment: When a buyer purchases an app, Tensor9 provisions an appliance in the buyer’s infrastructure where the app runs.
3. Configuration and Control: Buyers have the ability to customize their appliances to fit their organizational requirements. This includes defining security policies, allow-listing logs, and enabling or disabling specific features.

Key Concepts

• Buyer Info: Represents the buyer’s organization name, domain, and configuration details.
• App: The software product provided by the vendor that the buyer runs in their environment.
• Appliance: The secure, self-contained environment deployed within the buyer’s infrastructure where the vendor’s app runs.
• Vendor: The software provider that creates and delivers the app to the buyer.

Buyer Lifecycle

1. Onboarding: The vendor creates a buyer profile within Tensor9 and associates it with their app. Then the vendor generates an appliance setup script for the buyer’s infrastructure.
2. Appliance Creation: The buyer runs the setup script to deploy the appliance and launch the app in their environment.
3. App Usage: The buyer uses the vendor's app running in their private appliance.