Kurahi
Request materialsContact us
EN

Products

All editionsBusinessIndustrialCoreCapabilities
CapabilitiesAutopilotSecurity & governanceIntegrationsPricingResources
Request materialsContact us

Kurahi by KODA SōKEN · self-hosted enterprise agent platform

Agents that work for you. Decisions that stay yours.

Kurahi connects to the systems you approve, prepares the routine work your teams do every day (invoice cases, reply drafts, approval packages, design documents for legacy code) and brings every decision to the right person. You set how far each routine may go on its own. Japanese-first, in English too.

See a workflowDiscuss your workflowStart free
  • Runs inside your network
  • Autonomy from L0 to L3, set by you
  • Signed evidence for every run

What Kurahi prepares

One workflow, start to finish

An invoice arrives by email. Most invoices follow the routine path; a few raise an exception that a person investigates. Business edition, routine at L1 Prepare.

Routine path

Routine invoice path: an invoice arrives by email, Kurahi prepares a work item, a person reviews and decides, and the approval history and signed evidence are recorded01An invoice arrivesThe routine sees the newmessage in a connectedmailbox02Kurahi prepares thecaseA work item with a summary,the source and a replydraft03A person decidesThe approver reviews theprepared case andapproves, returns orcancels04The decision isrecordedApproval history and signedevidence of the runRoutine invoice path: an invoice arrives by email, Kurahi prepares a work item, a person reviews and decides, and the approval history and signed evidence are recorded01An invoice arrivesThe routine sees the new message in aconnected mailbox02Kurahi prepares the caseA work item with a summary, the source and areply draft03A person decidesThe approver reviews the prepared case andapproves, returns or cancels04The decision is recordedApproval history and signed evidence of therun
Fig 0.1Routine invoice intake with Kurahi Business. The person's step is outlined.

Exception path

Exception path: bank details differ, the case is held as suspected fraud and cannot be approved, a person investigates and clears the flag with a reason or rejects the case01Bank details differThe message asks to change the payeeaccount02The case is heldFlagged as suspected fraud; it cannot beapproved03A person investigatesChecks with the supplier, then clearsthe flag with a reason or rejects thecaseException path: bank details differ, the case is held as suspected fraud and cannot be approved, a person investigates and clears the flag with a reason or rejects the case01Bank details differThe message asks to change the payeeaccount02The case is heldFlagged as suspected fraud; it cannot beapproved03A person investigatesChecks with the supplier, then clears theflag with a reason or rejects the case
Fig 0.2Exception path. Only a person clears the flag, with a written reason.
Try the guided demoThe Business edition

Who does what

Employees and managers

  • Open the work queue and see what was prepared, with its sources
  • Approve, send back or cancel with a written reason
  • Clear flags such as suspected fraud, which only a person can do
  • Read a morning brief of what was handled and what waits for you

IT and administrators

  • Install Kurahi on your own servers and connect your identity provider
  • Turn on only the connectors you approve, read-only by default
  • Set each routine's autonomy level and standing approvals
  • Watch runs, verify evidence and stop any routine at once

Built for organisations that answer for their work

  1. Fig 1

    Your data stays in your network

    Kurahi is installed on your servers. Work items, documents, evidence and the audit log stay there, and you decide which models and cloud services, if any, take part.

  2. Fig 2

    You decide how much to hand over

    Every routine runs at an autonomy level from L0 observe to L3 act externally. The model never holds a tool that can send, pay or delete; the engine executes only what the level allows.

  3. Fig 3

    It works the way Japanese companies work

    稟議 approval routes, 15 department workspaces, connectors to kintone, freee, Money Forward, SmartHR, LINE WORKS and Box, and documents in Word, Excel and PowerPoint.

An edition for your work, one platform

Choose the edition for the work you do. Every edition runs on Kurahi Core, with the same controls.

Core The platform under every edition: projects, policy, approvals, connectors, autopilot and signed evidence.

220 capabilities. Every one verified in code.

The full list of what Kurahi Core and each edition do, published. If it is on this list, it is in the source code.

See all capabilities

Choose how much to hand over

Autonomy is set per routine, never assumed. A routine earns a higher level from its own record, a person accepts it, and a serious error lowers it again.

Autonomy ladder: L0 observe, L1 prepare, L2 act internally, L3 act externally under a standing approval; payments, contracts, decisions about people, bank-detail changes and anything flagged always go to a personL3Act externallySend outside, only under a person's standing approval.L2Act internallyFile, route, assign, update internal records.L1PrepareWork items, reply drafts, documents, meeting timeproposals.L0ObserveRead, classify, report. No actions.Always a personPaymentsContracts and signaturesDecisions about peopleBank-detail changesSecret or access changesDeleting dataAnything flaggedAutonomy ladder: L0 observe, L1 prepare, L2 act internally, L3 act externally under a standing approval; payments, contracts, decisions about people, bank-detail changes and anything flagged always go to a personL3Act externallySend outside, only under a person'sstanding approval.L2Act internallyFile, route, assign, update internalrecords.L1PrepareWork items, reply drafts,documents, meeting timeproposals.L0ObserveRead, classify, report. Noactions.Always a personPaymentsContracts andsignaturesDecisions about peopleBank-detail changesSecret or accesschangesDeleting dataAnything flagged
Fig 4Autonomy levels and the decisions that always stay with a person.
Kurahi Autopilot panel with fictional data: a routine lowered from L2 to L1 by the watchdog, waiting for a person to resume it
Fig 5When a run falls outside its usual pattern, the watchdog lowers the routine a level and pauses it until a person resumes it with a reason. Fictional data.
How Autopilot works

