Technical Stack and Deployment

This page summarizes the audited languages, frameworks, infrastructure-as-code, CI/CD, and environment configuration patterns.

Stack by system domain

Domain	Primary repos	Stack observed
Python services	alphaswarm, alphaswarm_api, alphaswarm_auth, alphaswarm_controller, alphaswarm_data, alphaswarm_mlops, alphaswarm_worker, most backend packages	Python packaging via pyproject.toml; FastAPI/Pydantic markers; Typer/Click-style CLI patterns; pytest/ruff/mypy in many repos.
Frontend apps	alphaswarm_ui, alphaswarm_website, alphaswarm_client, alphaswarm_admin, alphaswarm_ide	TypeScript; Next.js in hosted UI/website patterns; Vite/local client markers; Theia/Electron/browser app packages in IDE; pnpm/yarn lockfiles.
Docs site	alphaswarm_docs	Docusaurus-style docs, TypeScript config, Fern/OpenAPI assets, link/lint/check scripts, changelog automation, Cloudflare workers/static assets.
Platform/IaC	alphaswarm_platform, alphaswarm_local, alphaswarm_ops_console, alphaswarm_observe, alphaswarm_kb_federation, alphaswarm_learning	Kubernetes manifests, Helm charts, Dockerfiles, Compose stacks, Terraform in hosted platform, deployment templates.
Orchestration/data	alphaswarm_orchestration, alphaswarm_data, alphaswarm_ingest, alphaswarm_platform	Dagster/Prefect boundary, data-provider plugins, Kafka/Flink template markers, market-data source integrations.
AI/ML	alphaswarm_mlops, alphaswarm_models, alphaswarm_eval, alphaswarm_rl, alphaswarm_learning, alphaswarm_agents	Model/eval/RL packages, registry/spec docs, LLM provider markers, OpenTelemetry AgentOps/EVAL markers.

Deployment architecture

CI/CD findings

Updated from a working-tree recount (2026-08): the 2026-07-14 static audit's counts below are superseded — the agentic workflows enhancement program's WS0 pass (see agentic-workflows-enhancement/handoff.md) has since added .github/workflows/ to most previously zero-CI repos and added an actionlint.yml to most CI-bearing repos.

A current count of .github/workflows/*.yml finds GitHub Actions workflow files in 33 of the 41 checked-out repositories. Highest workflow concentration appears in:

• alphaswarm — 19 workflows, including release/change, CI, and platform checks.
• alphaswarm_ide, alphaswarm_platform — 8 workflows each.
• alphaswarm_core — 4 workflows.
• alphaswarm_agents, alphaswarm_bots, alphaswarm_cli, alphaswarm_config, alphaswarm_docs, alphaswarm_internal, alphaswarm_local, alphaswarm_ui — 3 workflows each.
• alphaswarm_admin, alphaswarm_auth, alphaswarm_client, alphaswarm_controller, alphaswarm_data, alphaswarm_eval, alphaswarm_finops, alphaswarm_kb, alphaswarm_kb_federation, alphaswarm_mcp, alphaswarm_mlops, alphaswarm_observe, alphaswarm_observe_js, alphaswarm_orchestration, alphaswarm_qap, alphaswarm_rl, alphaswarm_website — 2 workflows each.

Repos with exactly one workflow: alphaswarm_graph, alphaswarm_learning, alphaswarm_models, and alphaswarm_worker.

Repos with no .github/workflows/ directory at all: alphaswarm_api, alphaswarm_assistant, alphaswarm_catalog, alphaswarm_index, alphaswarm_ingest, alphaswarm_ops_console, alphaswarm_research, alphaswarm_viz. This is a substantially smaller zero-CI set than earlier in the agentic-workflows-enhancement program (see that plan's gaps.md G1 for the historical baseline) — most of the gap has since been closed by the WS0/WS2 work, though the remaining eight repos have not yet been wired.

Infrastructure-as-code and orchestration

IaC / runtime	Repositories	Notes
Dockerfiles	alphaswarm_admin, alphaswarm_api, alphaswarm_bots, alphaswarm_data, alphaswarm_graph, alphaswarm_kb_federation, alphaswarm_learning, alphaswarm_mcp, alphaswarm_mlops, alphaswarm_observe, alphaswarm_ops_console, alphaswarm_platform, alphaswarm_ui, alphaswarm_worker	Used for standalone services, frontend images, worker images, data services, and platform templates.
Docker Compose	alphaswarm_api, alphaswarm_local, alphaswarm_mlops, alphaswarm_observe, alphaswarm_platform	Local/hybrid stacks and observability/dev service orchestration.
Kubernetes manifests	alphaswarm_platform, alphaswarm_local, alphaswarm_controller, alphaswarm_docs, alphaswarm_kb_federation, alphaswarm_learning, alphaswarm_observe	Hosted cell/base services and package-specific deploy directories.
Helm charts	alphaswarm_platform, alphaswarm_local, alphaswarm_kb_federation, alphaswarm_learning, alphaswarm_observe, alphaswarm_mlops	Cell data plane, tenant MCP, fleet/platform charts, observability, federation, learning.
Terraform	alphaswarm_platform, alphaswarm_client markers	Hosted infrastructure and frontend demo/deploy surfaces.
Dagster/Prefect	alphaswarm_orchestration, alphaswarm_platform, alphaswarm	Portable task graph boundary plus platform pipeline/deployment assets.

Environment configuration model

Configuration is split across repo-local package settings, deployment manifests, and environment variables. Key patterns:

• Prefix conventions use ALPHASWARM_* and service-specific prefixes such as tenant-router, auth, ops-console, worker, and UI variables.
• Hosted authentication depends on OIDC issuer/audience/JWKS settings and verified tenant/workspace claims.
• alphaswarm_auth owns Postgres-backed identity/device state with local SQLite fallback for development.
• Worker and CLI flows rely on OAuth device login and registered device state rather than static shared credentials.
• Ops console actions are data-driven catalog entries; executable commands are configured, not supplied by requests.
• Data-provider credentials should resolve through configured credential stores/env references; documentation should avoid raw values.

Deployment recommendations

2026-08-07 first-party service alignment

• alphaswarm_platform owns ArgoCD selection and policy, while canonical API and Observe deployment artifacts live in alphaswarm_devops.
• The stateless release selects Admin and Observe through alphaswarm-services and the raw API bundle through alphaswarm-api.
• alphaswarm_config remains embedded in host runtimes and must not be modeled as an independently deployable backend.
• API, Admin, and Observe expose Prometheus scrape endpoints and structured request/error telemetry; Config exports metrics through its host process.

1. Treat alphaswarm_platform as the canonical hosted orchestration and policy source; consume repository-owned service manifests from alphaswarm_devops.
2. Treat alphaswarm_local as the canonical hybrid/local deployment source; do not mix it with hosted production manifests without an explicit runbook.
3. Treat alphaswarm_ops_console as a privileged operator UI and keep it separate from alphaswarm_api.
4. Publish cross-repo docs to alphaswarm_docs, not to individual service READMEs, except for service-local quickstarts.
5. Add a generated service catalog in alphaswarm_docs that records repo, package name, image name, chart path, workflow path, and owner domain.