Hyperscience SaaS

Hyperscience SaaS

Hyperscience SaaS Overview

Intelligent Automation as a Service. Organizations and government agencies use the Hyperscience Platform to enable a new era of human and machine collaboration. By leveraging the power of both professionals and technology, Hyperscience hyperautomation transforms workflows.

SaaS vs. On-premise / Private Cloud

Hyperscience offers two deployment types:

SaaS Service and Support

Because SaaS instances are deployed on infrastructure owned by Hyperscience, Hyperscience performs much of the maintenance that on-premise / private cloud customers complete themselves. This article highlights key aspects of the support provided.

Upgrading SaaS Instances

Hyperscience manages the upgrade process for SaaS instances. Your Hyperscience representative will let you know when a new major version of the application is available and work with you to coordinate the upgrade.

Upgrade processes

To learn more about the upgrade process, refer to the detailed documentation in the linked article.

API Access for SaaS Instances

API accounts have been deprecated and will be removed from the platform in a future version. For information on authenticating API requests, see Machine to Machine (M2M) Authentication with OAuth 2.0. Hyperscience SaaS uses an authentication mechanism to secure access.

IP Allowlisting

Deprecated feature
The IP Allowlisting settings have been removed from SaaS deployments. All outgoing traffic is now allowlisted by default. When creating connections that require data to be sent from your Hyperscience SaaS environment to outside sources, refer to the documentation for best practices.

IAM Roles for Input Blocks and Output Blocks

This feature is available in SaaS environments running v40.2 or later. In v40.2 and later, you can use Amazon Web Services (AWS) Identity and Access Management (IAM) roles to authenticate connections for the following blocks: S3 Listener Input Blocks, S3 Listener Output Blocks.

FedRAMP Security Admin Guide

Administrative and privileged accounts
Relevant requirements: FRR-RSC-01, FRR-RSC-02, FRR-RSC-03, FRR-RSC-06
Related articles: Permission Groups. Hypercell uses permission groups to define general user authorization. These permission groups dictate access levels.