The governed interface between your organisation and AI.
Give AI somewhere safe to work.
Connect the AI your team already uses to your company’s knowledge, systems and work. Kroy controls what it can see, what it can do and what it can share.
Use Claude, ChatGPT, Copilot, Codex and other AI tools without rebuilding your business around one provider.
Designed for the AI and systems your business already uses
- Claude
- ChatGPT
- Microsoft Copilot
- Codex
- Microsoft 365
- Xero
- QuickBooks
- GitHub
- Jira
- Salesforce
The problem
Your AI is smart. It still doesn’t know your business.
Your clients are in one system. Documents are in another. Email lives somewhere else. Projects, decisions and work are spread across people and applications.
Connecting each AI tool straight to each system multiplies credentials and risk, and none of them knows who is really asking. Kroy gives authorised AI a governed way to work with all of it.
How Kroy works
Watch the whole system, one step at a time.
-
Things meet at Kroy.
Your business, the people who work in it, and the AI they use. Kroy sits where they meet — and decides what may pass through.
-
Put your business in Kroy.
Clients, projects and decisions become structured, permissioned records — not files pasted into a chat.
-
Connect what lives elsewhere.
Xero, Microsoft 365 and GitHub stay authoritative. Kroy connects to them once and holds the credentials.
-
Know who is asking.
Every request starts with a person Kroy can identify — signed in, with a role and a portfolio.
-
Connect any AI.
Claude connects to Kroy, not to your systems. The AI never needs the keys to your business.
-
Only what they may see.
Priya asks about her clients. Kroy returns what her role and Claude’s delegation allow. Payroll stays out of reach.
-
Actions, with a person in charge.
Claude may create Outlook drafts. Sending an email waits for Priya to approve it.
-
Change AI. Keep the work.
Priya switches to ChatGPT. The decisions, tasks and drafts are still there — because Kroy holds the state, not the conversation.
-
Share the work, not the workspace.
ABC Limited receives a projection of its own record. Internal notes stay behind the boundary.
-
Their AI, your rules.
The client’s director connects his own Claude. It can see what was shared. Asked for internal notes, Kroy refuses.
-
Publish once. Use everywhere.
Approved information flows out to your website, your API and AI-readable profiles — from the same governed source.
-
All of it, through one point.
Every connection, decision and action passes through Kroy, and Kroy records what happened.
Priya · via Claude
- ✓Her clients
- ✓Xero · accounts
- ✓SharePoint · records
- ✕Payroll
Priya · via Claude
- ✓Her clients
- ✓Xero · accounts
- ✓SharePoint · records
- ✕Payroll
See it decide
Run it yourself.
Two short walk-throughs. The first inside a practice; the second with a client using their own AI.
A manager at a London accountancy practice, using Claude
- You
Which March year-end clients still owe us records?
- Kroy checks
- ✓Client list · KroyDB
- ✓Accounts status · Xero
- ✓Records received · SharePoint
- ✕Payroll
- Claude
Eleven clients are still missing records. ABC Limited is missing its March bank statements and fixed asset additions.
- You
Prepare reminders for all eleven.
- Kroy checks
- ✓outlook.draft.create
- ✕outlook.mail.send
- Kroy
✓ Eleven drafts created in Outlook for review. Sending stays with you. Recorded in audit.
John, director of ABC Limited, using his own Claude
- John
What records does my accountant still need from us?
- Kroy checks
- ✓ABC Limited · client projection
- ✓Outstanding requests
- Claude
Two items are outstanding: March bank statements and details of fixed asset additions.
- John
What do their internal notes say about us?
- Kroy checks
- ✕notes.internal.read
- Kroy
✕ Refused by Kroy. Internal notes are not part of what the practice shared with ABC Limited.
Illustrative walk-through with sample data.
Observe
See how AI is actually being used.
Every request through Kroy — allowed, refused or waiting for a person — in one place. Adoption, workflows and risk across the organisation, without turning Kroy into employee surveillance.
Recent AI requests
All connected agents · today
- Claude
xero.invoices.readPriya S. · ABC Limited Allowed - ChatGPT
sharepoint.files.readJames O. · Year-end pack Allowed - Claude
outlook.mail.sendPriya S. · 11 reminders Needs approval - Claude
notes.internal.readGuest · ABC Ltd · ABC Limited Denied - Codex
github.issues.createDev team · kroy-web Allowed
Outlook · send 11 client reminders
- ✓ Signed in as Priya S. (Entra)
- ✓ Claude acting under Priya’s delegation
- ✓ Skill: Prepare Client Reminder
- ! Policy: external email needs a person
How Kroy is built
Principles we don’t bend.
Credentials never reach the AI
Kroy holds the connection to every system. AI tools receive results, not keys.
Least access by default
An AI sees what the person it acts for may see — narrowed further by the Skill in use.
People decide what matters
External communication, publication and financial actions can require a named person to approve.
Everything is recorded
Allowed or refused, every request through Kroy is written to the audit trail.
Independent of any AI provider
Use Claude, ChatGPT, Copilot or Codex. Your state stays yours when you switch.
Honest about what exists
We publish what Kroy does today, and label what is planned. No invented customers or claims.
Kroy + PolicyHQ
Define the rules with PolicyHQ. Put them into practice with Kroy.
Most firms start with a question: should staff put client data into ChatGPT? PolicyHQ helps you write the answer down. Kroy enforces it.
PolicyHQ · AI Use Policy
7.2 AI-generated external communication must be approved by a person before it is sent.
Kroy · Policy
actor = agent
action = external_communication.send
require = human_approval Case Studies
See exactly how Kroy can be used.
Step-by-step implementations: the systems involved, what the AI can see, what it can do, and what Kroy refuses.
Accountancy
Chasing year-end records with Claude, Xero and Outlook
Claude identifies March year-end clients with outstanding records and prepares Outlook drafts for review. Nothing is sent without a person.
Accountancy
A client uses their own Claude with the information you share
The client’s own Claude answers questions about outstanding records from the shared projection. A request for the firm’s internal notes is refused by Kroy.
Technology · Professional services
Letting AI update your website — with a person approving
Claude prepares a change set for the affected public pages. A person approves it, Kroy publishes the projection and the site rebuilds.
Built first for professional services
For firms that hold other people’s information.
Accountants, solicitors, consultants and advisers in London were the first people we built Kroy for. Confidentiality isn’t a feature for them; it’s the job.
- Financial servicesUse AI in a regulated firm — and be able to show exactly what it did.
- ConsultingLet your consultants use AI on client work — one client at a time.
- AccountancyGive your firm’s AI the right client context — without giving it the whole practice.
- LegalGive your lawyers AI that respects the matter wall.
- TechnologyRun several AI agents on real systems — with one set of rules.