01 · Agree the scope
A paid pilot
An InfraGuard engineer agrees with you which systems, agents and models the pilot covers, and you receive the offline bundle.
Request a pilotInfraGuard · Private AI access control
InfraGuard is software you install on your own servers, between your AI agents, your people and your infrastructure. Each call is allowed, sent for approval or denied by your policy, and written to a record you can verify. Your models, your data and your access rules stay on your machines.
Works with the systems you run
What you get
InfraGuard is not a cloud service and not a chatbot. It is a gate you run next to your systems: every person, agent and application that wants to reach them goes through it, and it decides each call.

Who calls
People
Sign in with your SSO: OIDC, Active Directory, SCIM
AI agents
Tools over MCP or REST, or a hook in the runtime you use
Apps that call models
Any OpenAI-compatible client, pointed at the gateway
InfraGuard
What you install: one image, on your servers
ConsoleInventory, access, approvals and audit
Policy decisionAllow, require approval or deny, with a decision id
Tool gatewayTyped tools for agents, over REST and MCP
Model gatewayGrants with calls per minute and tokens per day
AuditA hash-chained record you verify offline
Your systems
Linux servers and VMs
On VMware, Proxmox or bare metal, over SSH
Kubernetes
Pods, logs, events and restarts
PostgreSQL
Logins that expire by themselves
Logs and events
Searched inside the caller’s role
Your models
Open-weight, on your GPUs
01 · Agree the scope
An InfraGuard engineer agrees with you which systems, agents and models the pilot covers, and you receive the offline bundle.
Request a pilot02 · Install
Verify the bundle and start it with Docker Compose or Helm. Without a licence file it runs as Community: 25 protected resources and 3 AI agents, with people not counted.
How to install03 · Run it
Growth, Business or Enterprise. Your limits are written in a licence file that your installation checks offline. A larger estate means a new file, with no restart.
Talk to usPrices are agreed with you and are not published on this site.
Private AI with access control
Search with access control
People and agents ask the same question. InfraGuard answers from what their tenant and role may read, and nothing older than the retention you set.

Results for your role
Scope of this answer
Events of other tenants are never returned, and nothing older than the retention is served.
Events per hour
06:0012:00
See it decide
An incident, a private model and a database login: three short replays of what InfraGuard decides, line by line, and why.
An operations agent investigates a slow payments service for the engineer on call.
A replay with example names, identifiers and limits. The tools, the decisions and the rules are InfraGuard’s.
What it does

Access control
Every tool call says who asked, for whom and what. A delegated agent gets the stricter of its own policy and the person’s. A write or privileged action runs only when a policy names it, and an approval runs it once.
Enterprise grade
Private models
Serve open-weight models from Hugging Face on your own machines. Each workload needs a grant, with calls per minute, tokens per day and an output limit. Prompts are not stored, and no service holds the model’s key.
Private models
Search and observe
Agents search the inventory, read logs, metrics and Kubernetes events, and query databases read-only. Logs and metrics arrive over OpenTelemetry, and an OpenSearch mirror keeps one role per tenant.
On-premisesPrivate LLMs
Choose an open-weight model on the Hugging Face Hub, download it once, and serve it on your own GPUs with vLLM or llama.cpp. With the reference egress rules, InfraGuard is the only way in: each workload, agent and chat gets a grant with its own limits, prompts are not stored, and every call is recorded.
Workloads, agents and the chat
Each with its own token, grant and limits
InfraGuard model gateway
Grant, budget, redaction and a record of every call
Your model server
vLLM or llama.cpp on your GPUs; InfraGuard holds its key
Hugging Face Hub
Open weights, downloaded once into your network
POST /v1/llm/chat/completions
Authorization: Bearer <workload token>
{ "model": "vllm/qwen3-8b",
"messages": [{ "role": "user", "content": "…" }] }Recorded from the product
Four recordings from the public tutorials: install, enrol a server, govern a model, check the audit.
Your estate
Each tile says how InfraGuard reaches the system today. Nothing on this list is a promise of a future connector.
Linux servers
Red Hat Enterprise Linux, Ubuntu, Debian, SUSE
SSH command profiles: typed parameters, never a free shell line
VMware vSphere
ESXi hosts and their guests
Linux guests through SSH command profiles
Microsoft Hyper-V
Windows Server virtualisation
Linux guests through SSH command profiles
Proxmox VE and KVM
Open-source hypervisors
Linux guests through SSH command profiles
People on servers
Engineers and administrators
Short-lived SSH certificates issued by InfraGuard
Kubernetes
OpenShift, Rancher and other distributions expose the same API
Pods, logs, events, restarts and discovery; tested on k3s
PostgreSQL
Operational databases
Read-only queries, writes under policy, temporary logins that expire
PostgreSQL in your cloud
Azure Database for PostgreSQL, Amazon RDS, Google Cloud SQL
The same PostgreSQL connector; not yet verified on these managed services
Microsoft Active Directory
Over LDAPS
People, groups and nested membership, synchronised on a schedule
Keycloak and OIDC
Single sign-on
Signed access tokens; tested end to end with Keycloak 26.4
SCIM 2.0 and SAML
Provisioning and federation
SCIM provisioning; SAML through an identity broker
OpenTelemetry
OTLP over HTTP
Logs and metrics in, each stored under its sender’s credential
OpenSearch
Version 3.9
A search mirror with one role per tenant
Your SIEM
Security operations
The audit chain by cursor, and signed webhook alerts
Hugging Face
Open-weight models from the Hub
Download once, serve on your GPUs, govern every call
vLLM
Model serving
The serving engine of the Private AI bundle
llama.cpp and Ollama
Local model servers
Any OpenAI-compatible or Ollama endpoint behind the gateway
LibreChat
Chat for employees
Private AI bundle: chat, model and sign-in on your machines
MCP and REST agents
Agent frameworks and assistants
One tool gateway over MCP streamable HTTP and REST
Docker Compose
A single host
The reference installation
Helm
Your Kubernetes platform
A chart with reference egress rules
Air-gapped networks
No internet at all
An offline bundle, verified locally, with an offline licence

