---
title: "Kajoo.ai Platform: Governed, Secure DXP Delivery"
description: "Human checkpoints, one secure AI gateway, cost control and DXP-specific agents and skills: the governance, security and infrastructure behind Kajoo.ai."
canonical: "https://kajoo.ai/platform"
type: "WebPage"
source: "https://kajoo.ai/llms.txt"
---

# Kajoo.ai Platform: Governed, Secure DXP Delivery

## Built for DXP work, not general-purpose coding.

_AI agents for DXP delivery_

Kajoo.ai is a team of specialized agents that plan, build and check DXP work, with a human checkpoint at every meaningful step.

[Image: Screenshot of the Kajoo.ai workspace showing a new chat with suggested prompts for a Sitecore migration.]

_The agents_

## A team on the road. You hold the map.

Each agent is a specialist: analysis, architecture, front end, back end, QA and security. They follow a plan you review and stop for your approval at every meaningful step.

### Sentry

**Security**

Hi, I'm Sentry. I guard every project: who can do what, who approved it, and a full record of what happened.

### Scout

**Business Analyst**

Hi, I'm Scout. I turn your goals into clear requirements the whole team can build from.

### Archie

**DX Architect**

Hi, I'm Archie. Before anything is built, I design how your content, components and platform fit together.

### Pixel

**DXP Front-end Developer**

Hi, I'm Pixel. I build the pages and components your visitors see.

### Forge

**DXP Back-end Developer**

Hi, I'm Forge. I build the content models and services that power the pages.

### Specs

**QA Engineer**

Hi, I'm Specs. I test the work against the requirements before it moves on to the next step.

_Platform Overview_

## Built for depth, not just speed.

Kajoo.ai runs on real infrastructure: governed, secure, cost-controlled, and built to fit how your team already works.

### Specialized skills and tools, made for DXP.

General-purpose coding agents weren't built for DXP complexity. This was.

- Tens of specialized skills, and growing
- Custom-built MCP servers for Sitecore XP/XM, SitecoreAI, Figma, Azure DevOps, and GitHub

[Image: Custom-built DXP MCP servers and a Sitecore skill that covers platform topics.]
_A list of custom-built MCP servers for Sitecore XP and XM, SitecoreAI, Figma, Azure DevOps and GitHub, next to a Sitecore skill that covers XP MVC, headless JSS, XM Cloud, SXA, GraphQL and Edge, SPE and content serialization._

### A real project plan, not just generated code.

Kajoo runs delivery the way a DXP project actually needs to run.

- Audits your scope and produces a full project plan: pages, tasks, dependencies, sequencing, following DXP delivery best practices
- Progress reported through a visual interface, phase by phase
- An auto-updating kanban task board that stays current as agents execute, no manual status updates
- Sync your kanban board with the project management tool your team already uses

[Image: A phase-by-phase progress bar and an auto-updating task board with three columns.]
_A progress bar showing phase 2 of 4 (source setup, discovery, code migration, content migration) above a task board with to do, in progress and done columns that updates automatically._

### AI you can trust with your DXP.

Every meaningful step has a human checkpoint. Set it once across your workspace or configure it project by project.

- Every tool call: require approval, run automatically, or always allow
- One approval center for every project in your workspace, not scattered across tools
- A full plan reviewed before any execution starts
- Custom roles and granular permissions
- Every job tracked on an auto-updating task board, with a full audit trail

[Image: A project plan, an approval centre with pending agent questions and a per-tool approval setting.]
_A four-phase migration project plan, an activity feed with pending approvals._

### One platform to vet, not one per AI vendor.

Kajoo acts as a single, secure gateway to every major AI model, so your security team evaluates one platform, not each vendor behind it.

- SOC 2 Type II certification in final stages
- Hosted on Azure, routed through Azure AI Foundry and Cloudflare secure gateway
- Customer data is not used to train or fine-tune models unless you agree in writing
- Full OAuth support
- Route work across a full catalogue of frontier and open-source models, all governed by Kajoo's own privacy and security standards

[Image: A secure AI gateway connecting a model list to model providers through Azure AI Foundry and Cloudflare.]
_A padlock gateway links a list of language models to Anthropic, OpenAI and open-source models, running on Azure AI Foundry behind a Cloudflare gateway._

### Built to be efficient, not just fast.

Speed doesn't have to come at the expense of your token budget.

- Smart semantic caching reduces context window and token consumption
- Smart routing sends each task to the most cost-effective capable model, across a full catalogue of models
- Long-running tasks run as durable scripts on a remote sandbox, not burned on live execution
- Coming soon: batch execution runs jobs in the background, with estimated savings of up to 50% on token costs

[Image: A model catalogue, a semantic cache and automatic routing of tasks to models.]
_A catalogue of language models with tiers, a bar showing context reused from cache, and automatic routing of tasks such as a coverage audit, a validation checklist and a migration plan to different models._

### Extend it. Own it. Make it yours.

Kajoo isn't a fixed toolset, it's a platform you can extend for your own use case.

- Build your own agents
- Build your own skills with the Recipe Builder agent: import from the community or GitHub, upload a skill file, or write one manually
- Connect any remote MCPs
- Package any repeatable workflow into a reusable recipe using the built-in recipe-builder agent

[Image: An agent team, skills, MCP connections and a packaged recipe in one workspace.]
_A workspace with a team of agents including one you create yourself, a skills library, a list of MCP connections including any custom remote MCP, and a recipe that packages the whole workflow._

### No new tool to learn, no walled garden.

Your team keeps using the tools they already have.

- Usable via the Kajoo CLI and MCP server from inside Claude, Copilot, Cursor, or Codex
- MCP Apps served directly into those same tools, no separate UI required

[Image: The Kajoo CLI and an AI assistant using the Kajoo MCP server, with a Kajoo app listing workspaces.]
_A terminal running the Kajoo CLI, an AI assistant asking permission to list workspaces from the Kajoo MCP server, and a Kajoo app inside the assistant showing workspaces and their status._

_Recipes_

## Expandable by design.

Kajoo.ai isn't a fixed set of capabilities, it's a platform built to be extended. A recipe is a pre-built template of specialized agents, skills, and tools, designed to solve one specific DXP use case. Build your own from scratch, start from an existing recipe and customize it, or mix and match pieces from several. Every use case on this page runs on a recipe, and yours can too.

[Image: An example recipe shown as a stack of cards: specialized agents, skills, prompt templates and MCP connections.]
_A recipe card stack labelled Sitecore to Headless recipe with four cards_