Cloud-specific agents need a different image per target.
Cloud-Agnostic Agent
The same container runs on AWS, Azure, GCP, or a laptop — two volume mounts and one URL is the entire contract.
Trust
The agent container has no cloud-specific code. AWS Secrets Manager, Azure Key Vault, GCP Secret Manager, or a local file — all three secret backends are built in. Mount your identity volume, mount your config, point it at the platform, and it runs.
What it solves
Common problems this capability removes from your engineering workflow.
Customer marketplaces demand SBOM, signed images, multi-arch builds.
Bootstrap secrets sit in code or YAML across cloud accounts.
Switching from AWS to Azure means re-architecting the agent.
How it works
The flow this capability runs end-to-end inside the platform.
- 1Same container image for every cloud and the laptop.
- 2Three secret backends supported via URI — AWS, file, or env var.
- 3Two volume mounts — identity and config — are the entire contract.
- 4Multi-arch builds, signed images, and CVE scans ship by default.
Related capabilities
Other capabilities in the BoltPipeline platform that work alongside this one.
6Agent &
Agent Runtime
A stateless executor near your warehouse runs orchestration, profiling, and cataloging with six reliability primitives.
6Agent &Agent Protocol
The agent in your network speaks three mTLS channels to the platform — and never holds policy or makes decisions.
2Validation &Observability
One metrics stack tells you whether the platform is up, the fleet is healthy, and why a slow page is slow.
See it on your data.
Try BoltPipeline against your live database — your data never leaves your environment.