# Getting Started

- 6 Articles

## [License Keys](https://help.hyperscience.ai/deployment/docs/license-keys)

- Published on Sep 17, 2024  
This feature applies only to on-premise deployments of v39 and later. After installing or upgrading to Hyperscience v39 or later, you need to enter a license key before logging in to the application. A license key is required for each individual deployment.

## [Configuration Overview](https://help.hyperscience.ai/deployment/docs/configuration-overview)

- Published on Sep 17, 2024  
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.

## [Editing the ".env" file and running the application](https://help.hyperscience.ai/deployment/docs/editing-the-env-file-and-running-the-application)

- Updated on Jul 24, 2026  
- Published on Sep 17, 2024  
Applies to application machines only. You should have different ".env" files for the application and the trainer. The instructions on this page apply to application machines only. In particular, you should never run the following commands in your...

## [Starting, Restarting, and Stopping the Hyperscience Application](https://help.hyperscience.ai/deployment/docs/starting-restarting-and-stopping-the-hyperscience-application)

- Updated on Jan 21, 2025  
- Published on Sep 17, 2024  
Note that you can run Docker commands on Podman with the podman-docker package. To learn how to install the podman-docker package, see step 2 of Configuring Podman in RHEL 8. To start, restart, or stop the Hyperscience application...

## [System Attributes Questionnaire and Recommendations](https://help.hyperscience.ai/deployment/docs/system-attributes-questionnaire-and-recommendations)

- Published on Sep 17, 2024  
To help us support you as efficiently as possible, we would like you to provide the following information about your system. This article also gives recommendations and explains our reasons for gathering this data. Application servers / virtual machines may vary.

## [Best Practices for Sharing Files Across Machines](https://help.hyperscience.ai/deployment/docs/best-practices-for-sharing-files-across-machines)

- Published on Sep 17, 2024  
The following best practices for using shared files across all machines (a.k.a. virtual machines, or VMs) will ensure the highest levels of synchronization for your Hyperscience instance. Such an example is when you want to use the same SSL certificates across all environments.