How to Manage Application Updates via Local File Server or Cloud for AirgapAI

Become the Custodian of Stability—Updates When You Want, From Where You Want, With Zero Surprises.

For Information Technology (IT) administrators, ensuring the stability, security, and compliance of enterprise software is paramount. This guide is specifically crafted for IT professionals responsible for deploying and managing Iternal Technologies' AirgapAI application within their organizations. Our goal is to empower you with comprehensive control over AirgapAI's update mechanisms, enabling predictable deployments, enhanced security, and seamless integration into your existing IT infrastructure, whether you operate in highly regulated environments requiring offline updates via a local file server or prefer the convenience of cloud-based distribution.

This detailed training article will walk you through the essential steps to configure AirgapAI's Update Manager, set up local file server Uniform Resource Locators (URLs) for offline updates, and strategically manage application versions by editing the updaterConfig.json file. We will delve into advanced strategies such as version pinning and staged rings, providing you with the tools to maintain control and compliance, particularly for sensitive or air-gapped systems. By the end of this guide, you will be equipped to manage AirgapAI updates with confidence, ensuring your workforce benefits from the latest features while upholding your organization's security posture.

1. Introduction to AirgapAI's Update Management

AirgapAI, developed by Iternal Technologies, is a powerful, locally installed Large Language Model (LLM) platform designed for maximum security, efficiency, and accuracy. Unlike cloud-dependent Artificial Intelligence (AI) solutions, AirgapAI operates entirely on the client device, such as a Dell Artificial Intelligence Personal Computer (AI PC), eliminating external network dependencies for its core Large Language Model inferencing and data processing. This air-gapped architecture is crucial for organizations with stringent data sovereignty requirements, enabling fast AI wins without compromising security.

For IT administrators, managing software updates in such an environment demands precision and control. AirgapAI's built-in Update Manager is designed with enterprise needs in mind, offering flexibility to align with diverse deployment strategies, from direct cloud updates to highly controlled, internal network distributions. This control is vital not only for application stability but also for ensuring that new features, security patches, and updated Large Language Models (LLMs) or datasets are rolled out in a manner that adheres to organizational policies and compliance mandates.

2. Understanding AirgapAI's Core Value Proposition (For Context)

Before diving into the mechanics of updates, it's essential to briefly understand AirgapAI's unique strengths, as these underpin the importance of its secure and flexible update mechanisms:

100% Local and Secure Artificial Intelligence: AirgapAI runs entirely on the user's Personal Computer, ensuring that sensitive data never leaves the device. This provides unparalleled data sovereignty and eliminates the risks associated with external network breaches or cloud data storage. This core principle extends to its update process, allowing for offline updates that maintain this isolation.
Cost-Effective and Perpetual Licensing: Unlike subscription-based cloud AI alternatives that incur recurring per-user fees, AirgapAI offers a one-time perpetual license per device. This significantly reduces Total Cost of Ownership (TCO) and simplifies budget management for IT departments.
Exceptional Large Language Model Accuracy with Blockify: Iternal Technologies' patented Blockify technology is integral to AirgapAI. It ingests vast datasets, condenses them into modular "blocks" of trusted information, and improves Large Language Model accuracy by up to 7,800%. Managing updates for Blockify datasets is a critical aspect of ensuring the continued reliability of your AI outputs.
Optimized for Artificial Intelligence Personal Computers: AirgapAI leverages the full capabilities of modern AI PCs, distributing workloads across the Central Processing Unit (CPU), Graphics Processing Unit (GPU), and Neural Processing Unit (NPU) for optimal performance and power efficiency. Updates may include optimizations for new hardware or improved utilization of existing components.

Given these advantages, the ability to manage AirgapAI's application, Large Language Model, and dataset updates with granular control is a key enabler for secure, scalable, and compliant Artificial Intelligence adoption across your enterprise.

3. The Two Paths to Updates: Local File Server versus Cloud

AirgapAI's Update Manager provides flexibility for how application and data updates are delivered to end-user devices. Understanding these two primary paths – Local File Server and Cloud – is crucial for IT administrators to implement a strategy that best fits their organization's security, compliance, and infrastructure requirements.

3.1. Local File Server Updates (Offline Updates)

This method is ideal for organizations operating in highly secure, air-gapped, or regulated environments where external network access for software updates is restricted or prohibited. It grants IT administrators complete control over the update lifecycle, ensuring that only approved and verified versions of AirgapAI, its Large Language Models, and associated datasets are deployed.