Not a chatbot over your servers
Give AI the reach your teams need, and keep the decision with your policy, your approvers and your audit.
Request a pilotWhy InfraGuard
InfraGuard decides before a call reaches the system. It is a gate, not an alert after the fact.
Tools take typed arguments and command profiles. What a model writes is never run as a shell line.
Agents act through InfraGuard. People get SSH certificates and database logins that expire on their own.
Services call the model through the gateway and never see its key, so a leaked token cannot reach the model elsewhere.
Every decision joins a tamper-evident hash chain. You verify it, and your SIEM reads it by cursor.
In your data centre, your private cloud or an air-gapped network, from an offline bundle you verify yourself.
Get started
InfraGuard is delivered as an offline bundle through a pilot. Verifying and loading it needs no network and no registry, and the running service makes no call to SoftQuantus.
cd infraguard-offline-<commit>
./verify-release.sh --key infraguard-release.pub --commit <commit>
# VERIFIED: infraguard-api-<commit>.tar.gz ...
docker load -i infraguard-api-<commit>.tar.gz
# Loaded image: infraguard-api:<commit>Requirements, configuration and the first steps are public. Read them before you talk to us, so the pilot starts on your questions.
Install guideTell us what your agents and people should reach. We agree a scope with you and send an offline bundle and, where the pilot needs one, a licence.
Request a pilotCheck the bundle with its own verification script before anything runs, then start InfraGuard with Docker Compose or the Helm chart, next to your PostgreSQL and identity provider.
Release verificationRegister one cluster, database or server, write the first policy and connect an agent over MCP. The tutorials walk through each step.
TutorialsQuestions
No. InfraGuard is the control layer between AI and your systems. Your agents, assistants and people keep the tools they use; InfraGuard decides what each of them may reach and records every decision. The optional Private AI bundle adds a chat for employees, governed the same way.
Any model service with an OpenAI-compatible chat completions route, or an Ollama endpoint, that you run or choose. For a fully private setup, serve open-weight models from Hugging Face with vLLM or llama.cpp on your own GPUs.
InfraGuard makes no call to SoftQuantus, and its licence is checked offline. Data goes only to the model services, identity provider and search cluster you configure. With models on your own GPUs, nothing has to leave at all.
Kubernetes, PostgreSQL and Linux hosts over SSH, including Linux virtual machines on VMware vSphere, Hyper-V, Proxmox and KVM, plus the inventory, logs and metrics InfraGuard collects. The integrations page of the documentation lists each one with its tests.
Community runs without a licence file, for up to 25 protected resources and 3 governed AI agents. Growth, Business and Enterprise are set by a licence agreed with us. We start with a paid pilot against an agreed scope, and we do not quote prices on this site.
Tell us what your agents and people need to reach, and where InfraGuard would run. It takes about two minutes.
The film and pictures on this page are SoftQuantus’s own, painted from noise and line work; the clips are recordings of the InfraGuard tutorials. Product names belong to their owners and show where InfraGuard fits, not a partnership or an endorsement.