Gardience · Pricing · Updated 2026-11-07 · Gardience Engineering · How we test

Gardience deployment options: self-hosted, air-gapped, or hosted

Gardience runs three ways: self-hosted on your own Linux server, fully offline on an air-gapped network from a signed bundle, or hosted by us on a dedicated server that is never shared. Paid licenses are verified offline and send no telemetry. CUI, government, and regulated fleets run self-hosted or air-gapped, inside their own boundary.

5 minto install on one Linux server
0internet connections needed for the offline bundle
Ed25519signed license, verified offline
$9,000a year, Hosted Starter, 250 machines

Every Gardience deployment runs the same product. What changes is where the server lives and who operates it. The machines you manage stay where they are and connect out to the Gardience server.

Which deployment fits your fleet?

	Self-hosted	Air-gapped (offline)	Hosted by Gardience
Where the server runs	Your Linux server, in your network or cloud	Your Linux server, on a network with no internet	A dedicated AWS server (US East), never shared
Internet needed	For updates and vulnerability data	None	Yes
Install	One command, about 5 minutes	Signed offline bundle, carried in	Set up by us
Updates	One command, signed and checked first	Signed bundle, carried in	Installed for you
Who has admin access	Your team	Your team	Gardience operates the server and its backups
License	Signed file, verified offline; no telemetry	Same	Same
Fits CUI and CMMC enclaves	Yes	Yes	Government, air-gapped, and regulated fleets stay on your own servers
Price	Starter $6,000, Team $15,000 a year	Same plans; Enterprise includes air-gapped setup with you	Hosted Starter $9,000, Hosted Team $21,000 a year

What does an air-gapped network need from a patch tool?

Requirement	How Gardience meets it
Install with no internet	Signed offline bundle with every container image and a software bill of materials
Verify what was carried in	Release signatures checked before install and upgrade
License with no license server	Ed25519-signed license file, verified offline and tied to one server
Linux packages	Built-in update cache, or your local mirror (aptly, reposync, Pulp)
Salt packages	An internal copy of Salt's signed packages, from packages.broadcom.com or mirror.gardience.com (same layout)
Windows updates	Scanned against Microsoft's offline update catalog (wsusscn2.cab)
Evidence out of the enclave	Signed evidence pack, checked offline with the public key inside
Two-person approval	Built in, recorded in the tamper-evident audit log

Can I keep my existing Salt master?

Yes. Attach mode connects Gardience to the Salt master you already run, with an undo that puts the master's configuration back exactly as it was. See keep your Salt master, add a console.

Questions

Does Gardience phone home?

Paid licenses do not. They are verified offline, and check in only if an admin turns on the daily release check, which is off by default. Trials and the free license check in once a day with the license file, version, and machine count. No fleet data ever leaves your servers. See privacy.

What does the Gardience server need?

Any supported Linux server with Docker, amd64 or arm64. It is tested on fresh Ubuntu 24.04, Debian 12, and Oracle Linux 9 servers.

Can a hosted customer move to self-hosted later?

Yes. Your states, settings, and evidence move with a backup and restore, and your machines point at the new server.

Try Gardience on your own machines

One supported console for Windows and Linux on open-source Salt: patching, a scored STIG/CIS-aligned baseline, drift repair, event-driven automation, two-person approval and a tamper-evident audit log. Flat yearly pricing, not per node.

Free 90-day trial (25 nodes)See it work Compare

Salt is a trademark of its owner, Ansible is a trademark of Red Hat, Inc., and other names are trademarks of their owners. Gardience is independent and not affiliated with any of them.