Key Benefits:

Enhanced Security: Prevents direct communication with external update servers, minimizing potential attack vectors. All updates originate from a trusted, internal source.
Compliance: Meets stringent regulatory requirements for data sovereignty and software provenance, common in sectors like government, defense, finance, and healthcare.
Predictable Deployments: IT teams can test updates thoroughly in a controlled environment before distributing them, ensuring compatibility and stability across the fleet.
Bandwidth Efficiency: For large-scale deployments, updates can be hosted once on an internal server, reducing external bandwidth consumption and speeding up distribution across the local network.
Offline Capability: Enables devices to receive updates even when completely disconnected from the public internet, critical for field operations or secure facilities.

3.2. Cloud-Based Updates

The cloud-based update mechanism allows AirgapAI applications to receive updates directly from Iternal Technologies' designated cloud update servers. This is a convenient option for organizations with less restrictive network policies, offering an "always-on" approach to keeping the application current.

Key Benefits:

Simplicity: Minimal IT overhead for update management, as updates are automatically fetched from the cloud.
Timely Access to Latest Features: Users receive the newest application versions, Large Language Models, and security patches as soon as they are released.
Scalability: Easily supports large deployments without the need for internal update infrastructure.

While convenient, cloud-based updates may not be suitable for all organizations due to security policies or limited external network access. The following sections will focus primarily on configuring AirgapAI for robust local file server deployments, giving IT administrators maximum control.

4. Configuring the Update Manager for Local File Server Deployment

The heart of AirgapAI's configurable update process lies within a specific configuration file: updaterConfig.json. By modifying this file, IT administrators can direct the application to retrieve updates from an internal, locally hosted file server rather than a default cloud Uniform Resource Locator.

4.1. Locating the `updaterConfig.json` File

The updaterConfig.json file is typically found within the AirgapAI application's installation directory, specifically in the auto-updater resources folder.

Default Path (Example for Windows):

C:\Users\<YourUsername>\AppData\Local\Programs\AirgapAI Chat\resources\auto-updater\updaterConfig.json

Note for Enterprise Deployment: In a managed enterprise environment, IT administrators would typically modify this file within their golden master image or deploy a pre-configured version of this file to all end-user devices via their standard image management applications (e.g., Microsoft Intune, System Center Configuration Manager, or similar tools). This ensures that all AirgapAI installations on the network inherit the desired update configuration from day one.

4.2. Editing the `updaterConfig.json` File

This JSON (JavaScript Object Notation) file defines the update server endpoints for different operating system and architecture combinations. You will need to edit this file to point to your internal update server.

Example updaterConfig.json Structure (from documentation):

{
  "win32-x64-prod": {
    "readme": "",
    "update": "https://d30h3ho4go3k4y.cloudfront.net/releases/prod/public/chat-assistant/prod/public/1.0.2/AirgapAI Chat Setup 1.0.2.exe",
    "install": "https://d30h3ho4go3k4y.cloudfront.net/releases/prod/public/chat-assistant/prod/public/1.0.2/AirgapAI Chat Setup 1.0.2.exe",
    "version": "1.0.2"
  }
}

Understanding the Key-Value Pairs:

"win32-x64-prod": This is the platform identifier, indicating the operating system (Windows 32-bit/64-bit) and the production environment. You will likely only need to modify this section for standard Windows deployments.
"readme": An optional field for a link to release notes or a readme file. You can update this to point to an internal document if desired.
"update": This is the critical Uniform Resource Locator (URL) that the AirgapAI application checks for the latest update package. When the application detects a new version number (defined by "version"), it will attempt to download the file from this URL.
"install": This URL typically points to the full installer package for a specific version. It might be used for initial installation or a complete reinstallation to a specific version.
"version": This string indicates the current expected version number. The AirgapAI Update Manager compares the version specified here with the version of the application currently running on the device. If the update Uniform Resource Locator points to a package with a higher version number, an update will be triggered. This field is crucial for version pinning and controlled rollouts, as discussed in Section 5.1.

Steps to Modify:

