mirror of
https://github.com/andwati/zitadel.git
synced 2026-10-18 05:52:51 +00:00
Florian ForsterandGitHub
2763e93a61
## What
Shorten the `title` frontmatter on 20 docs pages so that the rendered
`<title>` tag stays within the 70-character SEO limit.
The root layout appends ` | ZITADEL Docs` (15 chars) to every page
title, meaning the raw frontmatter `title` must be ≤ 55 characters. A
site scan flagged all 20 pages for the "Title too long" warning (titles
ranged from 71 to 92 characters in the final rendered tag).
## Why
Search engines may truncate or ignore `<title>` tags longer than 70
characters, hurting click-through rates and keyword relevance in search
results.
## How
Each title was rewritten to:
- Fit within 55 characters (leaving room for ` | ZITADEL Docs`)
- Front-load the primary search keyword (product name, protocol, or
feature)
- Include "ZITADEL" where users realistically search for `{feature}
ZITADEL`
- Avoid generic filler words ("Configure", "Set up", "Support for")
All 20 files already have a `sidebar_label` field that preserves the
original descriptive title for sidebar navigation — no navigation
changes result from this PR.
## Pages updated
| Page | Before (chars) | After (chars) |
|---|---|---|
| concepts/features/passkeys | 82 | 64 |
| guides/integrate/identity-providers/openldap | 72 | 58 |
| guides/solution-scenarios/b2b | 78 | 59 |
| guides/integrate/services/cloudflare-oidc | 86 | 54 |
| guides/integrate/login/hosted-login | 71 | 55 |
| guides/integrate/service-accounts/private-key-jwt | 76 | 56 |
| guides/integrate/service-accounts/client-credentials | 78 | 60 |
| guides/integrate/services/google-cloud | 92 | 57 |
| guides/solution-scenarios/saas | 88 | 65 |
| guides/migrate/sources/auth0 | 73 | 65 |
| guides/integrate/login-ui/oidc-standard | 81 | 55 |
| guides/integrate/login-ui/username-password | 73 | 59 |
| guides/integrate/login-ui/device-auth | 78 | 60 |
| guides/integrate/identity-providers/linkedin_oauth | 72 | 58 |
| guides/integrate/identity-providers/pingfederate-saml | 74 | 61 |
| guides/integrate/service-accounts/personal-access-token | 82 | 62 |
| legal/service-description/cloud-service-description | 76 | 61 |
| guides/integrate/login/login-users | 83 | 55 |
| guides/integrate/identity-providers/migrate | 74 | 65 |
| guides/manage/console/projects-overview | 71 | 62 |
All final `<title>` values are between 54 and 66 characters (well under
the 70-char limit).
87 lines
5.4 KiB
Plaintext
87 lines
5.4 KiB
Plaintext
---
|
|
title: ZITADEL Cloud & Enterprise Service Description
|
|
description: "Description of services and service levels for ZITADEL Cloud and Enterprise subscriptions."
|
|
sidebar_label: Service description
|
|
custom_edit_url: null
|
|
---
|
|
|
|
Last updated on April 5, 2024
|
|
|
|
This annex of the [Framework Agreement](../terms-of-service) describes the services offered by us.
|
|
|
|
## Services offered
|
|
|
|
### ZITADEL Cloud
|
|
|
|
[ZITADEL Cloud](https://zitadel.com) is a fully managed cloud service of the [ZITADEL software](https://github.com/zitadel).
|
|
|
|
You will benefit from the same software as the open-source project, but we take care of the hosting, maintenance, backup, scaling, and operational security. The cloud service is managed and maintained by the team that also develops the software.
|
|
|
|
When creating a new instance, you are able to choose a [data location](#data-location).
|
|
We follow a single-provider strategy by minimizing the involved [sub-processors](../subprocessors) to increase security, compliance, and performance of our services. [Billing](https://help.zitadel.com/pricing-and-billing-of-zitadel-services) is based on effective usage of our services.
|
|
|
|
### Enterprise license / self-hosted
|
|
|
|
The ZITADEL Enterprise license allows you to use the [ZITADEL software](https://github.com/zitadel) on your own data center or private cloud.
|
|
|
|
You will benefit from the transparency of the open source and the hyper-scalability of the same software that is being used to operate [ZITADEL Cloud](#zitadel-cloud).
|
|
|
|
#### Benefits over using open source / community license
|
|
|
|
- [Enterprise supported features](https://help.zitadel.com/zitadel-support-states#enterprise) are only supported under an Enterprise license
|
|
- Individual [onboarding support](./support-services#onboarding-support) tailored to your needs and team
|
|
- Get access to our support with a [Service Level Agreement](./support-services#service-level-agreement) that is tailored to your needs
|
|
- Benefit from personal [technical account management](./support-services#technical-account-manager) provided by our engineers to help you with architecture, integration, migration, and operational improvements of your setup
|
|
|
|
#### Benefits over ZITADEL Cloud
|
|
|
|
You can reduce your supply-chain risks by removing us as sub-processor of personal information about your users.
|
|
Support staff will have no access to your infrastructure and will only provide technical support.
|
|
Operation and direct maintenance of ZITADEL will be done by you.
|
|
|
|
You can freely choose the infrastructure and location to host ZITADEL.
|
|
|
|
### Responsibilities
|
|
|
|
Your obligations while operating and using ZITADEL are detailed in our [terms of service](/legal/terms-of-service#your-obligations) given the provisions in our [acceptable use policy](/legal/policies/acceptable-use-policy).
|
|
When using ZITADEL Cloud, we may process data on behalf according to the [data processing agreement](/legal/data-processing-agreement).
|
|
|
|
In a self-hosted setup, you will be responsible for the cost, operations, and availability of your infrastructure.
|
|
For DDoS, bot, and threat detection and protection we rely on external services in ZITADEL Cloud.
|
|
In a self-hosted setup, it is your responsibility to secure the infrastructure to protect confidentiality, integrity, and availability of your data.
|
|
|
|
ZITADEL Cloud comes with pre-configured SMTP service, SMS service, and a generated domain name.
|
|
The SMTP service and SMS service are limited in use.
|
|
You should configure your own service providers for production use cases.
|
|
In a self-hosted setup, you will be responsible for SMTP / SMS services, domains and certificates.
|
|
|
|
| Responsibility | ZITADEL Cloud | Self-Hosted |
|
|
|------------------------|---------------------------|-------------|
|
|
| Data / Information | Customer | Customer |
|
|
| User Access | Customer | Customer |
|
|
| SMTP Service | Customer (trial: ZITADEL) | Customer |
|
|
| SMS Service | Customer (trial: ZITADEL) | Customer |
|
|
| Custom Domain / TLS | Customer (trial: ZITADEL) | Customer |
|
|
| DDoS & Bot protection | ZITADEL | Customer |
|
|
| WAF / Threat detection | ZITADEL | Customer |
|
|
| [Backup](#backup) | ZITADEL | Customer |
|
|
| Networking | ZITADEL | Customer |
|
|
| Compute / Scaling | ZITADEL | Customer |
|
|
| Database | ZITADEL | Customer |
|
|
| Application | ZITADEL | ZITADEL |
|
|
|
|
## Data location
|
|
|
|
Data location refers to a region, consisting of one or many countries or territories, where the customer's data is being hosted.
|
|
|
|
We can not guarantee that during transit the data will only remain within this region. We take measures, as outlined in our [privacy policy](../policies/privacy-policy), to protect your data in transit and in rest.
|
|
|
|
## Backup
|
|
|
|
Our backup strategy executes daily full backups and differential backups on much higher frequency.
|
|
In a disaster recovery scenario, our goal is to guarantee a recovery point objective (RPO) of 1h, and a higher but similar recovery time objective (RTO).
|
|
Under normal operations, RPO and RTO goals are below 1 minute.
|
|
|
|
If you have different requirements we provide you with a flexible approach to back up, restore, and transfer data (f.e. to a self-hosted setup) through our APIs.
|
|
Please consult the [migration guides](/guides/migrate/introduction) for more information.
|