# Overview

Probo is available as a managed cloud service or as a self-hosted application. Both options provide the same core product experience; the difference is who controls and operates the infrastructure.

## Probo Cloud or self-hosted?

|                              | **Probo Cloud**                                        | **Self-hosted**                                                        |
| ---------------------------- | ------------------------------------------------------ | ---------------------------------------------------------------------- |
| **Infrastructure**           | Hosted and operated by Probo                           | Hosted and operated by your team                                       |
| **Data location**            | EU or US region                                        | Any location supported by your infrastructure                          |
| **Application updates**      | Released and applied by Probo                          | Scheduled, tested, and applied by your team                            |
| **Security patches**         | Monitored and deployed by Probo                        | Monitored and deployed by your team                                    |
| **Backups and recovery**     | Managed by Probo                                       | Designed, monitored, and tested by your team                           |
| **Monitoring and incidents** | Managed by Probo                                       | Managed by your team                                                   |
| **Availability and scaling** | Managed as part of the Cloud service                   | Determined by your architecture and operational practices              |
| **OAuth connectors**         | Provider credentials are managed by Probo              | You configure and maintain each provider's OAuth client and secret     |
| **New OAuth connectors**     | Available without deployment-level OAuth configuration | Require deployment configuration before organizations can connect them |
| **Deployment architecture**  | Managed regional platform                              | Docker Compose or Kubernetes                                           |

Choose **Probo Cloud** when you want Probo to handle platform operations, updates, security patches, and connector infrastructure. Choose **self-hosting** when your organization needs direct control over hosting, data location, network boundaries, or infrastructure services—and has the capacity to operate them.

For a more detailed comparison, see [Choose a deployment](/docs/product/getting-started/choose-deployment).

## Explore deployment options

- [Probo Cloud](/docs/deployment/cloud) — Review regions, managed operations, security, and shared responsibilities
- [Self-hosting](/docs/deployment/self-hosting) — Understand operator responsibilities and supported deployment architectures
- [Configuration](/docs/deployment/configuration/overview) — Configure probod with YAML files and PROBOD_ environment variables
- [Infrastructure security](/docs/deployment/infrastructure-security) — Review encryption, tenant isolation, backups, and security boundaries

## Understand the responsibility boundary

With **Probo Cloud**, Probo operates the application, platform updates, backups, monitoring, and the underlying infrastructure. Your organization manages its users, access settings, integrations, and compliance data.

With a **self-hosted deployment**, your team also owns:

- availability and capacity planning;
- application and infrastructure upgrades;
- PostgreSQL and object-storage backups;
- TLS, secrets, and network access;
- monitoring, logging, and incident response.

Review these responsibilities before exposing a self-hosted deployment to production users.

## Next steps

- For a local evaluation, follow the [self-hosted quickstart](/docs/product/getting-started/quickstart).
- For a single-host installation, use the [Docker Compose guide](/docs/deployment/self-hosting/docker-compose).
- For an orchestrated production environment, use the [Kubernetes guide](/docs/deployment/self-hosting/kubernetes).
- To discuss Probo Cloud onboarding and region selection, [contact Probo](/contact).