Skip to main content
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, 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.
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.

​
What Cymph operates

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 — 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:
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.

​
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.

​
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 — password resets and notifications depend on it.
  3. Configure single sign-on if your users authenticate through an identity provider.
  4. Create your first organisation — see Organisation management.
  5. Allowlist the egress addresses on any endpoint you plan to integrate with.
  6. Configure an AI provider if you want the AI features.
To discuss a managed tenant, contact support@cymph.io.