Know where a fact comes from.
Native records belong to your workspace. Connected services remain the authority for their external records. A synchronized copy or a draft does not mean an external action has succeeded.
The architecture, in plain language
One workspace.
Clear responsibilities.
You and Kora work with the same business context. The system keeps track of who can act, where each record belongs, and what actually happened.
Your teamPages, records and actions
KoraQuestions and proposed actions
Shared permissions & business servicesWorkspace access · Approval rules · Recorded outcomes
Workspace recordsNative business data
Connected toolsExternal records and results
The same rules,
whoever takes the action.
A teammate making a change in the interface and Kora using a tool go through the same application services. Workspace membership, roles and approval rules come from trusted server context.
That keeps a conversational request connected to the business rules behind the screen.
Keep a request separate from a result.
A proposed action, an approval, a queued job and a confirmed outcome are different states. Kora retains conversations and execution records so you can inspect the work.
Make access part of the system.
Your identity, workspace and role determine what you can see and do. Credentials and connection choices stay outside the model’s control.
Give long-running work a recovery path.
Background workers handle work that takes time. Persistent state and retry paths help the system recover without treating a failed or unfinished operation as complete.
For your technical team
The browser connects to a Next.js application. Application services enforce trusted actor context and manage native business records in Supabase Postgres and Storage.
The Kora runtime owns conversations, runs, tools, approvals, memory and retrieval. Durable workflows and background workers manage asynchronous execution. Connectors exchange data with external providers and preserve their authority over external records.
The public showcase is a separate static build hosted on Cloudflare. Demo releases must identify their application revision, sample-data version and runtime destination. Deployment history alone does not make an older app compatible with a newer database.