Skip to main content
TruStacks

Solutions · GitOps delivery

Deployment you can read in a pull request.

TruStacks proposes the deployment for each service as a pull request against your platform repository: a Helm chart and ArgoCD Application on Kubernetes, or a task definition and deploy workflow on ECS with Fargate. Nothing deploys until a person on your team merges it, and then your own tooling applies what was merged. The agents hold no production credentials and never touch the cluster: git is the only door, and your people hold it.

The path to production

Four steps, and only one of them is an agent.

  1. Step 1

    The crew proposes

    The deployment artifacts for your target, written into your platform repository as a pull request. The agents never touch a cluster or a cloud account.

  2. Step 2

    Policy decides

    The proposal is checked against the constitution before the pull request opens. A denial is recorded with its rule, and nothing opens.

  3. Step 3

    A person merges

    Your reviewer reads the blast radius and the rollback in the pull request body, and merges or doesn't. There is no autonomous merge path.

  4. Step 4

    Your tooling deploys

    Your ArgoCD syncs what was merged, or your own CI deploy job applies it to ECS, with your credentials, on your infrastructure. Production waits for a person, by rule.

Checked before you see it

Production does not deploy itself.

The constitution checks delivery artifacts the same way it checks pipelines. A proposal that would let production deploy without a person is denied before anyone is asked to review it.

Kubernetes with ArgoCD

  • proposal.has_helm_chart

    The proposal includes at least one Chart.yaml under the gitops/ service root.

  • proposal.has_argocd_application

    The proposal includes an ArgoCD Application manifest for the service and its target cluster.

  • practice.argocd_prod_requires_manual_sync

    ArgoCD Applications deploying to a prod-tier cluster must opt out of automated sync.

ECS on Fargate (Beta)

The crew writes the task definition and a GitHub Actions workflow that applies it to an ECS service you already run. It does not create services, networking, or IAM; the pull request lists those as prerequisites.

  • practice.ecs_task_runs_as_nonroot

    Every container in an ECS task definition sets a non-root user.

  • practice.ecs_task_image_is_pinned

    Every ECS container image names a digest or a non-floating tag, never latest.

  • practice.ecs_task_secrets_not_in_environment

    No credential-like value in a container's environment; secrets come from Secrets Manager or SSM by ARN.

  • practice.workflow_prod_deploy_requires_environment

    On a prod-tier target, every job that deploys declares a GitHub environment. The rule checks that one is named, not which reviewers it requires; on Fargate the pull request merge is the gate that always holds.

Today

ArgoCD and Fargate. One governed path.

The crew writes Helm charts or Kustomize overlays with ArgoCD Applications for Kubernetes, and task definitions and deploy workflows for ECS on Fargate, which is in Beta. You can declare Flux in your environment profile, and the crew takes it into account, but it does not write Flux configuration. The governed pull request does not care what applies the change, so every target gets the same propose, decide, approve path.

Keep your tooling. Lose the hand-written manifests.

The hosted Beta is open to the first 50 teams. Sign up with the Beta link and it's free for 45 days, with no card needed. The hosted quickstart walks you to your first governed pull request.