K8s-native execution live

TICKET
IN.
PR
OUT.

SprintFoundry orchestrates 10 built-in agents across pluggable execution backends (local, Docker, Kubernetes) to turn backlog tickets into tested, reviewed pull requests — with Mission Control v4 dashboard, snapshot recovery, and OTel-ready telemetry.

10
Built-in agents
3
Execution backends
4
Ticket sources
Mission Control
Live runs + execution backends + SSE streaming
3 active
Active Runs
LIN-423: OAuth token refresh
my-app · updated just now
executing
product architect developer qa security k8s
Runtime: claude-code · Backend: k8s · Namespace: sf-prod · PVC: run-423-ws
Active: developer · claude-sonnet-4-5 · sandbox: k8s-pod · 00:04:12
GH-88: Add CSV export
reports-svc · updated 1m ago
planning
orchestrator product developer qa docker
Active: orchestrator · claude-sonnet-4-5 · backend: docker · 00:00:41
JIRA-211: Payment retry flow
checkout-core · updated 2m ago
executing
product architect developer qa local
Active: architect · claude-sonnet-4-5 · backend: local · 00:02:14
Completed Runs
LIN-418: Rate limit middleware
api-gateway · 12m ago · PR #241 opened
completed
product architect developer qa security
GH-79: Session timeout warning
web-portal · 18m ago · PR #188 opened
completed
product architect developer qa security
5 runs · 3 active · 2 k8s · 1 docker · SSE live refreshed just now

Works with your existing stack

Linear GitHub Issues Jira GitLab Any git forge

WHAT'S NEW THIS WEEK

49 commits shipped since March 6. K8s-native execution, Mission Control v4, snapshot recovery, and more.

execution

Pluggable Execution Backends

A clean contract layer lets the orchestration service dispatch agent work to local processes, Docker containers, or Kubernetes pods — chosen per-project via env var, YAML, or CLI flag.

k8s

Kubernetes Pod Execution

PVC-backed workspaces, service account secret projection, namespace isolation, configurable egress network policies, and pod-level sandbox recovery.

dashboard

Mission Control v4 Dashboard

Complete React + Vite + Tailwind rewrite. Run dashboard with filtering, run detail with agent activity and file diffs, agent monitoring view, real-time SSE streaming.

reliability

Whole-Run Snapshot & Recovery

Export and restore entire run state. Resume interrupted runs from the last checkpoint. PVC snapshot plans for K8s workspaces keep agent work durable.

cli

Generic Direct-Run Agent

Skip the full SDLC orchestration pipeline for targeted tasks. Run any agent directly from the CLI with a prompt — the default mode for single-agent runs.

observability

Sandbox Lifecycle Metrics

Track sandbox creation, attachment, teardown, and recovery events through the OTel pipeline. Per-backend provisioning timing surfaced in metrics.

FROM BACKLOG TO BRANCH IN FOUR STEPS

A clean separation between your planning tools and your codebase. No new workflows to learn — SprintFoundry fits into what you already use.

1
Point at a ticket

Give SprintFoundry a Linear ticket, GitHub issue, or Jira task. Or just describe what you want built as a prompt.

2
Orchestrator plans

The orchestrator classifies the work, applies mandatory platform/project rules, and generates a structured execution plan (with model/runtime selection per step).

3
Agents execute

Specialized agents run sequentially or in parallel. Each reads prior artifacts, does its job, and writes outputs for the next agent. The filesystem is the message bus.

4
PR lands in your repo

A tested, reviewed pull request is created with code, tests, docs, and a full audit trail. You review and merge — or configure auto-merge for qualifying changes.

TEN BUILT-IN AGENTS. PLUS CUSTOM.

Each agent has runtime-specific instructions, explicit handoff artifacts, and service-enforced role ordering.

product
Product Agent
  • Requirements doc
  • User stories
  • Acceptance criteria
  • Scope clarification
architect
Architect Agent
  • System design
  • API contracts
  • Data models
  • ADRs
ui/ux
UI/UX Agent
  • Wireframes
  • Component specs
  • Design tokens
  • Interaction notes
