"It's a non-starter unless you can guarantee zero external connections," - CISO, U.S. federal contractor.
His voice carried the unmistakable tension of someone who'd just spent hours in a compliance review meeting. "We love your platform, but our federal contracts require complete isolation. Not 'minimal connections' or 'only essential traffic'—I mean nothing leaves our network. Is that something you can do?"
That call came on a Thursday afternoon last year, just as we were celebrating a major enterprise win. By Monday morning, our leadership had made the decision: we would build a truly air-gapped version of Plane. Six months later, what started as a frantic customer request has become one of our most strategic product offerings.
After months of development, our air-gapped capability has reached general availability. This post explores the journey of building this specialized deployment option for regulated industries where data sovereignty isn't just preferred—it's mandatory.
Updated November 2026: Plane Airgapped is available with Enterprise Grid (minimum 100 seats) and runs on Docker Compose or Kubernetes. The technical sections below reflect how it works today.
What regulated teams asked for
The demand for truly isolated software environments has been consistent across several regulated industries. Defense contractors operating under International Traffic in Arms Regulations (ITAR) require complete network isolation. Government Cloud (GovCloud) users need Federal Risk and Authorization Management Program (FedRAMP) compliant solutions with no external dependencies. Healthcare organizations handling Protected Health Information (PHI) and financial institutions managing sensitive transaction data both face similar constraints.
Even with our robust self-hosted option, we kept hearing the same feedback from legal and compliance teams: "Private cloud" solutions that still require Virtual Private Network (VPN) tunnels don't meet their stringent requirements.
Strategic fit
Developing an air-gapped deployment option completes Plane's deployment trilogy:
- Cloud → Our fully-managed SaaS offering with all the convenience and none of the maintenance
- Self-Hosted → Customer-managed deployment with control over data residency
- Air-Gapped → Complete isolation for the most stringent security requirements
For many of these teams, an air-gapped option was the only way Plane could pass a security review at all.
More importantly, the air-gapped version gives us a hardened security baseline that benefits every Product Stock Keeping Unit (SKU) in our portfolio. All deployment options now leverage:
- Comprehensive supply-chain scanning to validate components
- Rigorous CI/CD pipeline validation with hermetic builds
- Detailed artifact provenance verification
What started as a specialized requirement has evolved into a company-wide commitment to security excellence that strengthens our entire product line.
What an "air-gap" means in Plane
Building a truly air-gapped solution required rethinking how every component of Plane operates. Here's a practical breakdown of the key differences between our deployment options:
Component | Connected self-hosted | Airgapped |
Images | Pulled from Plane’s public registry | Copied on a connected machine and pushed to your internal registry |
Licensing | License key validated online against prime.plane.so | Offline license file, uploaded in God mode → Billing |
Updates | Pull new images and upgrade in place | New images and the version’s Compose file and env template (or Helm chart) are transferred through your approved process |
Deployment | Docker or Kubernetes | Docker Compose or Kubernetes (Helm) |
Network access | Outbound HTTPS to prime.plane.so for licensing | No outbound access needed; external egress blocked at the network |
With an air-gapped installation, your Plane instance lives completely within your security perimeter. It doesn’t need any outbound connection to run, to validate its license, or to update. Licensing works from an offline file, and new versions arrive through your own transfer process. Your network should still block external egress, as it would for any air-gapped enclave. This is what distinguishes a true air-gapped deployment from “private” or “isolated” options that still keep a connection to external networks.
Everything Plane needs is collected on a connected machine: the Plane container images, the Docker Compose file and environment template for your version (or the Helm chart for Kubernetes), and the license file. Your team reviews them, then moves them into the isolated network through its approved channels. Updates follow the same path.
Inside the build
What you bring into the network
A Plane Airgapped deployment is assembled from a short list of artifacts:
- Plane application images: web, admin, space, live, monitor, backend, silo, email, proxy, Plane AI, and node runner, plus iframely. These are copied with crane from Plane’s registry into your internal registry.
- Infrastructure images, if you run the bundled services in Docker: PostgreSQL, Valkey, RabbitMQ, MinIO, and OpenSearch. Your team pulls these separately, or points Plane at existing internal services.
- Deployment configuration: the Docker Compose file and plane.env template for your Plane version, or the Plane Enterprise Helm chart for Kubernetes.
- The license file: an offline Enterprise Grid license, downloaded from the Prime portal on a connected machine.
Plane’s release images are cosign-signed with build provenance, so your team can verify them on the connected side before transfer. Hashes and SBOMs don’t ship alongside the images; if your chain-of-custody process requires them, request them from Plane.
Installing offline
Installation uses tools your infrastructure team already runs:
- Docker: place the Compose file and plane.env in your install directory, point the image references at your internal registry, and start Plane with
docker compose --env-file plane.env up -d. Requires Docker 24 or later with the Compose plugin. - Kubernetes: install the Plane Enterprise Helm chart with values that reference your private registry, storage class, and internal certificate authority. Requires Kubernetes 1.31–1.33, Helm 3, an IngressClass, a StorageClass, and cert-manager with an internal CA.
Then activate Enterprise Grid by uploading the offline license file in God mode → Billing. Plane’s base sizing is 2 CPU cores and 4 GB of RAM, with 8 GB recommended for production.
Air-gap testing
To ensure true isolation, we've rigorously tested the entire deployment process in environments with zero external connectivity. Our test environments simulate the strict network restrictions found in regulated industries, with security controls that flag and block any attempted external connections.
This testing approach has helped us refine our installation process to work flawlessly even in the most restrictive network environments, ensuring that when you deploy Plane in your air-gapped environment, it simply works.
Hard problems, solved
Supply-chain trust
The biggest security challenge in air-gapped environments is establishing trust in the software supply chain. Without internet connectivity, you can't verify packages against online repositories or check for vulnerabilities in real-time. So the trust work happens before anything crosses the air gap:
- Signed images: Plane’s release images are cosign-signed with build provenance, so they can be verified on the connected side.
- Your review gate: images and configuration are scanned and approved in your connected staging zone, like any other software entering the enclave.
- Evidence on request: hashes and SBOMs aren’t bundled with the images. Teams that need them for audit records can request them from Plane.
These measures ensure that when you install Plane, you can be confident it's exactly what our development team built—nothing more, nothing less.
External integrations
Project management software typically relies heavily on external services, which presents a challenge in air-gapped environments. We've addressed this by implementing a webhook proxy pattern:
- All external integration points are clearly documented
- Integration configuration includes connection specifications
- An integration allowlist lets your security team selectively open specific ports inside your DMZ
For example, if you need GitHub integration, our documentation provides exact network requirements that your team can review, approve, and implement according to your security policies.
Keeping size manageable
Air-gapped packages can quickly grow unwieldy, making physical transfer difficult. We keep the images as small as we can through several techniques:
- Multi-stage builds - Our Docker images use multi-stage builds to eliminate development dependencies
- Layer optimization - We carefully arranged Dockerfile layers to maximize reuse across services
- Pruning debug symbols - Production images are stripped of debugging information
These optimizations ensure that transferring Plane into your secure environment remains practical, whether through approved USB devices or internal artifact repositories.
Customer zero
Our first air-gapped deployment was with a defense contractor working under ITAR (International Traffic in Arms Regulations) restrictions. Their requirements were among the strictest possible: no internet connectivity whatsoever, physical isolation, and compliance with federal security controls.
The deployment process was remarkably smooth—from receiving the release artifacts to first login took just 45 minutes. According to their security team, Plane "met ITAR enclave rules with zero code changes required," a testament to our design approach.
What surprised the customer most was performance. Without the latency of internet connectivity, their air-gapped deployment actually delivered faster response times than our SaaS offering.
What’s changed since launch
- Kubernetes support: Plane Airgapped now deploys with the Plane Enterprise Helm chart as well as Docker Compose.
- FIPS 140-3 images: FIPS images are available for the web, admin, and live services, for teams running FIPS-mode hosts with their own secrets provider and certificate authority.
- Offline licensing through the Prime portal: administrators download the Enterprise Grid license file on a connected machine and activate it in God mode, with no runtime connection to Plane.
Ready for air-gapped deployment?
If your organization operates in regulated industries like defense, healthcare, or finance—or if you simply need the highest level of data isolation, Plane’s air-gapped deployment might be exactly what you’ve been looking for. It’s available with Enterprise Grid for deployments of 100 seats or more.
Our security team specializes in helping organizations navigate the unique challenges of air-gapped environments. They'll work with you to evaluate requirements, plan the deployment, and ensure a smooth implementation that meets your security and compliance needs.
Because in environments where nothing can leave the network, the right software still needs to deliver everything.
This article was collaboratively written by the Plane engineering, security, and marketing teams.
Frequently asked questions
Q1. What is Plane Airgapped?
Plane Airgapped is a self-hosted edition of Plane built to run on networks with no internet access. All images, configuration, and the license file are brought in through your approved transfer process, and the instance runs without any outbound connection.
Q2. Which plan includes Plane Airgapped?
Plane Airgapped is available only with Enterprise Grid, with a minimum commitment of 100 seats. Every active user and pending invite on the instance counts as a seat.
Q3. Can Plane Airgapped run on Kubernetes?
Yes. Plane Airgapped deploys with Docker Compose or with the Plane Enterprise Helm chart on Kubernetes 1.31–1.33.
Q4. How do you upgrade Plane Airgapped?
On a connected machine, copy the new Plane images to your internal registry and download the Compose file and environment template (or Helm chart) for the target version. Transfer them into the isolated network, carry your existing configuration into the new templates, and redeploy. Then confirm the license in God mode → Billing.
Q5. Does Plane Airgapped need internet access for licensing?
No. Licensing uses an offline license file, downloaded from the Prime portal on a connected machine and uploaded in God mode → Billing. The running instance doesn’t contact Plane’s licensing service.
Further reading:
Recommended for you




