> 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

Choose where Teleskope runs and who operates it. An Outpost adds workers inside your network to reach private data sources.

| Model              | Platform location                         | Operated by                                       |
| ------------------ | ----------------------------------------- | ------------------------------------------------- |
| Single-tenant SaaS | Dedicated AWS account hosted by Teleskope | Teleskope                                         |
| Teleskope-managed  | Your AWS, Azure, or GCP environment       | Teleskope, using access you grant                 |
| Self-managed       | Your infrastructure                       | Your team, using Teleskope's deployment artifacts |

{% hint style="info" %}
**First sign-in uses a guided onboarding flow.** However you deploy, your first administrator finishes setup in the browser — naming the workspace, choosing an identity provider (or verifying by email), selecting connectors, and inviting teammates. To start, Teleskope just needs the email address of your first admin (your "onboarding user"); that person receives a one-time setup link to begin.
{% endhint %}

## Architecture and private data sources

The application plane provides the UI, APIs, scheduling, and findings storage. The data plane discovers and reads sources and classifies their content. Their placement depends on your deployment.

An [Outpost](/setup/deployment/outpost.md) runs data-plane workers inside your network and connects outbound to your Teleskope environment. It can be used with SaaS or a customer-hosted environment. Classification can run locally on the Outpost. Remote classification in your Teleskope environment is optional and sends content there for processing.

See [Architecture and Data Flow](/setup/deployment/architecture.md) for cloud, SaaS, and Outpost source paths and the application/data-plane boundary. The [Outpost network requirements](/setup/deployment/outpost.md#network-requirements) list destinations and ports.

For a fully on-premises or air-gapped installation, confirm the architecture, image delivery, and operational requirements with Teleskope. An Outpost requires connectivity to its Teleskope environment.

## Deployment guides

* **AWS:** [Teleskope-managed](/setup/deployment/deployments/aws/teleskope-managed.md) or [self-managed](/setup/deployment/deployments/aws/self-managed.md)
* **Azure:** [Teleskope-managed](/setup/deployment/deployments/azure/teleskope-managed.md) or [self-managed](/setup/deployment/deployments/azure/self-managed.md)
* **GCP:** [Teleskope-managed](/setup/deployment/deployments/gcp/teleskope-managed.md)
* **Source access:** [Least-Privilege Access](/connectors/least-privilege.md)