Inside your boundary

Kurahi is a service you run, not a service you send data to. People sign in with your identity provider, the agents read your systems where they are, and evidence stays on your servers.

Deployment diagram: people, Kurahi, your systems and the models you run sit inside your network boundary; cloud services and external models are outside and reached only through connectors an administrator turns onYour networkOnly what you enablePeopleStaff and approvers signin with your SSOKurahiEditions and work queueAutopilot and policySigned evidence and auditYour systemsFile shares, databases,legacy source codeModels you runLocal or self-hostedCloud servicesMicrosoft 365, kintone,external models: each offuntil configuredconfigured connectors onlyDeployment diagram: people, Kurahi, your systems and the models you run sit inside your network boundary; cloud services and external models are outside and reached only through connectors an administrator turns onYour networkOnly what you enablePeopleStaff and approvers sign in with your SSOKurahiEditions and work queueAutopilot and policySigned evidence and auditYour systemsFile shares,databases, legacysource codeModels you runLocal orself-hostedCloud servicesMicrosoft 365, kintone, external models: eachoff until configured
Fig 6Deployment. Everything outside the boundary is off until an administrator configures it.

Built to pass your security review

The controls your information security team will ask about are part of the product, not an add-on.

Security and governance
  • Single sign-on with OIDC or SAML 2.0
  • SCIM 2.0 provisioning, departments, teams and roles
  • Attachment quarantine and malware scanning that fails closed
  • Signed evidence for every run and a hash-chained audit log
  • Enterprise package: consumer-channel plugins omitted and refused at runtime
  • Emergency stop for every routine, even without the API

SSO, SCIM, roles, attachment scanning, signed evidence and audit are included in every plan, Free included.

Works with what you already run

Connectors are off by default and read-only by default. Every write is a separate administrator opt-in that waits for a person's approval.

  • Microsoft 365
  • Gmail
  • Microsoft Entra ID
  • kintone
  • freee 会計
  • マネーフォワード クラウド請求書
  • SmartHR
  • LINE WORKS
  • Box
  • IBM watsonx
  • A2A
  • MCP
  • OIDC
  • SAML 2.0
  • SCIM 2.0
  • OpenTelemetry

Product names are trademarks of their respective owners. Their use does not imply endorsement.

All integrations

Start free. Scale by agreement.

The self-hosted platform is free. Digital staff and enterprise operations are by written agreement.

Free

Editions, work queue, connectors, Office documents, SSO, SCIM, roles, attachment scanning and autopilot at L0 and L1.

Start free

Enterprise

Everything in Free, plus digital staff at L2 and L3, the data governance suite, deployment without internet access and SLA support.

Get a quote
Compare plans

Resources

Start with one workflow.

Tell us about the work you want to hand over. We will show you Kurahi on your own process, then help you decide how far to take it.

  1. Contact us

    A conversation about the work, the systems involved and who approves what. A demo on a process like yours.

    Contact us

  2. Get a quote

    For digital staff, the data governance suite, air-gapped deployment and SLA support, by written agreement.

    Get a quote

  3. Start free

    Install Kurahi on your own server and run the editions, the work queue and autopilot at L0 and L1 at no charge.

    Start free

Frequently asked questions

Security

Where does our data live?

In your network. Kurahi is installed and operated on your own servers; work items, documents, evidence and the audit log are stored there. Connectors and model providers are off until an administrator turns them on, so data reaches a cloud service only through the ones you configure.

What leaves an audit trail?

Every autopilot run writes a signed evidence bundle: a hash-chained event log and a signed manifest recording what was read, what the model proposed, each decision and the approval it ran under. Approvals, flag clearances and configuration changes are in the audit log. Evidence can be verified offline.

Product

Which AI models does Kurahi use?

The ones you choose. Agent sessions work with hosted, self-hosted and local models, including models that run inside your network and IBM watsonx.ai. Autopilot reasons through a model backend with no tools. Changing provider is configuration, not code.

How is autonomy limited?

Each routine has an autonomy level set by your administrator, from L0 observe to L3 act externally. L3 only works under a standing approval a person made, limited to named recipients, a template, a daily maximum and an expiry. Payments, contracts, decisions about people, bank-detail changes and anything flagged always go to a person.

Getting started

What is free?

The self-hosted platform: the editions, the work queue with approval routes, the connectors, Word, Excel and PowerPoint documents, SSO, SCIM and roles, attachment scanning and autopilot at L0 and L1. Security is included in every plan. Digital staff at L2 and L3 and the enterprise features are by written agreement.

Do you support Japanese?

Kurahi is designed Japanese-first: the console, the documentation, approval routes and design documents work in Japanese, and in English too. Enterprise agreements include SLA support in Japanese and English.