← Trust / Air-gap install

Air-gap install kit.

Self-contained tarball. Ships every byte install.sh would normally download, pre-verified against its sha256 pin. Move it onto the isolated host, verify, install. No outbound network needed at install or runtime.

Download
https://github.com/patl4588/railcall-core/releases/download/station-v0.27/railcall_airgap_v0.27.tar.gz
sha256 f2136fee1f1357f3850aea1a4ac4659673a2c3b8b0ca4b900bd541c6659b1696
# verify on the download machine before you carry it over
curl -fsSL -o railcall_airgap.tar.gz railcall_airgap_v0.27.tar.gz
shasum -a 256 railcall_airgap.tar.gz
# expect: f2136fee1f1357f3850aea1a4ac46596…

Install on the isolated host

tar -xzf railcall_airgap_v0.27.tar.gz cd railcall_airgap_v0.25 ./verify.sh # refuses if any file drifted ./install.sh # writes to ~/.railcall/ ; no outbound

install.sh prefers the local bundle files over any network fetch. Same sha pin gates apply on the local copies — the bundle cannot smuggle in a different CLI or station than the one this installer was minted for.

Four-check verification chain

  1. 1. Manifest check. verify.sh hashes every bundled file against MANIFEST.txt. Refuses on any drift.
  2. 2. Per-file installer pin. install.sh's pin_for() function has its own sha256 pin per CLI file, hardcoded at build time. Refuses if the local copy doesn't match — same rule as network downloads.
  3. 3. Station tarball pin. The station bundle is pinned by STATION_SHA in install.sh.
  4. 4. Module Ed25519 verify. Each module bundle a customer installs later carries a publisher Ed25519 signature, verified by the module loader at load time. Independent of the install chain.

Four independent checks. All fully offline. Nothing trusts the network.

What the bundle does NOT do

  • Modules aren't pre-installed. Vertical modules (HubSpot, Salesforce, etc.) publish on the marketplace and install on demand. For an air-gap environment, obtain specific module bundles separately and drop them into ~/.railcall/station/modules/<slug>/. Publisher trust allowlist + Ed25519 signature verification apply identically — no runtime does.
  • No online license activation. For paid-module DRM, the license file must reach the target machine some other way (email attachment, USB) and get installed with railcall license activate <path>. Verification is fully offline; the delivery is the customer's problem.
  • No calling home at runtime. Once installed, the station operates entirely on 127.0.0.1. LLM inference through Studio + any external API from a workflow use YOUR credentials + your outbound network only. We're not in the middle.
Doing an evaluation?

The design-partner program includes hands-on help with the air-gap install + a governance review of one real workflow. Rolling admission, capped at three per quarter.

Apply as design partner