Service Model

Last Updated November 6, 2025

Due to the flexible nature of the Service and the numerous use cases for which it can be deployed, the Service has a number of role attributes (“Roles”) that can be allocated among Organizations when they work together to use the Service. While in many cases, the same Organization will be the Subscriber, Multipath Gateway Owner, and the Enclave Access Owner (as defined below), these Roles can be and will at times be held by different Organizations due to the specific use case.

The Organization that purchases a Subscription Plan through a signed ordering document or online order (“Order Form”) to access the Service in accordance with such Subscription Plan is the Subscriber. The Service is a cloud-based technology that enables a Subscriber to create an Enclave and to control what services and tools are provisioned in the Enclave. Subscriber may be assigned a Tehama employee (“Concierge”) to assist a Subscriber with all activities relating to its use of the Service, including, but not limited to, setting up its Account, configuring the Subscriber within the Service, providing information on billing and invoicing, and in general serving as the point of contact for anything relating to the Subscriber’s Account.

The Organization that installs the Tehama Multipath Gateway to control the Enclave’s access to the resources and services within that Organization’s internal infrastructure, such as internal network, cloud, etc., (“Assets”) or provides some other secure connection between the Assets and an Enclave directly connected to the Internet (“Internet-Connected Enclave”) is the Multipath Gateway Owner. The Multipath Gateway Owner may, by way of example, use the Enclave as a secure and audited virtual private extension of the Multipath Gateway Owner’s IT network to receive IT services remotely from another Organization or third party.

The Organization who controls access to the Enclave is the Enclave Access Owner. An Enclave Access Owner can invite Users within its own Organization as well as other Organizations and third parties to access the Enclave and use the Service. In cases where the Subscriber is different from the Multipath Gateway Owner, such as where IT services companies are delivering services through Enclaves to end clients, the Multipath Gateway Owner is the Enclave Access Owner. User access to Enclaves in this use case is controlled through a proposal and acceptance workflow whereby a Subscriber proposes an individual and a Multipath Gateway Owner approves of access to the Enclave by that individual.

Copyright 2019-2025 Tehama Technologies Inc. and its affiliates or licensors. All Rights Reserved.

NOTICE: This document contains information and other content that is confidential and proprietary to Tehama Technologies Inc. or its affiliates or licensors and may be protected under the law of copyright, patent, or trade secret in Canada, the United States, and other jurisdictions. This document is provided for internal business use only. No part of this document may be modified, reproduced, distributed or disclosed in any form to any third party without the written permission of Tehama Technologies Inc.

TEHAMA and the Tehama logo are trademarks of Tehama Technologies Inc. or its affiliates. All references herein to the corporate names, trade names, trademarks, and service marks of third parties are intended to accurately identify such parties as the sources of specific products and services. No claim of association or license is intended or should be inferred by such use.