| name | nexus |
| description | Kailash Nexus — MANDATORY for HTTP/API/CLI/MCP unified deployment. Direct FastAPI/Flask BLOCKED. |
Kailash Nexus - Multi-Channel Platform Framework
Nexus is a zero-config multi-channel platform built on Kailash Core SDK that deploys workflows as API + CLI + MCP simultaneously.
Features
Nexus transforms workflows into a complete platform with:
- Zero Configuration: Deploy workflows instantly without boilerplate code
- Multi-Channel Access: API, CLI, and MCP from single deployment
- Unified Sessions: Consistent session management across all channels
- Enterprise Features: Health monitoring, plugins, event system, comprehensive logging
- DataFlow Integration: Automatic CRUD API generation from database models
- Production Ready: Deployment patterns, monitoring, troubleshooting guides
- Zero-Config Platform: Workflow-based platform without manual route definition
- Async-First: Uses AsyncLocalRuntime by default for optimal performance
Quick Start
from nexus import Nexus
workflow = create_my_workflow()
app = Nexus()
app.register("my_workflow", workflow.build())
app.start()
Reference Documentation
Getting Started
Core Concepts
Channel-Specific Patterns
Integration
Production & Operations
v1.3.0 Additions
Key Concepts
Zero-Config Platform
Nexus eliminates boilerplate:
- No manual routes - Automatic API generation from workflows
- No CLI arg parsing - Automatic CLI creation
- No MCP server setup - Automatic MCP integration
- Unified deployment - One command for all channels
Multi-Channel Architecture
Single deployment, three access methods:
- HTTP API: RESTful JSON endpoints
- CLI: Command-line interface
- MCP: Model Context Protocol server
Unified Sessions
Consistent session management:
- Cross-channel session tracking
- Session state persistence
- Session-scoped workflows
- Concurrent session support
Enterprise Features
Production-ready capabilities:
- Health monitoring endpoints
- Plugin system for extensibility
- Event system for integrations
- Comprehensive logging and metrics
- Correct channel initialization flow
- Proper workflow registration
When to Use This Skill
Use Nexus when you need to:
- Deploy workflows as production platforms
- Provide multiple access methods (API/CLI/MCP)
- Build enterprise platforms quickly
- Auto-generate CRUD APIs (with DataFlow)
- Replace traditional frameworks with workflow-based platform
- Create multi-channel applications
- Deploy AI agent platforms (with Kaizen)
Integration Patterns
With DataFlow (Auto CRUD API)
from nexus import Nexus
from dataflow import DataFlow
db = DataFlow(...)
@db.model
class User:
id: str
name: str
app = Nexus()
for name, wf in db.get_workflows().items():
app.register(name, wf)
app.start()
With Kaizen (Agent Platform)
from nexus import Nexus
from kaizen.core.base_agent import BaseAgent
agent_workflow = create_agent_workflow()
app = Nexus()
app.register("agent", agent_workflow.build())
app.start()
With Core SDK (Custom Workflows)
from nexus import Nexus
from kailash.workflow.builder import WorkflowBuilder
app = Nexus()
app.register("workflow_1", create_workflow_1().build())
app.register("workflow_2", create_workflow_2().build())
app.register("workflow_3", create_workflow_3().build())
app.start()
Standalone Platform
from nexus import Nexus
app = Nexus()
app.register("workflow_a", workflow_a.build())
app.register("workflow_b", workflow_b.build())
app.start()
Critical Rules
- ✅ Use Nexus for workflow platforms
- ✅ Register workflows, not individual routes
- ✅ Leverage unified sessions across channels
- ✅ Enable health monitoring in production
- ✅ Use plugins for custom behavior
- ✅ Nexus uses AsyncLocalRuntime by default (correct for Docker)
- ❌ NEVER mix raw HTTP routes with Nexus
- ❌ NEVER implement manual API/CLI/MCP servers when Nexus can do it
- ❌ NEVER skip health checks in production
Deployment Patterns
Development
app = Nexus()
app.register("my_workflow", workflow.build())
app.start()
Production (Docker)
from nexus import Nexus
app = Nexus()
app.register("my_workflow", workflow.build())
app.start()
With Load Balancer
docker-compose up --scale nexus=3
Channel Comparison
| Feature | API | CLI | MCP |
|---|
| Access | HTTP | Terminal | MCP Clients |
| Input | JSON | Args/JSON | Structured |
| Output | JSON | Text/JSON | Structured |
| Sessions | ✓ | ✓ | ✓ |
| Auth | ✓ | ✓ | ✓ |
| Streaming | ✓ | ✓ | ✓ |
Related Skills
Support
For Nexus-specific questions, invoke:
nexus-specialist - Nexus implementation and deployment
release-specialist - Production deployment patterns
- ``decide-framework
skill - When to use Nexus vs other approaches