developer
Developer Agent
  • Implementation
  • Self-test + self-review
  • Handoff to QA
  • Production code changes
go-developer
Go Developer Agent
  • Idiomatic Go implementation
  • Go API/service changes
  • Go handoff docs
  • Production Go code
qa
QA Agent
  • Unit tests
  • Integration tests
  • E2E tests
  • Test reports
go-qa
Go QA Agent
  • Go test suites
  • Race checks
  • Coverage artifacts
  • Go bug reports
code-review
Code Review Agent
  • Severity-ranked findings
  • Architecture alignment
  • Performance/error checks
  • Review handoff to dev
security
Security Agent
  • Vuln scanning
  • Auth review
  • Dep audit
  • SAST report
devops
DevOps Agent
  • Dockerfiles
  • CI/CD pipelines
  • IaC templates
  • Deploy config

LOCAL. DOCKER.
K8S.

A pluggable execution contract lets you run agents anywhere — from local processes for development to Kubernetes pods for production. Switch backends per-project with a single config line.

  • Three backends, one contract. LocalExecutionBackend, DockerExecutionBackend, and KubernetesPodExecutionBackend all implement the same ExecutionBackend interface.
  • K8s-native isolation. Namespace isolation, egress network profiles, service account secret projection, and configurable isolation levels.
  • PVC-backed workspaces. Agent workspaces persist on Kubernetes PersistentVolumeClaims, enabling recovery, reattach, and snapshot export.
  • Sandbox lifecycle management. prepareRunEnvironment, executeStep, pauseRun, resumeRun, teardownRun — all handled by the backend.
BACKEND: LOCAL
Local Execution

CLI subprocess or in-process SDK. Zero infrastructure. Ideal for development and single-agent direct runs.

local_process local_sdk zero-config
BACKEND: DOCKER
Docker Execution

Each agent runs in an isolated container with mounted workspace volume. Provides process and filesystem isolation without K8s overhead.

container isolation volume mounts
BACKEND: K8S
Kubernetes Pod Execution

Production-grade agent orchestration. PVC-backed workspaces, service account secret projection, namespace isolation, egress network policies, and pod-level sandbox recovery and reattach.

PVC workspaces secret projection namespace isolation egress policies sandbox recovery

SEE COST, TOKENS, TOOLS, AND SKILLS

Monitor UI gives run-level context while OpenTelemetry pipelines expose service and runtime telemetry for production operations.

OpenTelemetry pipeline

docker compose -f docker-compose.otel.yml up -d
SPRINTFOUNDRY_OTEL_ENABLED=1
runs_total step_duration_seconds tokens_used_total cost_usd_total agent_tool_calls_total

Grafana operations dashboard (trimmed capture).

Monitor-first troubleshooting

  • Live stream events: step transitions, tool calls, file edits, command runs.
  • Per-step metadata: runtime provider/mode, tokens, cost, and runtime skill details (names, warnings, hashes).
  • Review and audit paths: resolve human gates and inspect artifacts through monitor APIs.

HARD SHELL.
SOFT CORE.

Service enforces constraints; the orchestrator decides execution.

  • Credentials and limits stay in service. Keys, budgets, and timeouts never live in agent prompts.
  • Planner + validator split. Orchestrator plans steps; rules enforce required safety checks.
  • Artifacts + events are auditable. Workspace outputs and run events/logs feed monitor and review.
  • Human gates + rework are native. Runs can pause for review and re-route failed work.
  • Pluggable execution backends. Switch from local to Docker to K8s per project. Same contract, same agent code, different isolation levels.
hard shell
Orchestration Service (Node.js)
credentials · budgets · timeouts · rule validation · events/logs · review gates
soft core
Orchestrator Agent (runtime configurable)
ticket classification · agent selection · step planning · rework strategy
execution
Agent Runtimes (Claude Code + Codex)
product architect ui-ux developer code-review qa security devops
execution backends
Pluggable Sandbox Backends
local docker kubernetes
output
Pull Request
tested · reviewed · documented · audit trail

FULL-SURFACE SDLC AUTOMATION

Bring Your Own Keys

