Updated enterprise documentation
This commit is contained in:
@@ -35,4 +35,4 @@ Custom domains carry a registration fee (paid at checkout or when added post-sig
|
||||
| Annual renewal | Free | Varies by TLD |
|
||||
| Your own brand | No | Yes |
|
||||
| Available immediately | Yes | After registration |
|
||||
| Managed by Federated | Yes | No |
|
||||
| Managed by Federated | Yes | Yes |
|
||||
|
||||
@@ -11,8 +11,6 @@ toc: true
|
||||
|
||||
Federated Enterprise requires a minimum of **three domains** when you sign up, and this is a technical requirement of the platform — not an arbitrary constraint.
|
||||
|
||||
The underlying Federated Core platform uses multiple domains in tandem to support the various services that run on your Cores. These services include unified messaging, unified storage, authentication, and other components of the Core environment. Each domain serves a distinct functional purpose in the platform's routing and service delivery architecture.
|
||||
|
||||
Having three separate domains ensures that services can be isolated, routed independently, and remain resilient if one domain encounters an issue. It also allows the platform to properly configure email delivery, SSL certificates, and service endpoints across your environment.
|
||||
Each domain on your account needs its own SSL certificate to serve traffic securely. The platform provisions these certificates automatically, and three domains ensures there is enough capacity to cover all the certificates your environment needs to function correctly.
|
||||
|
||||
> **Note:** If you're unsure which domains to register, choosing the free Federated Domains option at checkout gets you a compliant, fully functional three-domain setup with no additional cost or configuration required.
|
||||
|
||||
Reference in New Issue
Block a user