Your infrastructure stays private. The FC Agent only dials out.
The FC Agent is a small service you run in your own environment. It connects outbound to FixControl over HTTPS and executes only signed, expiring, single-use operations — so FixControl can govern deployments and validation on Kubernetes, Argo, Jenkins and GitLab without any of those systems being exposed publicly. Offered as part of pilot onboarding.
One outbound connection, nothing inbound
The complete firewall requirement is one egress rule. There are no inbound rules, no VPN and no tunnel — the agent verifies each operation locally, then executes it inside your network.
From a paused pipeline to an executed decision
- 01PauseYour pipeline pauses itself
A deployment reaches a step your team already configured to wait: a GitLab deployment approval or manual job, a Jenkins input step, a GitHub Actions environment review, or a paused Argo rollout. FixControl never starts a deployment.
- 02GateFixControl opens an approval
The pause reaches FixControl as a signed webhook event and opens a deployment gate. Someone on your team reviews the change and the evidence behind it, then approves or rejects.
- 03Signed orderThe verdict becomes a signed operation
FixControl registers a single-use operation: signed with a FixControl key your agent has pinned, addressed to one cluster and one capability, and expiring within minutes. FixControl never opens a connection to deliver it.
- 04Outbound pollThe agent collects it — outbound
The FC Agent polls FixControl over HTTPS, verifies the signature, the expiry and its own local allowlist, and only then executes the operation against your Kubernetes, Argo, Jenkins or GitLab — with credentials that never left your environment.
- 05EvidenceThe result comes back for the record
The agent reports the outcome to FixControl. The approval, the operation and the result line up in one audit trail — including operations the agent refused.
Six properties, all enforced on your side of the wall
Outbound-only connection
The agent initiates every connection to FixControl over HTTPS. The complete firewall requirement is one egress rule; there are no inbound rules, no VPN, and no tunnel that gives FixControl a way in.
Private systems stay private
Kubernetes, Argo, Jenkins and GitLab keep their existing network posture. None of them needs to be made publicly reachable for FixControl to govern deployments on them.
Signed, expiring, single-use operations
Every action arrives as an operation signed by FixControl with a key your agent pins, expires within minutes, and can be redeemed exactly once. A replayed or altered operation is refused — and the refusal is recorded.
You keep local control
The agent executes only operations that pass its own allowlists — which namespaces, which rollouts, which capabilities. Those lists live in your environment; FixControl cannot send them and cannot override them. Empty means nothing is allowed.
Least-privilege RBAC
The agent’s Kubernetes role is minimal: read access to the rollouts you allow, plus its own bookkeeping — no cluster-admin. The component that runs validation is a separate identity that cannot touch rollouts at all.
Credentials stay with you
The Kubernetes service account and the GitLab or Jenkins credential live in your cluster’s own secrets, rotated by you. For connections through the agent, FixControl sends an operation and receives a result — it does not hold credentials for your infrastructure.
A closed set of operations, each with its own health
The agent advertises what it may do, FixControl narrows every operation to one cluster and one capability, and connectivity is tracked as first-class health — a silent agent shows up as degraded, not as green.
The agent polls FixControl on a short interval over HTTPS and picks up only operations addressed to its cluster and its granted capabilities.
Where configured during your pilot: GitLab deployment approvals and manual jobs, and Jenkins input steps. The verdict executes through your CI host’s own primitive. (GitHub Actions environment reviews don’t need the agent — api.github.com is reachable directly.)
Where configured. After an approved gate, the agent promotes through the path you chose — including a GitOps commit that your own in-cluster tooling verifies before promoting.
Where configured during your pilot, a proposed change is validated by a runner inside your Kubernetes environment, with the same evidence contract as FixControl’s isolated Docker validation.
Doesn’t exist. The agent has no listener, no service, no ingress. FixControl cannot connect to the agent — only the other way around.
Not possible. The operation vocabulary is closed — approve, reject, promote, run validation. There is no “run this command” operation, and the agent refuses anything outside the vocabulary.
If FixControl is unreachable, nothing in your cluster changes
The questions your security team will ask
Does FixControl need inbound access to our cluster or CI?+
Do we need to expose Kubernetes, Argo, Jenkins or GitLab publicly?+
Does the agent need cluster-admin?+
Where are our credentials stored?+
What happens if FixControl is unavailable?+
Can FixControl deploy to production on its own?+
Isolated Docker validation, and validation in your own cluster.
Tenant isolation, governance, evidence and audit.
Deployment gates with human-approved promotion.
The full install doc: egress rules, RBAC, local allowlists, enrolment and troubleshooting.
See a private deployment governed end to end
Book a demo and watch a pause in a private pipeline reach an approval — and the approval reach your cluster — without a single inbound connection.