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

# Deployment options

> Run Paradime as fully managed SaaS or deploy the Paradime data plane inside your own AWS, GCP, or Azure account with Bring Your Own Cloud (BYOC).

Paradime offers two deployment options: **Paradime-hosted SaaS**, fully managed in Paradime's cloud accounts, and **Bring Your Own Cloud (BYOC)**, managed by Paradime inside your own cloud account. Both options give you the same product experience. BYOC additionally gives you isolated compute, the ability to route traffic over private networks, and integration with services inside your VPC or VNet.

<Note>
  BYOC is available on the [Enterprise plan](https://www.paradime.io/pricing). Contact the Paradime team at [support@paradime.io](mailto:support@paradime.io) for details.
</Note>

## Paradime-hosted SaaS

By default, Paradime runs as a fully managed SaaS platform. Paradime provisions, operates, secures, and upgrades all infrastructure in Paradime-managed cloud accounts. This is the fastest way to get started and requires no infrastructure work on your side.

## Bring Your Own Cloud (BYOC)

With BYOC, all components that interact with your private data are deployed inside your own AWS, GCP, or Azure account and managed remotely by the Paradime Control Plane via the Paradime Operator. This keeps all data plane resources within your boundary while preserving the managed-service experience.

* The **control plane** runs in Paradime's managed infrastructure. It orchestrates deployments, upgrades, and scaling remotely.
* The **data plane** (the compute, storage, and databases that run your workspaces) lives entirely inside your own cloud account.

## Backend and frontend connectivity

There are two distinct directions in which Paradime exchanges traffic with your network, and each has its own reason for connectivity:

* **Backend connectivity**: traffic that flows **from Paradime into your network**. Paradime uses these connections to reach the things it needs to function: datawarehouses, git providers, auth providers (for example, an internal OIDC issuer), and any other service the Paradime data plane has to reach.
* **Frontend connectivity**: traffic that flows **from your network into Paradime**. Anything that needs to reach Paradime falls in this bucket: the Paradime UI running in employee browsers, API clients, the Paradime CLI, and CI/CD systems triggering Bolt schedules.

Most enterprise deployments end up using both: backend private connectivity (such as [AWS PrivateLink](/integrations/aws-privatelink/index)) into your data network, plus frontend private endpoints so the Paradime UI and your tooling talk to Paradime over the same private fabric.

## Choose a provider

<CardGroup cols={3}>
  <Card title="Amazon Web Services" icon="aws" href="/products/settings/deployment/byoc/aws">
    Deploy the Paradime data plane inside your own AWS account.
  </Card>

  <Card title="Google Cloud Platform" icon="google" href="/products/settings/deployment/byoc/gcp">
    Deploy the Paradime data plane inside a dedicated GCP project.
  </Card>

  <Card title="Microsoft Azure" icon="microsoft" href="/products/settings/deployment/byoc/azure">
    Deploy the Paradime data plane inside your own Azure subscription.
  </Card>
</CardGroup>


## Related topics

- [Continuous Deployment](/products/bolt/ci-cd/continuous-deployment/index.md)
- [Set up continuous deployment](/guides/orchestrate-data-pipelines/set-up-continuous-deployment.md)
- [Migrate dbt™ jobs from GitHub Actions to Paradime Bolt](/guides/migrations/migrating-dbt-tm-jobs-from-github-actions-to-paradime-bolt.md)
- [Gitgraph Diagrams](/integrations/mermaid-js/gitgraph-diagrams.md)
- [Confluence](/integrations/confluence/index.md)