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

# Managed cloud tenant

> A dedicated Cymph instance hosted and operated by Cymph, configured by you.

A managed cloud tenant is your own Cymph instance — reachable at a hostname of its own, such as `client1.cymph.io` — hosted on AWS and operated by Cymph.

It is the same product as a [self-hosted](/deployment/self-hosted/architecture) deployment, built the same way and behaving the same way. The difference is who runs the infrastructure underneath it: Cymph performs the installation, operates the database and filesystem as managed services, handles DNS and certificates, and takes the backups. Everything inside the application stays yours to configure.

<Note>
  This is not a shared multi-tenant service. Your tenant is a separate instance with its own hostname and its own data store — no other customer's data lives alongside yours.
</Note>

## What Cymph operates

|                                              | Handled by |
| -------------------------------------------- | ---------- |
| Installation and initial provisioning        | Cymph      |
| Hostname and DNS                             | Cymph      |
| TLS certificates and renewal                 | Cymph      |
| Database (managed PostgreSQL) and filesystem | Cymph      |
| Backups and restore                          | Cymph      |
| Version upgrades                             | Cymph      |
| Infrastructure monitoring and availability   | Cymph      |

You do not need to install anything, hold TLS certificates, run a backup routine, or plan an upgrade window. The operational pages under [Self-hosted](/deployment/self-hosted/architecture) — installation, TLS, backup and restore, upgrades — do not apply to you.

## What you configure

Your tenant comes with an **on-prem administrator** account, and you hold it. Despite the name, it is the deployment administrator account in both models, and it gives you full control over everything inside the application:

| Area                                      | Where                                                              |
| ----------------------------------------- | ------------------------------------------------------------------ |
| Outbound e-mail                           | [SMTP](/deployment/settings/smtp)                                  |
| AI provider                               | [AI configuration](/deployment/settings/ai)                        |
| Single sign-on (Google, GitHub, Entra ID) | [Single sign-on](/deployment/settings/sso)                         |
| Playbook Hub and Explore                  | [Playbook Hub & Explore](/deployment/settings/hub-explore)         |
| Organisations                             | [Organisation management](/administration/organisation_management) |
| Members, roles and teams                  | [Administration](/administration/user_management)                  |
| Audit logs                                | [Audit & logging](/security/audit-logging)                         |

<Info>
  The AI provider and the SMTP server are **yours to supply**, exactly as in a self-hosted deployment. Cymph does not provide a model or a mail server on your behalf — you enter your own provider's settings, and the credentials are encrypted with your tenant's own key material. See [AI & data usage](/security/ai-data-usage).
</Info>

## Networking

Your tenant runs in AWS `eu-west-1` (Europe / Ireland). Because integrations connect outbound from AWS rather than from your own network, endpoints behind a source-IP allowlist need Cymph's egress addresses permitted. The addresses, and the notice policy for changing them, are in [Networking](/deployment/networking#managed-cloud-tenant).

## Getting started

Onboarding is arranged with the Cymph team, who provision the tenant and hand over the administrator credentials. From there:

1. Change the administrator password at first login.
2. Configure [SMTP](/deployment/settings/smtp) — password resets and notifications depend on it.
3. Configure [single sign-on](/deployment/settings/sso) if your users authenticate through an identity provider.
4. Create your first organisation — see [Organisation management](/administration/organisation_management).
5. Allowlist the [egress addresses](/deployment/networking#managed-cloud-tenant) on any endpoint you plan to integrate with.
6. Configure an [AI provider](/deployment/settings/ai) if you want the AI features.

To discuss a managed tenant, contact [support@cymph.io](mailto:support@cymph.io).