> For the complete documentation index, see [llms.txt](https://docs.trustlogix.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trustlogix.io/cloud-deployment-options.md).

# Cloud Deployment Options

TrustLogix offers two deployment models: SaaS and TrustLet. Each model balances security, operational effort, and customer control differently, so you can choose the option that best fits your organization's security and compliance requirements.

This document explains the TrustLogix architecture, describes each deployment model, and outlines the responsibilities shared between TrustLogix and your team.

### TrustLogix Architecture

The TrustLogix platform is made up of two planes:

* Control Plane (CP): Hosts the TrustLogix console, APIs, and the policy store where access policy definitions are maintained. The Control Plane always runs in the TrustLogix AWS account, regardless of the deployment model.
* Data Plane (DP): Hosts the services that connect to your data sources and AI agents. The Data Plane can run in the TrustLogix cloud or in your own cloud account, depending on the deployment model.

The Data Plane is made up of two groups of services:

* Data and Agent Access Governance (DAG): Deploys and synchronizes access policies, user attributes, and metadata with your data sources, and enforces governance for AI agents.
* Data and Agent Activity Monitoring (DAM): Collects and analyzes activity and metadata to power monitoring policies, risk detection, Access Analyzer, reports, and AI-assisted security insights.

### SaaS Deployment

In the SaaS model, both the Control Plane and the Data Plane are deployed and fully managed by TrustLogix in the TrustLogix AWS account.

* Deployment: TrustLogix manages all deployments and product upgrades.
* Encryption: Data Plane storage and the Control Plane database are encrypted using AWS KMS keys.
* Feature Management: DAG and DAM features are enabled from the TrustLogix console, and the required cloud resources are provisioned automatically. Refer to [Tenant Settings](https://docs.trustlogix.io/configurations/tenant-settings).
* Monitoring: TrustLogix proactively monitors the health of all Control Plane and Data Plane services.
* Network Security: Snowflake accounts hosted on AWS can connect securely to the TrustLogix Control Plane using AWS Private Link.

Best suited for: Organizations that want a fully managed service with minimal operational overhead.

### TrustLet Deployment

In the TrustLet model, the entire Data Plane is deployed in your AWS account. Only the Control Plane runs in the TrustLogix AWS account.

* Deployment: Your team deploys and upgrades the Data Plane services in your AWS account. TrustLogix manages the Control Plane.
* Encryption: Data Plane storage is created in your AWS account and encrypted using AWS KMS keys. The Control Plane database is encrypted using AWS KMS keys.
* Feature Management: Your team enables DAG and DAM features and deploys the required AWS resources.
* Monitoring: Your team monitors the Data Plane services. TrustLogix monitors the Control Plane.
* Network Security: Your team manages networking for the Data Plane in AWS. AWS Private Link remains available for Snowflake connectivity to the Control Plane.

Best suited for: Organizations that require maximum control over their environment, with data source activity and audit data remaining in their own cloud account.

Note: In the TrustLet model, the Data Plane uses separate data source users or service principals for policy creation (control plane) and policy deployment (data plane). Refer to [Key Pair Authentication Setup](https://docs.trustlogix.io/data-sources/snowflake/key-pair-authentication-setup) for configuration details.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.trustlogix.io/cloud-deployment-options.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
