Skip to main content

Agent Foundry

Battle-tested agent baselines. Ship in weeks, not months.

Zero to running an agent in four commands
  • A2A native
  • AWS native
  • MCP enabled
  • OIDC + Keycloak
  • Temporal™ orchestration
  • Hardened by Chainguard
  • OpenSpec driven
  • Apache-2.0
Secure by default

Built on Chainguard™

Every baseline ships referencing Chainguard container images — minimal, distroless, and continuously rebuilt against the latest CVE data. Supply-chain posture isn’t a Day 2 problem.

Open to everyone

Chainguard latest-dev

Public baselines pull Chainguard’s freely availablelatest-dev images. Clone, build, and run with a hardened base — no registry credentials required.

  • Distroless runtime, minimal attack surface
  • Rebuilt continuously against upstream CVE feeds
  • SBOM and signatures generated for every image
Booz Allen engagements

Full Chainguard catalog

Booz Allen’s enterprise agreement with Chainguard unlocks the full hardened image library on customer delivery. Same baselines, production-grade provenance, zero rework.

  • Pinned, FIPS-ready images for regulated workloads
  • Vendor-backed SLAs and patch cadence
  • Drop-in upgrade — no baseline code changes required

Framework-Agnostic Architecture

Build with AWS Strands, LangChain, or your own framework. Connect them over the A2A protocol. Run it durably on Temporal — retries, timers, signals, and human-in-the-loop come standard.

Foundry architectureThree agents — AWS Strands, LangChain, and Custom — each expose an A2A API. All three sit on a shared A2A protocol bus, which feeds into a Temporal-orchestrated workflow engine below.[ AGENTS ][ A2A PROTOCOL ][ DURABLE ORCHESTRATION · TEMPORAL ]Agent AAWS StrandsA2A APIAgent BLangChainA2A APIAgent CCustomA2A APIAgentic Workflow EngineTemporal Orchestration
Why Temporal

Durable execution

Workflows survive process restarts, network failures, and multi-day waits. State is checkpointed, not lost.

Retries & timers built in

Activity retries, backoffs, and timers are first-class — no custom queue or scheduler glue to maintain.

Human-in-the-loop signals

Pause for review, gather input, then resume — signals make long-running, supervised agent workflows tractable.

Learn Core Concepts