Skip to main content

alphaswarm-local

Catalog date: 2026-06-24.

alphaswarm-local packages a self-hosted AlphaSwarm backend and links it to the hosted AlphaSwarm platform. It enables "Bring Your Own Backend" (BYOB) scenarios where sensitive data and heavy compute remain on the developer's machine while the hosted UI provides the orchestration and visualization surface.

For personal or limited-scope hosted-link development, the recommended user/operator facade is:

alphaswarm-cli local dev ...

That facade is documented in the local environment lifecycle runbook. alphaswarm-local remains the lower-level package/service primitive and owns stateful local backend lifecycle details.

Role​

  • Hosted-link lifecycle primitive: Owns stateful local backend lifecycle details for the personal personal-hosted-link profile, while alphaswarm-cli local dev ... provides the recommended operator facade.
  • Hybrid Development: Links a local backend to the hosted platform via a device-paired reverse tunnel.
  • Developer Quickstart: Bootstraps a local environment with Docker Compose and sensible defaults.
  • Simulation: Provides high-fidelity simulation of market data, execution venues, and risk gates.
  • Local Persistence: Manages local SQLite/PostgreSQL, Redis, and file-based data stores.
  • Local Orchestration: Owns Compose orchestration by default and k3d where that lower-level path is explicitly selected and supported.

Connection Model​

The backend dials OUT to the hosted platform's control plane. Requests from the hosted UI are proxied through the reverse tunnel to the local backend. Authorization is handled against the central alphaswarm_auth service.

The first hosted-link profile is personal-hosted-link: local services run on the client machine, Compose is the default orchestrator, and the hosted connection uses the hosted-link/device tunnel. Azure CLI or Entra profile discovery is only a convenience for finding a tenant id. Platform auth still uses:

alphaswarm-cli auth login --device --entra-tenant <tenantId>

Cloudflare DNS is deferred and unsupported for this first profile. Use the hosted-link/device tunnel connection path.

Relationship to local platform overlay​

The local platform overlay is the standalone single-machine deployment path: a local Compose stack that runs without hosted platform linking. alphaswarm-local is the lower-level primitive for hosted linking and local backend lifecycle, and alphaswarm-cli local dev ... is the recommended facade for personal hosted-link operations.

Repository​