Sales outreach
Point the Sales layer at CRM exports and draft cold emails, follow-ups, and battlecards in a single swarm run. Budget caps keep costs predictable.
Use-case scenario
Swarm 357
Layered specialists, portable memory, and honest cost controls, without pretending three hundred agents replace governance.
Landing 0.2.2 · techtide-swarm 0.2.2
Type a business task and watch a simulated route through the swarm. Demo writes go through a same-origin BFF. The write key stays server-side, never in the browser bundle.
Marketing site and docs bring people in; the swarm CLI and YAML layers coordinate work; Memvid (optional Beta bridge) stores portable memory; local JSONL traces and cost reports keep production honest. Opik cloud is not implemented.
Read status docspip install techtide-swarm==0.2.2. The wheel ships the compact 357-agent roster and soul templates so swarm boot works out of the box.
swarm boot expands six business layers plus management meta-agents, with per-layer budgets and model preferences.
swarm run routes through the Conductor, executes role agents with tools, and reports cost and latency you can show FinOps.
Core runtime (Python + Memvid bridge) lives in swarm-357; this site is the separate Next.js product surface, so memory, hooks, and UI ship on independent release trains.
Read the docsSix business layers (Sales, Support, Marketing, SEO, Research, Operations) plus Management meta-agents. Pre-defined roles, not blank-slate prompts.
Flat-file topics ship Stable by default. Optional Memvid bridge (Beta) adds portable .mv2 capsules with WAL crash safety, search, and verify. No database server required.
Per-agent budget caps enforced at runtime, per-layer cost controllers, and a swarm cost CLI. Know what you spend before production reviewers ask.
Pick a layer to browse roles. No endless card wall.
Real-time from public GET endpoints. Refreshed on each visit.
Open /api/health (JSON) to verify roster size.
Named Agent Roles
Business Layers
Security Gate Rules
Total Cost (USD)
Last 10 swarm executions logged in real time.
Illustrative composites of how teams use Swarm 357. Not customer endorsements.
Point the Sales layer at CRM exports and draft cold emails, follow-ups, and battlecards in a single swarm run. Budget caps keep costs predictable.
Use-case scenario
Optional Memvid .mv2 (Beta bridge) lets agents recall prior research without re-running prompts. Flat-file topics remain the Stable default.
Use-case scenario
BashSecurityGate, HITL for Bash, budget caps, and Memvid verify give reviewers concrete controls, not a blank-slate agent sandbox.
Use-case scenario
Load one file and Claude Code understands the swarm: layers, CLI, memory, bridge, and STATUS maturity. Faster engineer onboarding.
Use-case scenario
Feed quarterly goals into swarm plan for a phased rollout with budget estimates. Useful as a planning artifact, not a substitute for human sign-off.
Use-case scenario
Open-source agent harness and memory bridge. Bring your own Anthropic keys and hosting.
Full swarm package, bring your own keys
Priority support + architecture review
Install techtide-swarm, optional-build the Memvid bridge, and follow the quickstart to run your first layer task.
Start with swarm init