Book a demo Sign up

Project management and AI search for IT services and MSPs.

Run delivery, support queues, change and engagements in Kroolo Work. Ask across runbooks, tickets, architecture docs and contracts in Kroolo Search, with every answer cited.

Delivery and supportTicket intelligenceCited answers
Ask KrooloKroolo Search
Which client engagements have SLA breaches this week?
Answer
4 engagements have SLA breaches this week. 3 are P2 tickets older than the response target and 1 is a P1 awaiting a vendor 1. Delivery managers were notified 2.
1Ticket queue2#delivery-ops
Engagement healthKroolo Work
Cloud migration
On track
Managed service
SLA watch
Security upgrade
Behind
The problem

Delivery knowledge lives in people, tickets and wikis.

58%
of the workday goes to work about work, such as chasing status and switching apps.
Asana, Anatomy of Work Index 2022
30%
of work time is spent searching for information.
Today · scattered
Engagements
Runbooks
Incidents
Handover
Change
With Kroolo · one workspace
EngagementsOne plan per engagement with milestones and owners
RunbooksAsk in plain language, get the cited runbook
IncidentsTasks, timeline and history in one place
HandoverAsk the full history of a client or system
ChangeChange requests with approvers and a record
The platform

One platform runs the work. One finds the answers.

Kroolo Work
Plan, execute and deliver
Sprint progress
Engagements and migrations as
Change and release requests
Incident and problem follow-up
Client onboarding and offboarding
Dashboards
One set of
permissions
Kroolo Search
Ask anything, then act on it
What is blocking this quarter?
3 sourcesCitedPermission-aware
Ask in plain language
Cited answers
Permissions before AI
50+ connectors
Action agents
Use cases

Where Kroolo goes to work.

Six workflows IT services teams run on Kroolo Work and Kroolo Search.

Delivery
Migrations with milestones, owners and risks

Plan discovery, build, cutover and handover as one project, with dependencies and client sign-offs visible.

Milestones: Track against contract dates.
Dependencies: See what blocks cutover.
Client sign-offs: Record every approval.
EngagementsLive
Active
14
At risk
3
Late
1
Cloud migration
On track
Data platform
Watch
Security upgrade
Behind
Kroolo Work · the work layer

How delivery, change and support work moves.

Four workflows IT services teams run in Kroolo Work, with owners and approvals at each step.

Client engagement delivery
DiscoveryPlanBuildCutoverHandover
Automated: Milestones and dependencies come from a delivery template, with sign-offs tracked.
Result: One plan per engagement that the client can follow.
Change and release
RequestRisk reviewApproveImplementVerify
Automated: Requests route to approvers by risk and system, with a record.
Result: Fewer failed changes and a clean audit trail.
Incident follow-up
DetectRespondReviewActionsClose
Automated: Post-incident actions become tasks with owners and dates.
Result: Repeat incidents reduced and tracked to closure.
Client onboarding
Kick-offAccessToolingTrainingLive
Automated: Access, tooling and training tasks are created per client from a template.
Result: New clients live faster, with nothing missed.
Kroolo Search · the data layer

Questions your data answers, with the source attached.

Engineers, managers and account leads ask across tickets, docs and contracts and get a cited answer.

Where the data lives
Jira
Confluence
ServiceNow
GitHub
GitLab
Slack
Kroolo Search
One index across runbooks, tickets, architecture docs, contracts and chat. Permissions enforced at retrieval.
ConnectorsKnowledge graphACLs
What teams get
Cited answers
Every answer links to its source
AI agents
Act within the asker's permissions
Kroolo Work
Findings become tasks with owners
How do we fail over the payments database in the EU region?
Answer
Promote the standby replica, update the connection string in the secrets store and run the verification checklist 1. The on-call lead approves before traffic shifts 2.
1Payments DR runbook2Change policy
What incidents did client Acme have in the last 90 days?
Answer
Acme had 11 incidents, 6 related to authentication timeouts. The most common fix was a token refresh configuration change 12.
1Acme tickets2Post-incident reviews
What does the Acme contract say about response times?
Answer
P1 incidents require a 15-minute response and a four-hour target to restore. Credits apply after two breaches in a quarter 1.
1Acme MSA
Which engagements depend on the vendor delay?
Answer
Two engagements depend on the vendor hardware delivery, the data centre move and the branch rollout 12.
1Delivery board2Vendor update
Work meets data