Use your own Anthropic/OpenAI credentials. Keys stay service-side, not in agent artifacts.

BYOK
Planner + Validator

Orchestrator plans execution; validator enforces role ordering and mandatory rules.

Deterministic gates
K8s-Native Execution

Run agents as Kubernetes pods with PVC workspaces, namespace isolation, egress policies, and service account secret projection.

Production-grade
Budget + Timeout Control

Per-agent/per-task token-cost caps and timeout windows are enforced during orchestration.

Cost governance
Rules Engine

Inject required agents, human gates, and model/budget overrides from metadata, labels, priority, or changed files.

Policy as YAML
Human Review Gates

Pause runs for reviewer decisions with `sprintfoundry review`, then continue with feedback trail.

Controlled autonomy
Rework Loops

QA/security/code-review failures re-route to targeted agents with bounded rework cycles.

Iteration built-in
Monitor + APIs

Live board UI plus APIs for runs, events, logs, and workspace files (`/api/runs`, `/api/events`, `/api/log`, `/api/files`).

Observability
Artifact + Audit Trail

Every step writes durable artifacts plus runtime debug metadata for traceable audits.

Traceable output
Snapshot & Recovery

Export and restore whole-run state. Resume interrupted runs from checkpoints. PVC snapshots for K8s workspace durability.

Fault-tolerant
Project Creator CLI

`sprintfoundry project create` scaffolds config, integrations, agents, branch strategy, and runtime profile.

Fast onboarding
Direct Agent Mode

Skip full SDLC orchestration. Run any agent directly from CLI for targeted tasks — the default for single-agent runs.

Flexible workflow

UP IN MINUTES

  1. 1
    Install SprintFoundry

    Install via Homebrew/npm, then scaffold config with project create and run doctor.

  2. 2
    Configure your project

    Set repo, ticket source, agents, runtime/model overrides, and BYOK credentials.

  3. 3
    Point it at a ticket

    Run on GitHub/Linear/Jira/prompt. Use dry-run for planning-only mode.

  4. 4
    Monitor + approve gates

    Track runs in monitor and resolve review gates with sprintfoundry review.

terminal
# Install (Homebrew recommended)
brew tap Sagart-cactus/tap
brew install sprintfoundry

# Or install with npm
npm install -g sprintfoundry

# Create project config interactively
sprintfoundry project create

# Run preflight checks, then validate config
sprintfoundry doctor --project my-saas-app
sprintfoundry validate --project my-saas-app

# Run on a Linear ticket
sprintfoundry run --project my-saas-app \
  --source linear --ticket LIN-423

# Run on a GitHub issue
sprintfoundry run --project my-saas-app \
  --source github --ticket 42

# Or just describe it
sprintfoundry run --project my-saas-app \
  --source prompt --prompt "Add CSV export to the reports page"

# Optional: plan-only dry run
sprintfoundry run --project my-saas-app \
  --source linear --ticket LIN-423 --dry-run

# Run with Docker execution backend
SPRINTFOUNDRY_EXECUTION_BACKEND=docker sprintfoundry run \
  --project my-saas-app --source linear --ticket LIN-423

# Run with Kubernetes execution backend
SPRINTFOUNDRY_EXECUTION_BACKEND=k8s sprintfoundry run \
  --project my-saas-app --source linear --ticket LIN-423

# Export a run snapshot for recovery
sprintfoundry snapshot --export run-423

# Run a single agent (skip full SDLC)
sprintfoundry run --project my-saas-app \
  --source prompt --prompt "Review auth logic" --agent security

# Add a custom agent definition
sprintfoundry agent create

# Monitor runs and logs
sprintfoundry monitor --port 4310

# Resolve a human review gate
sprintfoundry review --workspace /tmp/sprintfoundry/my-saas-app/run-123 \
  --review-id review-123 --decision approved

YOUR BACKLOG.
HANDLED.

Stop context-switching. Stop writing boilerplate. Stop waiting for bandwidth.
Let your AI agents handle the sprint while you focus on what matters.

Open source · Self-hosted · BYOK · K8s-native · No vendor lock-in