---
title: "Configuration Overview"
slug: "configuration-overview"
updated: 2024-09-17T10:25:44Z
published: 2024-09-17T10:25:44Z
canonical: "help.hyperscience.ai/configuration-overview"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://help.hyperscience.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Configuration Overview

You can configure your Hyperscience instance to meet the infrastructure and business needs of your organization.

The options available to you depend on whether you have an on-premise / private cloud instance or a SaaS instance of Hyperscience.

## On premise / private cloud instances

Hyperscience allows you to customize many aspects of your on-premise / private cloud implementation to meet the needs of your organization.

The table below lists the various ways in which you can tailor your configuration, along with links to articles with more information.

### Making changes to the “.env” file

Configuration of on-premise / private cloud instances is managed through the “.env” file in the supplied bundle. The bundle contains an example “.env” file that needs to be filled in. You should delete any sections that you are not using. You may also need to add entries for some of the optional features if enabled. To learn more, see [Editing the “.env” file and running the application](/deployment/docs/editing-the-env-file-and-running-the-application).

### Configuration options for on-premise / private cloud instances

| **Configuration** | **Required?** | **Options** |
| --- | --- | --- |
| [Database](/deployment/docs/database-overview) | Yes | - [Oracle](/deployment/docs/oracle) - [PostgreSQL](/deployment/docs/postgresql) - [MSSQL](/deployment/docs/mssql) |
| [File Storage](/deployment/docs/file-storage-overview) | Yes | - [S3 Cloud Storage](/deployment/docs/s3-cloud-storage) - [Azure Blob Storage](/deployment/docs/azure-blob-storage) - [Google Cloud Storage](/deployment/docs/google-cloud-storage) - [Network-attached Storage / Local Storage](/deployment/docs/network-attached-storage-or-local-storage) |
| [Application Authentication](/deployment/docs/application-authentication-overview) | Yes | - [Built-in User Management](/deployment/docs/built-in-user-management) - [LDAP](/deployment/docs/ldap) - [OpenID Connect](/deployment/docs/openid-connect-oidc) - [SAML](/deployment/docs/saml) |
| [Security](/deployment/docs/security) | Only if your organization uses security certificates (e.g., TLS) |  |
| [Submission Retrieval Storage](/deployment/docs/s3-submission-retrieval-store) | Only if you plan on storing submission images on an external server | - [OCS](/deployment/docs/ocs-submission-retrieval-store) - [S3](/deployment/docs/s3-submission-retrieval-store) |
| [Proxy Server](/deployment/docs/proxy-server) | No |  |
| [VM CPU Cores](/deployment/docs/vm-cpu-cores) | Only if you are instructed to change these settings by a Hyperscience representative |  |
| [CPU Usage](/deployment/docs/cpu-usage) | Only if you need to limit the percentage of CPU resources consumed by the Hyperscience application |  |
| [Time Zone](/deployment/docs/time-zone) | Only if you want to set your application’s time zone to a time zone other than US/Eastern |  |
| [Connections](/deployment/docs/connections) | No |  |
| [Task-Polling Intervals](/deployment/docs/task-polling-intervals) | No |  |

## SaaS instances

If you have a SaaS instance of Hyperscience, Hyperscience configures your instance for you. You can work with Hyperscience to customize the parts of your system listed in the table below.

### Configuration options for SaaS instances

| **Configuration** | **Required?** | **Options** |
| --- | --- | --- |
| [Application Authentication](/deployment/docs/application-authentication-overview) | Yes | - [Built-in User Management](/deployment/docs/built-in-user-management) - [OpenID Connect](/deployment/docs/openid-connect-oidc) - [SAML](/deployment/docs/saml) |
| [Submission Retrieval Storage](/deployment/docs/submission-retrieval-storage-overview) | Only if you plan on storing submission images on an external server | - [S3](/deployment/docs/s3-submission-retrieval-store) |
| [Connections](/deployment/docs/connections) | No |  |