# What breaks when project management software loses internet access > Source: > Published: 2026-07-29 08:24:58+00:00 Run a project management platform on a laptop in a basement with no network cable and it will probably keep accepting ticket updates. Cut the same platform off from the internet inside a regulated production environment and the failure surface shifts to places nobody tests during a cloud trial: license seat synchronization, telemetry endpoints, identity provider metadata refresh, package repositories for upgrades, and model inference for AI assistants. The database is still local. The system is still broken in the ways that matter for long-term operations. The defining property of air-gapped software is not where its database is installed. It is the set of hidden dependencies the product carries and the operating cycle those dependencies impose once outbound connectivity is removed. A platform that phones home for license validation, usage analytics, or telemetry will degrade or halt the moment that call fails. A platform that assumes an online package repository for upgrades cannot be patched without re-architecting its release pipeline. These are not deployment preferences. They are operating constraints that determine whether the software can survive its first disconnected quarter. [Try for free](https://ones.com/sign_up?utm_campaign=14604708-EN%20BLOG%20SEO&utm_source=blog&utm_medium=cta_side) ## The License and Telemetry Trap Most enterprise software treats licensing as a live conversation between the application and a vendor-controlled server. Seats are counted, entitlements are checked, and grace periods expire into read-only mode. In an air-gapped environment that conversation is impossible by design, so the product must complete the entire licensing cycle offline. ONES handles license activation through an offline file and does not require online seat synchronization, which removes the most common silent failure: a platform that runs for thirty days and then locks out its users because it cannot reach a validation endpoint. Telemetry is the second hidden dependency. Products instrumented for usage analytics and product telemetry often assume they can ship events outbound. When that path is blocked, the behavior ranges from queued events consuming disk to background retry loops consuming CPU. ONES disables usage analytics, product telemetry, and outbound calls by default in its air-gapped deployment. The point is not the feature list. The point is that telemetry is a runtime dependency, and disabling it at the network layer without application-level support creates operational debt that surfaces as resource exhaustion or alerting noise. [Try for free](https://ones.com/sign_up?utm_campaign=14604708-EN%20BLOG%20SEO&utm_source=blog&utm_medium=cta_side) ## Identity, Storage, and the Integration Surface Identity is where air-gapped assumptions collapse most quickly. A platform may support SSO in its cloud edition, but if that SSO implementation depends on federated metadata refresh from a public endpoint, it will stop accepting new tokens once the cached metadata expires. The integration has to work with directory services and identity providers that are themselves reachable only inside the restricted network. ONES supports AD, LDAP, Azure AD, SAML, and OIDC identity integrations, which means the authentication path can be pointed at internal infrastructure rather than public endpoints. The same dependency logic applies to storage and observability. Object storage for attachments, log aggregation, and metrics collection all need targets that are reachable without crossing the air gap. ONES supports S3-compatible storage, internal load balancers, Prometheus and Grafana, plus optional SIEM integrations including ELK, Splunk, and Azure Monitor. Each of these is a statement about where data flows when the internet is absent. A platform that hardcodes a vendor-hosted storage bucket or a cloud-native logging service cannot be made air-gapped by changing a configuration flag. The integration surface has to be designed for internal endpoints from the start. [Try for free](https://ones.com/sign_up?utm_campaign=14604708-EN%20BLOG%20SEO&utm_source=blog&utm_medium=cta_side) ## Upgrades, Rollbacks, and the AI Dependency The operating cycle of air-gapped software is dominated by the upgrade path. In a connected environment, upgrades are a pull operation: the platform fetches new images or packages from a registry, applies them, and restarts. In an air-gapped environment, that pull becomes a manual transfer of signed bundles across a controlled boundary, followed by an install step that must not reach outward for dependencies. ONES handles installation, upgrades, and rollback using offline packages, and its air-gapped deployment supports Kubernetes, K3s, bare metal, and virtual machines, from single-node to high availability. The infrastructure flexibility matters less than the fact that the entire release cycle, including rollback, is modeled as an offline operation. A platform that can install offline but requires online access to roll back is not air-gapped. It is a deployment that has not yet failed. The newest hidden dependency is AI. Assistants and copilots embedded in project management tools often call public model endpoints directly. In an air-gapped environment those calls fail, and the assistant becomes a disabled feature or a source of error noise. ONES Assistant and ONES MCP can connect to an organization-approved model through an OpenAI-compatible API, which means the inference endpoint is something the organization controls inside its own boundary. The trade-off remains: the assistant is only as good as the approved model, and the organization bears the cost of hosting or brokering that model. Air-gapping AI does not eliminate the dependency. It relocates it. What actually breaks is the assumption that local installation equals operational independence. The database can be on bare metal in a locked room and the platform can still fail on license validation, telemetry retries, metadata refresh, package fetches, or model inference. Air-gapped software is defined by its operating cycle, the offline completeness of that cycle, and the set of dependencies the product is willing to treat as internal. Everything else is a connected product with a longer network cable. More detail on one vendor’s approach is at [https://ones.com/airgap](https://ones.com/airgap). ### Ready to Improve How Your Team Works? Contact us today. Optimize the way you work.