Own Domain, Axis Hosted Domain, and Hybrid Approach Feature Comparison Matrix
The following table summarizes when to use your own domain, Axis hosted domain, and hybrid approach:
| Feature | Own Domain | Axis Hosted Domain | Hybrid Approach | Description |
|---|---|---|---|---|
| Easier and faster to deploy. | Yes | Yes (for POC only) | No | Requires minimal configuration. |
| Higher Performance | Yes | No | No | Provides higher performance because URL rewriting is not required |
| Better User Experience | Yes | No | No | Users access the URL format that they would normally see instead of seeing a URL. |
| Requires changes to public DNS records | Yes | No | No | |
| Requires Customer Support assistance to configure URL rewriting for the application to work properly. | Sometimes | No | No | If you have all your domains for deploying an application, customer support is not required for the Axis hosted domain. Note: If you need help discovering your domains for an application, work with Customer Support. |
| Requires that you log into your application and record all the internal and SSO domains that your application uses that need to go through the Axis Cloud. | No | Sometimes | Yes | |
| Supports existing SSO/SAML configured web apps | Yes | Yes | No | For customers who have web apps they have already been configured in an IdP, such as Okta, these apps are internal and already have Okta configured to use the URL, such as https://myapp.company.com. For this to work through the Atmos Agent, you will need to use your own domain and domain certificate to match that URL. Important: If you are using an Axis hosted domain, you will not be able to launch your application from Okta because Okta uses the original URL of the application. |
Updated about 2 years ago