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

# Deployment

Teleskope can be hosted by Teleskope or deployed in infrastructure you control. Choose a deployment based on your data residency requirements and who will operate the environment.

## Choosing a deployment model

| Model                          | Where it runs                               | Who manages it                    |
| ------------------------------ | ------------------------------------------- | --------------------------------- |
| Single-Tenant SaaS             | A dedicated AWS account hosted by Teleskope | Teleskope                         |
| Self-Hosted, Teleskope-Managed | Your AWS, Azure, or GCP environment         | Teleskope, using access you grant |
| Self-Hosted, Self-Managed      | Your infrastructure                         | Your team                         |

### Single-Tenant SaaS

Teleskope hosts and operates your environment in a dedicated AWS account, including upgrades, monitoring, and scaling. This option suits teams that want a managed service without maintaining deployment infrastructure.

### Self-Hosted

Teleskope runs in infrastructure you control. Choose the management model that fits your operational requirements:

* **Teleskope-Managed:** Your organization owns the cloud environment, and Teleskope manages deployment, upgrades, monitoring, and scaling using access you grant.
* **Self-Managed:** Your team deploys and maintains the environment using deployment artifacts and guidance provided by Teleskope. Your team controls infrastructure operations and upgrade timing.

Work with Teleskope to confirm the supported configuration for your cloud or on-premises environment.

## On-premises and private data sources

On-premises describes where Teleskope runs, rather than a separate management model. A self-hosted deployment can run in your datacenter.

You can also connect a cloud-hosted Teleskope environment to private databases and file shares through an Outpost inside your network. An Outpost connects outbound to your Teleskope environment; it does not require inbound access from Teleskope.

Local classification is available. Classification location and the information returned to your Teleskope environment depend on your configuration, so review data handling requirements with Teleskope when planning your deployment.

## Air-gapped environments

Air-gapped deployments are intended for environments that prohibit outbound connectivity. They require a complete self-managed deployment within your infrastructure. An Outpost connected to a cloud-hosted Teleskope environment is not an air-gapped deployment.

Work with Teleskope to confirm installation, updates, data source access, and feature availability for your connectivity requirements.

## Getting started

Contact your Teleskope representative or <contact@teleskope.ai> to choose a deployment model and obtain the appropriate setup guide. Provide the email address of your first administrator to begin workspace onboarding.