Integrations
Composer to write the role contract. Library to start from living roles. BYOAI gateway for your models. Tools/MCP with edge enforcement. Raise the integration level at your own pace.
01·The four pillars
Kordana wraps your existing agents. The four pillars are adopted independently and compose with each other; no framework migration required.
Define mission, limits (what it does NOT do), access, autonomy, KPIs and budget. Versioned, signable, reusable across units and frameworks.
A catalog of living roles —collections, L1 support, research, QA— with KPIs, policies and benchmarks. Instantiate a unit in minutes with owner and budget.
A/B/C tier routing: premium model for critical reasoning, mid model for stable operation, low-cost model for bulk work. Fallback and per-unit budgets.
Kordana doesn't rewrite your agents: it wraps them. Every tool call passes through Policy Decision Point and Policy Enforcement Point before hitting the world. LangGraph, CrewAI, AutoGen, LlamaIndex, custom.
02·BYOAI Gateway · A/B/C routing
The gateway routes every call to the right bucket based on the role, the graph step, and the available budget. Bring your keys; we handle observability, fallback and cost control.
Critical reasoning, escalations, case resolution.
GPT-5, Claude Opus, Gemini Ultra
Daily operation, resolution with wide context.
GPT-5-mini, Claude Sonnet, Gemini Pro
Classification, extraction and repetitive work at scale.
GPT-nano, Haiku, Flash, self-hosted
Cascading fallback A→B→C with timeouts, retries and per-role budget. Every call is signed to audit with model, bucket and real cost.
03·Multi-framework tools & MCP
Official adapters for the most-used frameworks and native MCP to plug in tools from your stack. Every tool call crosses PDP → PEP before touching the world.
Kordana consumes existing MCP servers as tools for your units, and exposes its own MCP server so external assistants (Claude, ChatGPT, Cursor) operate your fleet with signed permissions.
Each tool call is evaluated against the signed role: allow, deny, require-approval or dry-run. Framework runners stay intact; the edge decides.
04·L0 → L3 adoption steps
No big-bang required. Start by inventorying, add telemetry when you're ready, and enable control once the role is signed.
Register units manually with owner, role and group. No telemetry, no enforcement. You get the map and accountability from day one.
Living roster
Connect the BYOAI gateway or the lightweight SDK. Live telemetry: throughput, spend, latency and errors per unit. Still no intervention.
Aggregate stoplight
Enable stop/play, freeze, inline approval and handoff to the escalation inbox. The fleet is now governable without a redeploy.
Live levers
Composer publishes signed role versions; PDP/PEP enforce every tool call; the quality flywheel feeds the next version.
Closed loop
Start at L0 today. You can reach L3 without changing a single framework.
