Kora
Your company's operations, formalized and running
Define your business processes once. Assign each step to humans, AI agents, or both. Every decision audited, every handoff tracked.
Running a company shouldn't require tribal knowledge
Processes live in people's heads.
When someone leaves, the process leaves with them.
AI agents can't join real operations.
Demo-ready in an hour. Production-ready? Nobody has that infrastructure.
Human and AI work are managed separately.
No shared process, no clean handoffs, no gradual migration path.
Automation tools ignore your org chart.
No roles, no authority limits, no escalation. Every workflow is bespoke wiring.
You can't audit what isn't formalized.
Compliance from email threads and memory is not compliance.
One engine for how your company operates
Describe your operations. Kora formalizes them.
How Kora works
Two layers, one semantic model. Run the same engine locally, self-hosted, or managed.
Kora FAQ
Is Kora another workflow automation tool like n8n or Zapier? +
No. Those tools mostly wire together API calls. Kora formalizes how your company operates - org structure, roles, authority, human and agent handoffs - and executes that as durable, auditable workflows.
How is this different from CrewAI or LangGraph? +
Agent frameworks orchestrate LLM chains. Kora orchestrates business processes where agents are one participant alongside humans. It adds process formalism, org-aware routing, human steps, compliance-grade audit, and long-running execution.
Do I need to learn BPMN? +
No. You write YAML, or describe a process in natural language and let AI draft it. Kora compiles to BPMN-aligned intermediate representation internally for execution semantics and interoperability.
Can I start with humans and add agents later? +
Yes. That is the intended migration path. Define the process once with role-based assignment, start with humans filling every role, and later assign an agent to the same role without changing the process graph.
What happens when an agent step fails or exceeds its budget? +
Temporal handles retries and timeouts automatically. Agent steps run with scoped tool access and token budget ceilings. If limits are exceeded, the step fails and follows the escalation path you defined, including handoff to a human if needed.
Is Kora open source? +
Core engine, compiler, CLI, and runtime are Apache 2.0. The managed platform layer for tenancy, governance, and enterprise operations is commercially licensed. The open source core is intended for production use.
What integrations are supported today? +
Channels include Slack, Teams, Email, and WhatsApp. Connectors include PostgreSQL, HTTP, and CLI. Agent providers include Anthropic and MCP. New integrations follow a plugin model with compile-time validation and runtime execution bundles.
What does BPMN-aligned mean exactly? +
Kora implements an executable subset of BPMN 2.0 semantics progressively. Unsupported constructs are rejected explicitly at compile time instead of being silently ignored, so you keep standard process semantics without pretending unsupported cases work.
How does the org model affect process execution? +
Tasks declare the role or capability required, not a specific person. The org model resolves assignment at runtime based on role membership, capability matching, and authority constraints. Escalation follows reporting lines, and budget limits are enforced per role.
Can I run Kora alongside my existing tools? +
Yes. Kora connects to existing systems through connectors like SQL, HTTP, and CLI, and through channels like Slack, Teams, and Email. It does not replace your CRM or project tool - it orchestrates the workflows that span them.
Have more questions? Get in touch