Open updaterConfig.json: Use a plain text editor (like Notepad++, Visual Studio Code, or even Notepad) to open the updaterConfig.json file.
Identify the Target Platform: Locate the object corresponding to your deployment environment (e.g., "win32-x64-prod").
Update update and install URLs: Change the values for "update" and "install" to point to the Uniform Resource Locators on your internal file server where the AirgapAI installer packages will be hosted.
- Example for a Local File Server:
```
{
  "win32-x64-prod": {
    "readme": "http://your-internal-server/airgapai/releases/readme.txt",
    "update": "http://your-internal-server/airgapai/releases/prod/1.0.3/AirgapAI Chat Setup 1.0.3.exe",
    "install": "http://your-internal-server/airgapai/releases/prod/1.0.3/AirgapAI Chat Setup 1.0.3.exe",
    "version": "1.0.3"
  }
}
```
- Ensure the Uniform Resource Locators are accessible from the client devices where AirgapAI is installed.
- The Uniform Resource Locators should point directly to the executable .exe installer files for the respective versions.
Update version: Change the "version" string to match the version number of the AirgapAI installer you are making available on your internal server. This is critical for the Update Manager to correctly identify if an update is available.
Save the File: Save your changes to updaterConfig.json.

4.3. Preparing Your Local File Server

Once you've configured the updaterConfig.json to point internally, you need to set up your internal file server (e.g., a Microsoft Internet Information Services (IIS) server, Apache HTTP Server, or a simple network share accessible via HTTP/S).

Required Files to Host:

AirgapAI Application Installer: This is the executable .exe file (e.g., AirgapAI Chat Setup 1.0.3.exe). You will need to host new versions of this file for each update you wish to deploy.
Optional: Release Notes/Readme: If you specified a readme Uniform Resource Locator, host the corresponding text file.

Best Practices for File Server Structure:

Create a logical directory structure on your internal server to manage different versions. For example:

your-internal-server/
└── airgapai/
    └── releases/
        └── prod/
            ├── 1.0.2/
            │   └── AirgapAI Chat Setup 1.0.2.exe
            ├── 1.0.3/
            │   └── AirgapAI Chat Setup 1.0.3.exe
            └── readme.txt

This structure allows you to easily manage different versions and point the updaterConfig.json to the specific version you want to deploy.

4.4. Pushing Updates (Deployment to Devices)

After configuring updaterConfig.json and staging the update files on your local server, the actual deployment to end-user devices can be managed through your existing IT image management solutions.

Initial Deployment: For new device imaging, include the pre-configured updaterConfig.json (pointing to your internal server) and the AirgapAI application installer as part of your golden master image.
Ongoing Updates: When a new version of AirgapAI is available on your internal server, the local application's Update Manager will detect the new "version" specified in its own updaterConfig.json compared to the version it finds at the update URL. The application can then prompt the user to install the update or, if configured for silent updates (advanced deployment), install it automatically.
- Alternatively, IT can push the updated updaterConfig.json file (with a higher "version" number) and the corresponding new installer package to target devices using tools like Microsoft Intune, System Center Configuration Manager (SCCM), Group Policy Objects (GPO), or other enterprise software distribution systems. This method allows for a controlled, centrally managed update rollout.

5. Advanced Update Management Strategies

For robust enterprise deployments, merely pointing to a local server is just the beginning. IT administrators often require more sophisticated strategies to manage software updates effectively.

5.1. Version Pinning and Controlled Rollouts

Version pinning allows IT to dictate exactly which version of AirgapAI (application, Large Language Models, and datasets) should be running on client devices. This prevents unwanted automatic updates and ensures consistency across a user base.

How to Implement Version Pinning:

Host Specific Versions: Ensure your local file server hosts all approved versions of AirgapAI installer packages.
Set updaterConfig.json version Field: Modify the version field in the updaterConfig.json file on client devices to precisely match the version you want them to run. The update URL should point to the installer for that specific pinned version.
- Example for Pinning to Version 1.0.2:
```
{
  "win32-x64-prod": {
    "readme": "http://your-internal-server/airgapai/releases/readme_1.0.2.txt",
    "update": "http://your-internal-server/airgapai/releases/prod/1.0.2/AirgapAI Chat Setup 1.0.2.exe",
    "install": "http://your-internal-server/airgapai/releases/prod/1.0.2/AirgapAI Chat Setup 1.0.2.exe",
    "version": "1.0.2"
  }
}
```
- By pinning the version, the application will not attempt to update unless the version number in its updaterConfig.json is explicitly changed to a higher number pointing to a newer installer package.

5.2. Staged Rollouts (Deployment Rings)

