Integrations

Works with what you already run.

Kurahi connects to the systems your teams use today, under the same rules: off by default, read-only by default, every write approved by a person.

Microsoft 365 and Google

  • Microsoft 365

    Mail, calendar, OneDrive and SharePoint files. Draft-only replies with attachments, and a mail watcher for real-time triggers.

  • Gmail

    Mail, with sending as a separate approved opt-in.

  • Microsoft Entra ID

    Sign-in, users and groups.

  • Word, Excel, PowerPoint

    Office documents with editable charts, written into the Project.

Japanese SaaS

  • kintone

    Records of the apps you list, allow-listed fields; comments and record creation as approved opt-ins.

  • freee 会計

    Companies, deals, partners, account items and receipt metadata.

  • マネーフォワード クラウド請求書

    Billings, quotes and partners.

  • SmartHR

    Employees (work fields only) and departments, read-only.

  • LINE WORKS

    Channels and members; bot text messages as an approved opt-in.

  • Box

    Search, metadata and scanned fetch into the Project; upload to one folder as an approved opt-in.

Connector documentation

IBM watsonx

Kurahi works alongside an IBM watsonx estate, not instead of it. Every piece uses IBM's published APIs and is off by default.

  • watsonx Orchestrate

    Orchestrate calls Kurahi over A2A, an OpenAPI endpoint or a remote MCP toolkit, and Kurahi can call Orchestrate agents.

  • watsonx.ai

    Use watsonx.ai models as a Kurahi model provider.

  • watsonx.governance

    Governance traces over OpenTelemetry with Langfuse-compatible attributes, for Langfuse or Arize.

  • watsonx.data and Db2

    Read-only, allow-listed queries and Db2 REST services.

IBM watsonx documentation

Open standards

A2A
Agent-to-agent calls with other platforms
MCP
Tools from any MCP server, under the same policy
OIDC
Single sign-on
SAML 2.0
Single sign-on
SCIM 2.0
User and group provisioning
OpenTelemetry
Traces to your observability stack

The same rules for every connector

  • Off by default; an administrator turns each one on
  • Read-only by default; each write is a separate opt-in that waits for a person's approval
  • Tokens live in Kurahi's secret store; audit rows hold ids and counts only
  • Provider text reaches the model only as untrusted data
  • The console shows a connector as active only after a successful live probe

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

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