Ways to run TruStacks
TruStacks is a hosted service. We run the control plane; you run one lightweight component, the runner, inside your own Kubernetes cluster. The runner is outbound-only, so your source code never leaves your cluster. Only findings, audit events, and pull requests flow back to us. The one thing you hand us is your model provider key: the control plane holds it in memory just long enough to seal it to your runner, which writes its own in-cluster Secret. We never store the raw key.
There are two ways to get started, and they differ only in how you onboard. Both are the same hosted track, the same agent crew, the same constitution, and the same pull-request workflow.
Agents propose. Policy decides. Humans approve.
The two doors at a glance
| Self-serve trial | Concierge (Beta cohort) | |
|---|---|---|
| Onboarding | Sign in and you’re in, no invite | We provision your workspace and send you a sign-in link |
| Best for | Trying it yourself, right now | Design partners and guided Beta onboarding |
| Billing | 30-day trial, no card | Off during Beta, unmetered |
| Specialists | Baseline Security · SOC2 self-serve | Baseline Security and SOC2 included |
| You install | Only the runner, in your cluster | Only the runner, in your cluster |
| Start here | Hosted quickstart | Getting started (Beta) |
Self-serve trial
Sign up yourself and you land in your own isolated workspace with a 30-day trial, no credit card. Enroll one runner in your cluster, connect a service repo and a platform repo, and watch the crew open a real, policy-checked pull request. This is the fastest way in.
Follow the hosted quickstart.
Concierge (Beta cohort)
The white-glove path for design partners and the Beta cohort. We provision your workspace and hand you a sign-in link, billing is off for the whole Beta, and the Baseline Security and SOC2 specialists are included at no cost. Everything else, from the runner install to the first PR, is identical to the self-serve path.
Follow Getting started (Beta).
Not sure which one
Start with the hosted quickstart. It is the fastest way to see the crew open a real, policy-checked pull request, and nothing you learn there is wasted if we later move you onto the concierge path. The runner install, the constitution, the Environment Profile, and the review workflow are identical.
Running the whole platform yourself? That is a self-hosted, contributor path, not the customer track. It runs the full control plane locally and is kept out of the main docs. If you are an internal developer or a design partner who needs offline or air-gapped evaluation, see the self-hosted quickstart or local development under Contributing.