> For the complete documentation index, see [llms.txt](https://docs.fortifiedid.se/installation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fortifiedid.se/installation/readme.md). # Installation Fortified ID products can be installed through Management Center, with platform-specific scripts, or as containers. Use this page to choose the installation method first, then continue to the platform-specific instructions for Linux, Windows, or container deployments. ## Installation methods The installation method controls how the product is installed, upgraded, and operated after installation. Linux and Windows are platforms; they are not installation methods by themselves. | Method | Use when | Benefits | Continue with | | ----------------- | ----------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------ | | Management Center | You want one place to install, upgrade, configure, and monitor Fortified ID products. | Reduces manual handling of installation media and service setup, gives administrators a product-aware UI, and is the preferred path when the environment will be managed through Management Center after installation. | [Linux](/installation/linux/management-center.md) or [Windows](/installation/windows/management-center.md) | | Script | You want to manage the product directly on the host operating system without Management Center. | Works well for controlled server environments, automation, and installations where configuration and service operations are handled outside Management Center. | [Linux Bash script](/installation/linux/script.md) or [Windows PowerShell script](/installation/windows/script.md) | | Container | You deploy and operate applications as container images. | Provides a predictable runtime environment, simple image-based versioning, and a deployment model that fits container platforms and orchestration tools. | [Container](/installation/container.md) | {% hint style="info" %} The application configuration is separate from the installation method. Choose the installation method based on how the product should be deployed, upgraded, and operated, then apply the product-specific configuration for the Fortified ID product you are installing. {% endhint %} ## When to use Management Center Use Management Center when the Fortified ID installation should be managed from a central administrative UI instead of only through files and host-level scripts. This is usually the right choice when administrators should install or upgrade products from the UI, manage product configuration in Management Center, monitor product state, or manage several Fortified ID products in the same environment. Management Center is also a good fit when the environment should have a more guided installation and operations model. It can install Management Center itself and let you select the Fortified ID products that should be installed during setup. Use a script-based installation instead when the environment is managed by server automation, when only a single product should be installed directly on a host, or when you explicitly do not want Management Center to manage the product lifecycle. For Management Center itself, see the separate documentation: [Management Center docs](https://docs.fortifiedid.se/management-center). ## Platform choices After choosing the installation method, select the platform: * [Linux](/installation/linux.md) for Linux servers, virtual machines, or Linux-based operations. * [Windows](/installation/windows.md) for Windows Server environments and Windows Services. * [Container](/installation/container.md) for Docker image based deployments. ## Online and offline installation Some environments allow the target server to download the required JRE and Fortified ID artifact directly during installation. This is the simplest path because the installer or script can retrieve the files when it runs. Restricted environments often require an offline installation flow. In that case, the required files are downloaded on another machine with internet access and then moved to the target server. This is especially relevant for Windows installations, where the documentation separates the download step from the actual installation step. Choose the online flow when the server has controlled access to the Fortified ID artifact repository. Choose the offline flow when the server has no internet access, when downloads must pass through a separate approval process, or when installation files must be staged before a maintenance window. ## High availability A single-node installation is enough for test environments, proof-of-concepts, and smaller deployments where downtime during maintenance is acceptable. Production environments often require more than one node so that traffic can continue during planned maintenance or node failure. When several nodes are used, place a load balancer in front of them and configure clustering for shared session handling. Start by installing each node with the selected installation method, then apply the [cluster configuration](/installation/cluster-configuration.md) instructions. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.fortifiedid.se/installation/readme.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.