-
crewAI
Framework for orchestrating role-playing, autonomous AI agents. By fostering collaborative intelligence, CrewAI empowers agents to work together seamlessly, tackling complex tasks.
CrewAI is excellent at what it's designed for: a "crew" of role-shaped agents collaborating on one task. Declarative Agent + Task + Process (sequential or hierarchical), with strong primitives for delegation between agents inside the same crew.
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
-
AutoGen is conversation-shaped: agent-to-agent chat with an explicit GroupChat manager. Great for "two LLMs argue and converge on an answer" — code-writer vs code-reviewer, advocate vs critic.
-
n8n
n8n is a workflow automation platform for building AI-powered workflows and agents, connecting any AI model to any business system with full control over data, security, and deployment. Build visually or in code while n8n handles infrastructure from prototype to production with fully auditable executions.
n8n and similar visual workflow tools were on the list for one specific reason: leadership likes seeing the boxes-and-arrows. But the LLM nodes aren't first-class — you'd be wrapping every model call in HTTP, and the graph is in a database, not in code that's reviewable in a PR. Auditability and reproducibility are both worse than the LangGraph + bus path. (n8n is a great fit for non-LLM SOAR-style automations, just not for this.)
-
vllm-mlx
OpenAI and Anthropic compatible server for Apple Silicon. Run LLMs and vision-language models (Llama, Qwen-VL, LLaVA) with continuous batching, MCP tool calling, and multimodal support. Native MLX backend, 400+ tok/s. Works with Claude Code.
We run one local LLM — GLM-4.7-Flash 8-bit on a Mac M1 (64 GB) via vllm-mlx — and every role calls it with a different system prompt and a different tool whitelist. The resilience comes from a FailoverChatModel (first described in an earlier post) that transparently falls back to a Qwen3 backup on a studio1 box if the m1 dies, and flips back the moment the primary recovers.
-
langchain-failover
Primary/secondary failover wrapper for LangChain chat models, with tool-calling preserved across failover.
📦 New — we open-sourced it. That FailoverChatModel is now a standalone, dependency-light package on PyPI: langchain-failover. pip install langchain-failover, point it at two chat models, and you get the same primary/secondary failover that keeps this SOC's brain online when a GPU box drops off — connection-aware (it walks the exception's cause chain), recovery-aware (logs the flip back), and mid-stream-safe. The non-obvious part it gets right: tool-calling survives the failover — it binds your tools on both legs, so an agent mid-investigation doesn't lose its tools the instant it fails over. That's exactly what a SOC role needs at 3 AM. Source, tests, and docs: github.com/vinayvobbili/langchain-failover. 🚀 {: .prompt-tip }
-
security-ops-platform
Discontinued Open-source security detection & response platform: 50+ tool integrations, an on-prem LLM investigation-agent fleet with MCP, self-healing Webex/Teams bots, and 80+ Flask SOC web apps. [GET https://api.github.com/repos/vinayvobbili/security-ops-platform: 404 - Not Found // See: https://docs.github.com/rest/repos/repos#get-a-repository]
The full module lives at src/components/soc_in_box/ — agents, schemas, bus wrapper, verdict store, HITL store, web routes, systemd units, README.
Related posts
-
OpenChamber: An Agentic Development Environment
-
Show HN: Jido Assembly; Slack Clone in Pure Elixir with Integrated Agents
-
Show HN: Aidress – open-source discovery and trust registry for agents
-
SecurityPolicy restrictions unenforced by default sandbox back end in PraisonAI
-
Handoffs can turn one task into a 15x token bill