Concepts

The three nouns

Actor. A product definition for one AI agent: a repository, a container image, and a config.json. The actor is what the marketplace lists; it does not run by itself. The actor is the class.

Kompanion. One account’s running instance of an actor — a database row plus a pod in that account’s namespace. The kompanion is the instance.

Kreator. A creator who publishes actors on the marketplace. That is you. (The in-app hub for kreators is the “Creator Hub” — that product name stays.)

A simple rule: you build an actor; a customer runs a kompanion; the person who built it is a kreator.

kaboum vs Kaoohi

They are two halves of one pipeline, and the difference matters:

kaboum is the Copier template that produces actors. It generates a complete FastAPI + LangChain microservice: PostgreSQL persistence, Redis caching, health probes, metrics, settings, marketplace metadata. It is not a runnable application — you render it into a new repository and extend it there.
Kaoohi is the platform that runs and sells actors. It pulls your published image, reads the config.json baked inside it, lists the actor in the marketplace, and deploys per-account kompanions.

You work in kaboum’s output; your customers work in Kaoohi.

The marketplace

The marketplace is where actors are listed and deployed. As a kreator you register an actor from its container image: Kaoohi pulls the image, extracts and validates the config.json, and walks it through review — submission, approval, then the actor goes live. Customers then deploy their own kompanions from the listing.

Pricing is set at registration: a pricing model — free, one_time, or subscription — and a price. A free allowance or trial can ride on top of a paid model.

Mesh

The mesh is how one account’s kompanions reach each other.

A group is a set of one account’s kompanions that can talk through the mesh. Groups from different accounts cannot see each other.
The mesh resolver tells each kompanion its peers: which role lives at which endpoint.
Each kompanion plays a mesh role — for example, a “calendar” actor and a “mail” actor in the same group, calling each other’s tools.
A suite is a family of actors built to cooperate in one domain.

An actor opts into the mesh at generation time (the fleet_mesh template option); nothing about mesh participation is accidental.

Bundles

A bundle is a sellable grouping of actors, with each member’s mesh role and dependency recorded. Bundles carry no runtime topology by themselves — the mesh does that — they are a commercial unit: several actors, bought together, wired to cooperate.

Connectors

Connectors are the external services an actor talks to — WhatsApp, n8n, and others. Actors declare which connectors they require or optionally support, and the platform provisions the right credentials per kompanion. In the kreator-sandbox, connectors run in mock mode so you can exercise flows without real accounts.

MCP

MCP (Model Context Protocol) shows up in two directions:

Your actor consumes MCP tools. Set the MCP_SERVERS_JSON environment variable to a JSON mapping of servers, and the actor loads their tools at startup and merges them with its own — no code changes.
Your kompanion is an MCP tool. Every actor can expose itself on the external API edge (https://<platform>/api/v1/k/<ref>/…) over REST and MCP, so end users can drive it from their own AI agents.

Where to go deeper

This guide teaches the path. The reference docs of record live in the repos:

kaboum reference documentation — architecture, API, configuration, extension guide: github.com/allcare/kaboum/tree/main/documentation
kaoohi glossary (normative for every term above): documentation/00-overview/glossary.md in the kaoohi repo
kaoohi actor contract (what the platform requires of every actor): documentation/30-actor-platform/actor-contract.md in the kaoohi repo

Next: ](en/paths/).