Staged rollouts, also known as deployment rings, enable IT administrators to deploy updates to a small group of users first (e.g., IT department, pilot users) before a wider rollout. This minimizes risk by identifying and addressing potential issues with a limited impact.

Implementing Staged Rollouts:

Define Rings: Divide your user base into different "rings" (e.g., Alpha, Beta, Production).
Separate updaterConfig.json Profiles: For each ring, maintain a slightly different updaterConfig.json file, or manage distinct Group Policy Objects that deploy different versions of the configuration.
- Alpha Ring: updaterConfig.json points to the newest available update (e.g., version 1.0.3).
- Beta Ring: updaterConfig.json points to the previously validated update (e.g., version 1.0.2).
- Production Ring: updaterConfig.json points to the stable, widely deployed version (e.g., version 1.0.1).
Sequential Deployment: Once a new version (e.g., 1.0.3) is validated in the Alpha ring, update the Beta ring's updaterConfig.json to point to 1.0.3. After Beta validation, move it to Production.
Use Your Existing Tools: Leverage Microsoft Intune, SCCM, or other Mobile Device Management (MDM) solutions to push the appropriate updaterConfig.json file to devices within each ring.

5.3. Rollback Procedures

Despite thorough testing, issues can arise post-deployment. A robust rollback plan is essential.

Recommended Rollback Steps:

Retain Previous Installers: Always keep previous stable versions of AirgapAI installer packages on your local file server.
Modify updaterConfig.json: If a critical issue is discovered, IT can quickly update the updaterConfig.json file on affected devices (or for the problematic ring) to point back to the URL of the previous, stable AirgapAI installer package. Ensure the "version" number in the configuration file matches the previous version to trigger the downgrade/reinstall.
Push Rollback: Use your enterprise software distribution tools to push this modified updaterConfig.json to the target devices, effectively initiating a rollback.
User Communication: Inform users about the rollback and any temporary service interruptions.

5.4. Audit Checklist for Compliant Updates

For organizations in regulated industries, maintaining an audit trail for software updates is critical.

Version Control: Implement version control for updaterConfig.json and all hosted AirgapAI installer packages.
Deployment Logs: Maintain detailed logs of when, which versions, and to which devices updates (and rollbacks) were deployed.
Testing Documentation: Document the testing process for each new AirgapAI version before deployment, including test cases, results, and sign-offs.
Access Control: Ensure strict access control to your internal file server hosting the update packages and to the systems used to modify updaterConfig.json.
Checksum Verification: Before deploying, verify the cryptographic hash (checksum) of downloaded AirgapAI installers against official Iternal Technologies releases to ensure file integrity.
Security Scans: Regularly scan your internal update server and deployed packages for vulnerabilities.

6. Benefits for IT Administrators and Organizations

Implementing a controlled, local update strategy for AirgapAI offers significant advantages:

Unwavering Security and Compliance: By isolating updates to your internal network, you drastically reduce exposure to external threats and meet stringent data governance and regulatory compliance requirements. AirgapAI's core secure, local AI benefits are extended to its management.
Predictable and Stable Operations: Staged rollouts and version pinning ensure that new software versions are thoroughly vetted before wide release, minimizing unexpected downtime or user disruption.
Optimized Network Resource Utilization: Hosting updates internally reduces reliance on external bandwidth, which is especially beneficial for large organizations or those with numerous remote sites.
Empowered IT Teams: Gain granular control over the software lifecycle, enabling proactive management and rapid response to any emergent issues, reinforcing IT's role as the custodian of stability.
Continuous Artificial Intelligence Value: By securely and predictably updating the AirgapAI application, Large Language Models, and Blockify datasets, your organization continuously leverages the latest AI capabilities and accuracy improvements without compromising its security posture.

7. Conclusion

AirgapAI represents a significant leap forward in secure, cost-effective, and highly accurate Artificial Intelligence for the enterprise. Its flexible update management, particularly the ability to utilize a local file server for offline updates, is a cornerstone of its enterprise-readiness. By mastering the configuration of the updaterConfig.json file, implementing staged rollouts, and adhering to audit best practices, IT administrators can confidently deploy and maintain AirgapAI across their organization. This ensures that every employee can access the transformative power of local, private AI, accelerating productivity and innovation while maintaining the highest standards of data security and operational stability.

Download the free trial of AirgapAI today at: https://iternal.ai/airgapai