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.

  • Runs inside your network
  • Autonomy from L0 to L3, set by you
  • Signed evidence for every run

The whole platform

Everything in Kurahi, at a glance

Two editions, Business and Industrial, on Kurahi Core. All 244※ capabilities are verified in the source code.

Kurahi Business 57 capabilities※

The back office, department by department

Learn more

Functional pack: Starts with a functional pack configured for this work, with its own queues, forms and checks. Department workspace: Starts with the company-wide department workspace: its own queue, incoming mail routed to it, the shared checks and standard approval.

※ As of Kurahi 2.6.0 (1 November 2026). Capabilities counted as verified in the source code.

All capabilities

In the product

Prepared by agents. Checked by policy. Decided by people.

Real screens from the Kurahi console, shown with sample data. An invoice asks to change the supplier's bank account: the agent prepares the case, a policy check stops it, and only a person can decide.

  1. 01

    Prepared

    Work arrives as cases in each department's queue, with the source attached and the status visible to everyone involved.

    Kurahi work queue for Finance & Accounting with four cases awaiting review
  2. 02

    Checked

    Every case passes the company's policy checks. A bank-change request fails as suspected fraud and blocks approval, with the policy version on record.

    Policy check 'Suspected fraud: verify bank-change request' failed and blocking
  3. 03

    Decided

    Only a signed-in person records the decision. Required approvals and separation of duties apply, and every step leaves signed evidence.

    Electronic approval panel: approvals 0 of 2, separation of duties enabled, approve, send back or cancel

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.
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 for 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 Accounting
  • Money Forward Cloud Invoice
  • 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

Four steps, at your pace.

Start wherever suits you. Starting free needs no sales contact.

  1. Download materialsProduct, security and editions overviews as PDF.
  2. Contact & demoA workflow demonstrated on a process like yours.
  3. Get a quoteEnterprise and the first workflow activation, fixed in writing.
  4. Start freeDownload and evaluate on your own. No sales contact needed.

Digital staff at L2 and L3, the data governance suite, air-gapped deployment and SLA support are by written agreement.

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.