Is FIPS included in all Rocket.Chat plans?
FIPS is available on Government and Defense plans and requires the FIPS license add-on.
Do users see any changes in a FIPS-complaint workspace UI ?
FIPS mode affects only the underlying cryptographic implementation used by the workspace. It does not introduce any changes to the user interface or standard user workflows.
Do I need a special deployment for FIPS in Rocket.Chat?
Organizations that require FIPS compliance must deploy Rocket.Chat using the designated FIPS-compliant Docker images while deploying their workspace.
Are Marketplace apps and custom apps supported in FIPS mode?
Yes. Marketplace and custom apps are supported in FIPS deployments.
Are external integrations covered by FIPS mode?
External integrations operate outside Rocket.Chat's cryptographic boundary and may implement their own cryptographic mechanisms. If FIPS compliance is required for an integration, it must be evaluated independently.
Can I migrate an existing standard Rocket.Chat deployment to the FIPS image?
Yes. You can migrate an existing workspace from the standard Rocket.Chat image to the FIPS image. However, this migration is not recommended without taking a full database backup first.
Before migrating, review the known FIPS limitations and verify that your workspace does not depend on unsupported functionality. A full backup allows you to roll back safely if you encounter any issues during or after the migration.