Internet connectivity requirements

Despite the fact that the on-premise version of the WebSpellChecker package is designed to ensure data security and privacy by processing data in a controlled environment (e.g. behind a firewall), the Internet connection is required during the initial setup. These cases are:

1. Download the installation package from files.webspellchecker.com (AWS S3, USA).

2. Download default language models from files.webspellchecker.com (AWS S3, USA). This should be done during the installation process and not manually, to ensure all necessary dependencies are correctly addressed.

3. Download the additional component(s), language model(s), which are required for the AI-based proofreader engine work. The pre-trained language models for English, German, and Spanish are heavy. Thus, they are excluded from the installation package and have to be downloaded during the installation. These files are located on files.webspellchecker.com (AWS S3, USA). There is an option to skip downloading these files during the installation and do it manually later. For more details, visit Download and enable AI language models manually.

4. Download Named Entity Recognition (NER) models to ensure that named entities are correctly identified and not flagged as misspellings in English, Spanish, German languages and their dialects from: https://files.webspellchecker.com/models/NER/. There is an option to skip downloading these files during the installation and do it manually later. For more details, visit Download and enable NER models manually.

5. Activate a license and extend the license term. The license activation is mandatory for the proper work of the application. During the license activation process, the application server will attempt to connect to the external entry point (https://webspellchecker.com/api/licensing/v1/process-license, AWS EC2 + RDS, USA) to validate and confirm the license. It can be automatic or manual. Upon approaching the license due date, the application server will attempt to extend the license by default. If needed, this option can be disabled. For more details, visit Licensing.

Other than that, there won't be any other communication with the external entry points after the application deployment and while the license is valid.