Internal Governance AI Transformation

Install iGAT from one command.

Licensed LGU deployments install through the iGAT CLI.

This site is the public releases portal for iGAT. The actual install entrypoint is get.igat.com.ph, which installs the igat CLI. The CLI then activates the server and pulls the authorized proprietary release.

LGU operators do not need to manually fetch manifests, raw binaries, or separate release URLs. The standard installation path is just the installer command, then the setup wizard.

$ curl -fsSL https://get.igat.com.ph | bash

Then run sudo igat setup · Linux server deployment · support@igat.com.ph

Install Flow

The public install story is intentionally short. Use get.igat.com.ph to install the CLI, then let igat setup handle activation, server configuration, secrets, and the initial deployment.

Install the iGAT CLI

Run the bootstrap command on the target LGU server. This downloads the latest allowed CLI build for the machine architecture and installs igat locally.

bash

curl -fsSL https://get.igat.com.ph | bash

Run the setup wizard

The setup flow asks for the license, validates the machine, writes the deployment environment, and installs the authorized iGAT package for that LGU.

bash

sudo igat setup

Operate and update through the CLI

After first setup, operators work through the same CLI for health checks, upgrades, logs, backups, and restore operations. No direct release URL handling is required.

bash

# health and current deployment
sudo igat status

# upgrade to the latest entitled release
sudo igat upgrade

Public Model

iGAT is proprietary. That means the product artifacts are protected even though the public entrypoints are visible on the web.

01 / Install

get.igat.com.ph

Public bootstrap endpoint. It serves the tiny installer script used in curl -fsSL https://get.igat.com.ph | bash.

02 / Backend

releases.igat.com.ph

Public portal plus protected release backend. The CLI talks to this service for release metadata and downloads after license and machine checks pass.

03 / Protection

Entitlement Gate

Authorized binaries and manifests are served only to valid deployments. Operators should never need to manually browse protected release paths.

Short version: install from get.igat.com.ph. The CLI handles releases.igat.com.ph behind the scenes.

Operator Commands

These are the standard commands an LGU operator should actually use on the server after the CLI is installed.

First-time server

Initial install

Use the bootstrap installer once, then run the guided setup flow.

bash

curl -fsSL https://get.igat.com.ph | bash
sudo igat setup

Existing deployment

Routine operations

Use the CLI for inspection and updates. No separate install script is needed after first setup.

bash

sudo igat status
sudo igat logs
sudo igat upgrade

Advanced internal release endpoints exist for the CLI and release automation, but they are not part of the normal LGU operator workflow.

Linux target CLI-managed upgrades License-gated releases Backup and restore support