Your Kastel's vocabulary, without the jargon.

Your company's structured memory: its organisation, its processes, its responsibilities, its clients, its projects, the history of its decisions. Kastel builds it, maintains it, and exposes it to the AIs you plug in.

It's versioned text files that remain your single source of truth - never a proprietary format to break.

Kastel's product category: the living map of who knows what and who decides what at your company, structured and governed, exposed to the AI of your choice. Kastel doesn't run any model itself - it's neither an inference platform nor a runtime.

The differentiator isn't the word: it's that you don't need a data team to build it, or to maintain it.

A standardised socket an AI tool plugs into to reach your company's context and tools. Kastel is an MCP server: it publishes your Kastel on that socket, and any compatible AI - Claude, ChatGPT, Cowork, a model you host yourself - connects to it.

Like a standard wall outlet: you swap the appliance without rewiring the house. Switching AI becomes a gesture, not a project.

You plug in your own AI keys, or a model that runs on your own infrastructure. It's mandatory, including in managed hosting: Kastel never resells inference and never takes a margin on it.

Like bringing your own fuel: Kastel is the vehicle, not the pump. The AI bill stays yours.

One rule drives two things: who is allowed to see what, and which sensitive action must be submitted for approval before it runs. You set it once, by role, and every connected AI follows it: you decide what each AI is allowed to see.

It's your company's chart of responsibilities, made executable by the machine.

Control over what AIs are allowed to do, not just to see. A sensitive action goes through human approval, which signs off the exact effect - never a vague intent - and every action is logged for audit.

AIs work fast; some decisions still require a person's sign-off.

Self-host: you run Kastel on your own infrastructure, and the full core, Kastel Core, is free there forever. Managed: Kastel hosts and operates an isolated instance for you, in Europe - never an engine shared across companies.

Like cooking at home, or ordering delivery: the preparation changes, and so does the menu - self-hosted Core stays complete for a team that governs itself, managed adds multi-person collaboration and enterprise sign-on. Hosting by Kastel is always paid; free self-host is your trial path.

You own your data, your context and your infrastructure: you can host everything yourself, export everything, switch AI whenever you want. Sovereignty is data ownership plus self-host - it doesn't require the engine's code to be open.

Like owning a house and everything in it, without holding the blueprints of the factory that made the bricks.