Coordinate the work. Not your code.
Foreman is designed around a clear trust boundary. The control plane coordinates delivery and holds the evidence trail, while your source code and provider credentials can stay inside your own environment.
Two sides. One authorized channel.
Foreman control plane
Coordinates — never holds your code
- Policy
- Work state
- Authority
- Evidence
- Routing
- Readiness
authority ·
evidenceAuthorized
channel
Your environment
Private Runner — your code stays here
- Private Runner
- Repository
- Provider credentials
- Approved AI agents
- Verification tools + their credentials
- Build / tests / validation
What each side is responsible for.
Source-code boundary
Code can be kept inside your environment via the Private Runner rather than moving to Foreman.
Credential boundary
With Private Runner, credentials for AI providers, GitHub, and verification tools such as BrowserStack or Snyk remain in your environment. Foreman receives the operational results and evidence it needs—not those provider credentials.
Network model
The control plane exchanges work state and authority over authorized communication.
Execution boundary
Agents execute where you place the runner — next to your code.
Tenant / workspace isolation
Work is separated by workspace so teams and clients stay isolated.
Policy enforcement
Assignment and release respect the policies you define.
Evidence
Validation, review, and remediation are recorded against each candidate.
Release authority
Nothing ships without a human decision.
Audit history
A durable record of assignment, validation, review, and release.
This describes Foreman's architectural trust model. Specific controls, certifications, and deployment options are reviewed with your security team as part of an enterprise engagement.
Bring your security team to the table.
We'll walk through Foreman's trust boundary, the Private Runner, and the audit trail in detail — on your terms.