Connect

Connect your business once.

  1. Your systems, scattered.

    Xero, Outlook, GitHub, SharePoint — each with its own credentials and its own idea of who may do what.

  2. Connect each one to Kroy.

    A Connector links each system to Kroy once. Kroy holds the credentials; nothing else needs them.

  3. Signals begin to travel.

    Kroy can now read and act in those systems — but only on behalf of a request it has authorised.

  4. Use it safely with any AI.

    AI tools and people connect on the other side. They reach your systems through Kroy, never directly.

Kroy
Xero
Outlook
GitHub
SharePoint
Claude
ChatGPT
Your team
Kroy
Xero
Outlook
GitHub
SharePoint
Claude
ChatGPT
Your team
Business systems connecting to Kroy, with AI on the opposite side. Your systems, scattered.. Connect each one to Kroy.. Signals begin to travel.. Use it safely with any AI..

What a Connector is

A Connector tells Kroy how to communicate with another system. It defines:

  • authentication;
  • resources and their schemas;
  • actions, such as outlook.draft.create;
  • events and webhooks;
  • health and rate limits;
  • the permissions each action requires.

Why connect through Kroy

Connecting each AI tool directly to each business system multiplies credentials, permissions and risk. Every new AI means another set of keys to your business.

With Kroy, systems connect once. AI tools connect to Kroy. Kroy decides, on every request, whether an action is allowed.

Who builds Connectors

LabelMeaning
Kroy BuiltBuilt and maintained by Kroy.
Kroy VerifiedBuilt by a third party and reviewed against Kroy requirements.
CommunityCommunity-maintained, with clear disclosure.
PrivateAvailable only within one organisation — for proprietary systems.

Private Connectors mean an organisation does not need to wait for Kroy to support an internal ERP or database.

Case Studies using Connect

Accountancy

AI-assisted bookkeeping review in Xero

Claude reviews the month’s bookkeeping and proposes a change set of corrections. The bookkeeper approves the ones they agree with and Kroy applies only those. Deletions and bank detail changes are refused.

ClaudeXero

Accountancy

Claude + Xero through Kroy

Claude answers questions using authorised Xero data and prepares drafts — without holding Xero credentials or reaching data the user cannot see.

ClaudeXero

Technology

Claude Code and Codex working from shared state

Claude Code records a task’s progress and design decisions in Kroy State. Codex picks up the task from that state on another developer’s machine. Both open pull requests; neither can merge to the main branch or read production secrets.

Claude CodeCodexGitHubJira

Technology

A release workflow with deployment approval

Claude drafts release notes, creates a draft release and deploys to staging. Production deployment waits for the release manager’s approval, and Kroy refuses any attempt to skip it.

ClaudeGitHub

Professional services · Technology

Updating Salesforce after a client meeting with Claude

Claude logs the meeting, creates follow-up tasks and drafts the follow-up email. An opportunity stage change goes to the account manager’s manager for approval. Deletion, reassignment and bulk export are refused.

ClaudeSalesforceOutlook

Technology

A private ERP Connector with a customer-facing order status Skill

A developer builds a private Kroy Connector for the ERP and a Check Order Status Skill. Staff AI and a customer’s own AI can both invoke it; each customer sees only their own orders.

Microsoft CopilotClaudeChatGPTPrivate ERP connector