FusionAuth will install and run on nearly any system. We have done our best to document the supported configurations here. If you have any questions about platform support, please ask a question on the forum or open an issue on Github. If you have a licensed edition you may open a support request from your account.
Please read through this documentation and ensure you have met all of the requirements before continuing with the installation of FusionAuth.
FusionAuth will run on most platforms. The following list summarizes the supported platforms.
Linux - all distributions (64-bit)
macOS 10.8 (Mountain Lion) or newer
Windows Server 2012 R2 (64-bit) w/ Windows Management Framework 5.0 or newer
Windows 10 (64-bit) w/ Windows Management Framework 5.0 or newer
Docker, k8s and other container platforms are supported because the host operating system is based upon Linux.
The minimum memory required to run FusionAuth will vary depending upon the number of users you expect and the general intended system capacity.
If you have memory lying around, feel free to throw more at it - but in a multi-node configuration
1GB assigned per node should be very adequate.
This memory is required for the FusionAuth application. Other programs as well as the operating system take memory too. If you are going to run another application on the same server or a local database, increase your memory appropriately.
If you intend to run Elasticsearch and FusionAuth on the same host you will need to ensure the host has adequate memory for both services and ensure you have adequate disk space for the Elasticsearch index to be stored.
Considerations that may require a larger amount of memory:
Bulk importing users into FusionAuth. If you are importing in chunks of 250k to 500k it is possible FusionAuth will require additional memory to complete this request.
> 1k Tenants. There are tasks that require a full traversal of all tenants, when you have 1000’s of tenants these tasks may affect performance and will increase your memory requirements.
> 1k Applications. There are tasks that require a full traversal of all applications, when you have 1000’s of applications these tasks may affect performance and will increase your memory requirements.
MySQL 5.7.9 or newer.
IBM Compose for MySQL or other MysQL platforms that utilize MySQL Group Replication are not supported.
MariaDB and Percona are known to work, however these variants are not actively tested against by FusionAuth. Please do let us know if you run into an issue.
See MariaDB known issues on our GitHub issues.
PostgreSQL 9.5 or newer
Elasticsearch is optional, and may be leveraged for improving user search functionality. See the Core Concepts - User documentation for reference in configuration and usage.
If you will be running Elasticsearch on the same host as FusionAuth, please ensure there is adequate RAM for both services to operate normally. Elasticsearch may also protect the index by moving it to read-only if the underlying host is running low on disk space, ensure you have plenty of free storage for the Elasticsearch index.
Versions 6.3.x - 7.6.x are currently supported, later versions may work as well but may not have been tested for compatibility.
FusionAuth downloads MySQL drivers at install time. Due to the drivers' licensing, they cannot be bundled into the application. Prior to 1.16.0, the drivers were downloaded no matter which database you used. After that version, they are only downloaded if you are using MySQL.
If you are running FusionAuth in an environment with no network access and are using MySQL, you must download the MySQL driver jar file and place it in
If you are using a paid edition of FusionAuth, the instance must have outbound network connectivity for license id verification and metrics reporting. You must also allow access to enable advanced features provided by FusionAuth Reactor cloud services.
If you need specific hostnames to add to your network security or firewall safelist, please open a support ticket.