Hyperscience offers two deployment types:
On-premise / private cloud — These deployments give you full control over your infrastructure and maintenance.
SaaS — SaaS deployments are ideal for organizations who want to maximize the benefits of Hyperscience while minimizing the time, infrastructure, and human resources required to do so.
Both SaaS and on-premise / private cloud offer the same Hyperscience solution. If you would like to migrate your on-premise / private cloud Hyperscience deployment to SaaS, you should be aware that there are some differences between the two, as described in the table below.
SaaS | On-premise / private cloud | |
|---|---|---|
Infrastructure | Hyperscience manages all infrastructure. Key features of SaaS instances include:
| Hyperscience allows you to customize your instance's infrastructure to meet the needs of your organization. For example, you can select from several options for databases, file stores, and submission retrieval stores. See Infrastructure Overview and Configuration Overview for more information. |
Regional availability | Hyperscience SaaS is available globally with the majority of environments hosted in the United States and Frankfurt, Germany. If your use case requires a service hosted outside of North America or Europe, contact your CX representative to check for availability. | There are no restrictions on where you can deploy on-premise / private cloud instances of Hyperscience. |
Hyperscience's access | While Hyperscience manages the infrastructure of SaaS instances, under normal circumstances, no one from Hyperscience will access your instance without your permission. For more details, see SaaS Service and Support. | Hyperscience cannot access your instance. You may share your screen during support calls, if you think it would be helpful and your organization allows it. |
Authentication | SaaS instances provide a built-in authentication method and integrations with SAML and ODIC providers. For added security and flexibility, we leverage Okta in our identity-management layer. | Hyperscience offers its own built-in authentication method. You can also choose to integrate your instance with one of our supported external authentication providers. To learn more about available authentication methods, see Application Authentication Overview. |
Integrations | SaaS instances also allow you to integrate with a variety of input and output systems. Supported connections include many of the same connections available in on-premise / private cloud deployments. Examples include Box Folder Listener, Email Listener, HTTP Notifier, and Message Queue input and output connections. You may need to create firewall pinholes for certain connection types. To learn more, see the documentation for Input Blocks and Output Blocks for your version of Hyperscience. | You can integrate your instance with a number of input sources and downstream systems. Examples of connections include Message Queue input and output connections, Email Listener, Folder Listener, and HTTP Notifier. To learn more about supported connection types, see Connections. Outside of your instance, you can also set up UiPath, Bizagi, and Box Hyperscience connectors. For more information, see the UiPath Integration, Bizagi Integration, and Box Integration articles for your version of Hyperscience. |
Monitoring system health | In SaaS deployments, the System & Health page does not include information about components that are fully managed by Hyperscience, including application and trainer machines, databases, and the file store. | In v30 and later, you can monitor key aspects of system health on the System & Health page of the application (Administration > System & Health). For example, you can check the health of your application and trainer machines, database, and file store, along with the number of submissions, jobs, flows, and trainer tasks completed in the past 24 hours. To learn more about this page, see System & Health Page. You can also set up monitoring methods outside of your Hyperscience instance to check metrics like RAM and storage usage. For more information about recommended monitoring practices, see Monitoring Hyperscience. |
API access | For session management and ease of integration, we provide a Client Library for authenticating to and using our API. System Admins can create API accounts for specific permission groups in Administration > API Accounts. For more information, see API Access for SaaS Instances. | Your organization's users can access our API via token-based authentication. By default, users in the System Admin, Business Admin, and API User permission groups can send API requests. To learn more about API authentication, see our API documentation and the Managing API Tokens article for your version of Hyperscience. |
Upgrades | Hyperscience completes the upgrade process for you, though you will have control of the training of models to ensure the best performance for your documents. To learn more, see Upgrading SaaS Instances. | While Hyperscience can support you during the upgrade process, you are responsible for completing each step. For more information, see the Upgrading Hyperscience section of this site. |
Support | We also provide support for our SaaS instances 24 hours a day, everyday. In addition to providing support upon request, we perform regular maintenance work on your instance during established maintenance windows. To learn more, see SaaS Service and Support. | Support is available 24 hours a day every day of the year. Hyperscience cannot access your instance, but our Support team will help you troubleshoot your issues and guide you through the resolution process. |