Sovereign agentic platform

Command an entire fleet of engineering agents.

Fleet is the enterprise tier of the BoldBlack agent line — an organized force of agents running inside your own cloud. GitOps-controlled, fully audited, and invisible to the public internet.

0
Public endpoints
N
Agents, one command
1
Template bootstrap
HIPAA · SOC 2
By construction
agent · code-review agent · on-call agent · release
Sector scan 3 on station
01 — Fly a sortie

One task. Full flight plan.

Follow PR #482 through the fleet

A single pull request enters the pattern and every station plays its role — dispatch, review, verify, ship. This is what "orchestrated" means: not one agent, but a formation.

Each leg of the sortie is a durable workflow step. If anything stops — restart, deploy, blackout — the flight resumes exactly where it left off.

T+00:00 LAUNCH human → dispatch

Sortie begins

A maintainer assigns PR #482 to the fleet from chat. The flight plan is instantiated: review, verify, release.

mission feed dispatch
14:02 @capotej fly review of PR #482
14:02 workflow sortie-482 instantiated · 4 legs
T+00:04 REVIEW agent · swe-pal

Agent reviews the code

swe-pal reads the diff against repo conventions and its own memory of the codebase. One finding blocks merge.

mission feed swe-pal
14:06 PR #482 auth-service token refresh
14:06 finding 1 · HIGH rotation window allows reuse
       auth/session.go:214
T+00:11 VERIFY workflow · durable

Human decides, fleet verifies

The maintainer asks for a fix. swe-pal patches, the suite re-runs inside the perimeter — and the flight log records who decided what, forever.

mission feed swe-pal · workflow
14:09 @capotej patch it, re-run the suite
14:11 patch pushed · tests 214/214 ✓
14:11 attribution: decision human · execution agent
T+00:19 RECOVER agent · release

Aboard and merged

Green suite, approved review — release folds the PR into the train. Canary first, promote on health. The sortie closes; the audit trail remains.

mission feed release
14:21 PR #482 merged · train v2.14
14:23 canary 5% · err 0.01% · p99 412ms
14:31 promoted · sortie-482 COMPLETE · 29 min
02 — The strike group

Every capability, in formation.

AG-01
AGENTS

Chat-native engineers

Agents with individual identities, roles, and skills — code review, releases, on-call, reporting — operating in your chat rooms.

GC-02
GITOPS

Self-healing control

Every workload declared in git, reconciled continuously. Drift is corrected automatically; change review is the pull request.

WO-03
ORCHESTRATION

Durable workflows

Long-running, resumable agent operations. A workflow that survives restarts picks up exactly where it left off — for hours or weeks.

NM-04
MESH

Private network

An encrypted mesh with no public ingress. Nothing is reachable from the internet — not the control plane, not the agents.

SC-05
FORGE

Self-hosted git + CI

Your repositories and your build pipelines live inside the perimeter. Source never leaves your account — not even to build.

AT-06
AUDIT

Total attribution

Every agent action is attributed, logged, and replayable. Compliance evidence is a property of the architecture, not a report you write.

Your cloud. Your agents.
Your rules.

Sovereignty is not a setting — it is the architecture

03 — Sovereignty

Agent SaaS vs. Fleet.

DimensionAgent SaaSFleet
RUNS ONTheir cloud, their regionYour cloud account
SOURCE CODELeaves your perimeterNever leaves your perimeter
MODELSThe one they sellYour choice, in-account
NETWORKPublic API endpointsZero public endpoints
COMPLIANCEBolt-on, audit-timeBy construction, always on
COST MODELPer-seat, foreverEnterprise / bring-your-own-cloud
04 — Questions

Asked at every briefing.

Where does Fleet run, exactly? +

Inside your own AWS account. One CloudFormation template bootstraps the platform — self-provisioning Kubernetes, GitOps control, self-hosted git and CI, workflow orchestration, and the private mesh. Nothing runs in a BoldBlack-owned account.

Does our source code ever leave our perimeter? +

No. Repositories, code reviews, and container builds all run on infrastructure inside your account. Agents read and write code over the private mesh; there is no public endpoint to exfiltrate through.

How is compliance handled? +

By construction, not by audit scramble. Every action — human or agent — is attributed and logged with actor, diff, and workflow id. HIPAA and SOC 2 evidence is a property of the architecture and stays current continuously.

Which models can the agents use? +

Your choice. Fleet agents call models provisioned in your own account, with your keys and your egress rules. Nothing about model access is routed through BoldBlack.

What happens if a workflow is interrupted? +

It resumes. Workflows are durable — a release train that survives a restart picks up exactly where it stopped, whether the interruption is a deploy, a node failure, or a blackout hours into a multi-day operation.

How do we get started? +

A briefing. We walk your team through a live cluster architecture and a deployment plan for your account, then bootstrap the platform together. The gated setup skills walk your operators through every step.

05 — Request a briefing

Put your fleet to work.

See a live cluster architecture, a deployment walkthrough, and what a sovereign agent organization looks like for your team.