A
Data stored in Kabyn
Store customers, projects, requests, tasks, assets and approvals in Kabyn when it owns the record.
- State and rules in one model
- Validation on every command
- Events for meaningful outcomes
Kabyn platform
One governed platform for every way your business works.
Applications, people using AI chat through MCP, and autonomous agents use the same business data, commands and rules. Kabyn controls what each can see and do, brings in a person when needed, and records what happened.
01 / A purchase approval
Follow one request from start to finish.
A command starts the work. Business logic handles it, emits an event and reacts to what happens next.
- 01
Object
Purchase request created
Kabyn stores the supplier, amount, budget, requester and status.
- 02
Command
Approval requested
An application, a person using AI chat through MCP or an autonomous agent calls
submitForApproval. The caller cannot write directly to the database. - 03
Business logic
The command is handled
Kabyn validates the request, checks the actor and approval threshold, updates the status and emits
ApprovalRequested. - 04
Event-triggered logic
Finance review opens
The
ApprovalRequestedevent states what happened. It triggers logic that creates the review and notifies Finance. - 05
Approval
Finance decides
An authorised approver reviews the details and submits the decision through
approvePurchase. - 06
Business logic
The decision is applied
Kabyn validates the approver, updates the request and emits
PurchaseApprovedorPurchaseRejected. - 07
Event-triggered logic
The next step starts
The outcome event triggers logic that routes approved requests to purchasing or returns rejected requests with a reason. The audit log records the commands and logic that ran, the decision and each event.
02 / How it fits
Different ways in. One set of rules.
Used by
ApplicationsAI chat through MCPAutonomous agents
Ways in
QueriesCommandsMCPComponents
Governed operation
Business logicPermissionsPoliciesApprovals
Operational record
Kabyn objects & dataEventsAudit recordsConnected systems
03 / Choose where data lives
Store it in Kabyn or keep it in the source system.
B
Connected source systems
Keep the record in an existing database, app, document or API. Kabyn still applies the same commands and rules.
- Named commands for every caller
- The same policy checks
- Shared business logic across systems
04 / Before anything changes
Kabyn asks four questions.
Can this actor see or change it?
Is this action inside the business rules?
Does this decision require human judgement?
Can we explain what happened and why?
Governed actions, not raw access