Skip to Content
Overview

TruStacks Docs

TruStacks is a crew of AI agents that proposes software-delivery changes (CI workflows, Helm or Kustomize config, ArgoCD Applications) as pull requests in your platform repo. Every proposal is checked against a signed policy before the pull request opens, and a human on your team merges it.

Agents propose. Policy decides. Humans approve.

This site is the technical reference. For positioning and pricing, head to trustacks.com .

Where to start

  • Quickstart · create a workspace, install the runner, connect two repos, and merge your first governed pull request.
  • How TruStacks runs · the hosted control plane, your runner, and what crosses between them.
  • Installation · runner install reference, credentials, and GitOps wiring.
  • Product guide · every screen in the app.
  • Reference · architecture, the constitution, supply-chain verification, and the runner CLI.
  • Workshops · guided walkthroughs of the crew on real-shaped problems.

The unit you adopt: an Application

You use TruStacks one Application at a time. An Application is:

  • one or more service repos: application code the crew reads; and
  • one platform repo: your GitOps repo, where the crew opens pull requests with the CI workflow, deployment config, and ArgoCD Applications for those services.

Each service repo belongs to exactly one Application. TruStacks never writes generated files into your service repos. The one file you add there yourself is a small CI caller workflow, once per service.

How the rules fit together

┌──────────────────────────────────────────────────────────────────┐
│  Your overlay rules (optional)                                   │
│  Can only add denials; can never loosen the constitution.        │
│  Enforced by the runner from 0.2.14.                             │
├──────────────────────────────────────────────────────────────────┤
│  Specialists                                                     │
│  Baseline Security (included) · SOC2 Specialist Pack             │
├──────────────────────────────────────────────────────────────────┤
│  Constitution (signed, public, every tier)                       │
│  The rules every proposal must pass before a PR opens.           │
└──────────────────────────────────────────────────────────────────┘

The constitution is published from the public trustacks-policy repo and signed, so you can read every rule and verify the bundle your runner evaluates. The specialists review your setup during gap analyses. Your own overlay rules can be drafted in the app, and from runner 0.2.17 a hosted runner enforces them from rules/ in your platform repo, once a reviewed pull request merges them.

Your GitOps controller deploys merged pull requests the way it always has.

Status

TruStacks is in Beta. These docs describe what works on the hosted service today and call out Beta limits where they apply. If something is missing or wrong, open an issue.

Last updated on
TruStacks 101