Skip to main content

Customer experience

The customer sets up the appliance in their own cloud by running a setup script (provided by the vendor) in the cloud provider's cloud shell (e.g. Google Cloud Shell). The setup script downloads the tensor9 CLI, and then uses Terraform to provision the appliance inside their cloud. The setup process takes under an hour. A more detailed guide is coming soon.

Once the customer’s appliance is set up, their experience has high fidelity to the SaaS experience they are used to. The key difference being that the customer accesses the vendor’s software through their own appliance's private endpoint. For example: PlayHT which uses Tensor9 to offer text-to-speech software on-prem. Their SaaS customers convert text to speech by sending REST requests against the PlayHT's public REST API at https://api.play.ht. But when an on-prem customer, say, One Medical, uses PlayHT through their own appliance, they send REST requests to their appliance's private endpoint at https://playht.onemedical.com.