---
title: "Air-gapped Workspace Configuration"
slug: "air-gapped-workspace-configuration"
description: "Configure a Rocket.Chat workspace in air-gapped mode. Learn offline setup steps, licence handling, and secure management for isolated environments."
tags: ["Premium"]
updated: 2026-05-18T20:34:40Z
published: 2026-05-18T23:04:08Z
canonical: "docs.rocket.chat/air-gapped-workspace-configuration"
stale: true
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.rocket.chat/llms.txt
> Use this file to discover all available pages before exploring further.

# Air-gapped Workspace Configuration

![](https://cdn.us.document360.io/6ae79a05-7252-45d0-96e8-8f375e07b1b2/Images/Documentation/Premium(1).svg)

Air-gapped workspaces are mostly isolated from the public internet, which limits the availability of certain cloud-based Rocket.Chat services like [mobile push notifications](/v1/docs/push) and access to the [Rocket.Chat Marketplace](/v1/docs/rocketchat-marketplace). This guide outlines the alternative configurations you can use to adapt your air-gapped workspace for these limitations.

## Set up push notifications in air-gapped workspaces

Since air-gapped servers lack internet connectivity and block most external connections, standard push notifications via FCM (Firebase Cloud Messaging) or APNS (Apple Push Notification Service) are unavailable by default. Here are some alternative options to consider for configuring push notifications in air-gapped workspaces:

1. **Allow controlled outbound traffic**

If your setup functions as a regular server with a strict firewall rather than a completely sealed network, you can configure outbound traffic to allow push notifications by opening specific ports according to FCM and APNS guidelines. Refer to the official [FCM](https://firebase.google.com/docs/cloud-messaging/network-configuration) and [APNS](https://support.apple.com/en-us/HT203609) documentation for the exact port and IP configuration.

> [!WARNING]
> This approach compromises the air-gapped security model and must be carefully considered by your security team.

1. **Build a custom push mechanism**

For workspaces that must remain fully air-gapped, develop a custom Rocket.Chat app that handles internal push notifications through your desired messaging infrastructure. Refer to the [Rocket.Chat Apps-Engine documentation](https://developer.rocket.chat/docs/rocketchat-apps-engine) for more details.

## Install apps in an air-gapped workspace

Rocket.Chat allows you to extend and bring new functionalities to your air-gapped workspace through [Rocket.Chat Apps](/v1/docs/rocketchat-marketplace). These apps can enhance collaboration, productivity, and workspace functionalities.

Depending on your workspace plan, there are two ways to install Marketplace apps in an air-gapped workspace:

1. [**Commercial**](/v1/docs/our-plans#commercial-plan)**,** [**Government**](/v1/docs/our-plans#government-plan)**, and** [**Defense**](/v1/docs/our-plans#defense-plan) **plans**: Request specific Marketplace apps through [Rocket.Chat Support](/v1/docs/support) using your registered contact.
2. [**Starter**](/v1/docs/our-plans#starter-plan) **workspace**: Manually download available public apps from the [Rocket.Chat Github repository](https://github.com/RocketChat).

Apps that require external cloud services will not function in an air-gapped environment. Here are some Rocket.Chat apps that can be used in an offline setting:

- [Data loss prevention](/v1/docs/data-loss-prevention-dlp-app)
- [Jitsi](/v1/docs/jitsi-app)
- [Pexip](/v1/docs/pexip-app)
- [Poll](/v1/docs/poll)

Alternatively, you can build a Rocket.Chat app tailored to your organization's custom needs. Refer to [Private App Development and Installation](/rocketchat-private-apps) to learn more.