> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bondata.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Deployment scenarios

> How BonData's components are arranged for each supported deployment model.

BonData runs the same software in every deployment, but the way the components are arranged, what's multi-tenant versus dedicated, whose AWS account they live in, how the public surface is exposed, depends on the operational context the customer needs.

The following scenarios are supported.

### [Cloud SaaS](/platform/deployment-scenarios/cloud-saas)

Multi-tenant deployment operated entirely by BonData. **Intended for proofs of concept and customers on lower-tier packages** - tenants are isolated logically and share the same infrastructure in BonData's AWS account in the United States. Public surface: `app.bondata.ai`.

### [Dedicated Cloud](/platform/deployment-scenarios/dedicated-cloud)

**Single-tenant, fully managed, for enterprise customers.** A dedicated environment with no other tenants and no shared services, hosted in a separate AWS account that BonData owns and operates. The customer chooses the region but does not provision or operate AWS. Public surface: `{customer}.app.bondata.ai`, fronted by BonData's Cloudflare.

### [Cloud-Prem on AWS](/platform/deployment-scenarios/cloud-prem-aws)

**Single-tenant, inside the customer's own AWS account.** BonData provisions and operates the stack via an IAM role the customer creates and can revoke at any time. The customer's data never leaves their account, except for HTTPS calls to AI model providers. Supports customer-managed encryption keys (BYOK) and customer-owned CloudTrail. Public surface: `{customer}.app.bondata.ai`, fronted by BonData's Cloudflare.

## At a glance

|                     | Cloud SaaS                    | Dedicated Cloud                            | Cloud-Prem on AWS                           |
| ------------------- | ----------------------------- | ------------------------------------------ | ------------------------------------------- |
| Tenancy             | Multi-tenant                  | Single-tenant, dedicated                   | Single-tenant, dedicated                    |
| AWS account         | BonData (shared)              | BonData (dedicated per customer)           | Customer's own                              |
| Region              | US default, EU on request     | Customer's choice                          | Customer's choice                           |
| Operated by         | BonData                       | BonData                                    | BonData (via customer IAM role)             |
| AWS bill            | Included in subscription      | Included in subscription                   | Direct to customer                          |
| BYOK (customer KMS) | No                            | No                                         | Yes                                         |
| Operator audit      | Internal; extracts on request | Dedicated CloudTrail; extracts to customer | Customer-owned CloudTrail, real time        |
| Best for            | POCs, lower-tier packages     | Enterprise needing isolation + residency   | Customer-owned cloud, strictest sovereignty |

***

The component-level description that both scenarios share lives on the [Application architecture](/platform/application-architecture) page. The EKS cluster, networking, storage, and IAM that BonData provisions inside a customer's AWS account for Cloud-Prem is documented in the [Amazon EKS reference architecture](/platform/deployment-scenarios/amazon-eks).

<Card title="Not sure which deployment fits?" icon="comments" href="mailto:support@bondata.ai">
  Contact us to scope the right deployment for your enterprise. We'll recommend the path that fits your security, residency, and compliance requirements, and walk through the engagement together.
</Card>