A recurring incident, from pattern to permanent fix.

Search finds the pattern, Work owns the fix, and the runbook is updated for everyone.

1Kroolo Search
Search finds the pattern

An engineer asks about recent incidents for a client. Kroolo shows six auth timeouts and cites the tickets.

2Kroolo Work
Work opens a problem record

A problem task is created with an owner, due date and linked incidents.

3AI agent
Agent drafts the fix

The incident agent drafts the config change and runbook update for review.

4Approver
Change approved

The change is approved and implemented through the change board.

5Kroolo Search
Search serves the next engineer

Next time, ask the runbook and get the new fix, cited.

The result: Repeat incidents closed out, with the fix findable by every engineer.
AI agents

Meet your new AI team.

Use pre-built agents or build your own with the no-code agent builder. Each one works inside your permissions.

Incident agent

Summarises incidents and drafts post-incident actions.

Drafted 6 action plans
Runbook agent

Answers how-to questions from approved runbooks, with citations.

Answered 34 questions
Change agent

Checks change requests for missing approvals.

Flagged 5 changes
Reporting agent

Prepares weekly client status reports.

8 reports ready
Meet the agents
Roles

Built for every role in IT delivery.

From the delivery director to the engineer on call.

Leadership
Every engagement, one view

See delivery health, SLA risk and utilisation across all clients.

Portfolio view: All engagements in one place.
SLA risk: Flag breaches before they happen.
Utilisation: See capacity by team.
Delivery portfolioLive
Engagements
14
At risk
3
SLA breaches
1
Delivery
On track
SLA
Healthy
Utilisation
High
Integrations

Connects to the tools your delivery teams already run on.

50+ native integrations across ticketing, source control, documentation and communication.

JiraConfluenceServiceNowGitHubGitLabSlackMicrosoft TeamsZendeskJira Service ManagementAzure BoardsGoogle DriveSharePointJiraConfluenceServiceNowGitHubGitLabSlackMicrosoft TeamsZendeskJira Service ManagementAzure BoardsGoogle DriveSharePoint
See all integrations
Security and governance

Secure by design. Governed by default.

Your proprietary data stays your own. Agents operate within your workspace permissions, and every action is traceable.

ACL before AI

Permissions are enforced at retrieval, so people only get answers from what they already have access to.

No training on your data

Your content is never used to train models. Tenants are isolated.

Cited and auditable

Every answer shows its sources, and activity is audited by default.

Deploy where you need it

Run on AWS, Azure, GCP or on-prem, with SSO through Azure or Google.

SOC 2ISO 27001GDPRNIST AI RMFISO/IEC 42001EU AI Act
Read the Responsible AI Framework

FAQs on Kroolo for IT Services

Can Kroolo keep one client's documents separate from another's?
Yes. Kroolo Search enforces access control lists and role-based access at retrieval, so the AI only sees what the person asking is already allowed to see. Answers cite their sources.
Is our data used to train models?
No. Your content is not used to train models, and each tenant is isolated.
Where can Kroolo run?
Kroolo cloud runs on AWS, with US East as the primary region. You can also run it on Azure, GCP or on-prem, with SSO through Azure or Google.
How long does it take to go live?
Kroolo Search connects to the systems you already use through 50+ native connectors.
Can we bring our own model?
Yes. Kroolo supports bring-your-own-model and key, and routes between Claude, Gemini and GPT.

Run delivery with the full picture.

Plans, tickets and runbooks in one place, so every engagement starts with the context it needs.

Explore

Kroolo for other industries

All industries