Every entry publishes named capabilities
A marketplace entry belongs to a product and knows that product’s objects, its API and its failure modes. Each entry publishes named capabilities rather than a description of what it might do. A capability is a specific nameable job: investigation, alert dedup, support intake, an ops report, change correlation. An entry commonly publishes several, and the list is the full statement of its scope — if the job you want is not on it, that entry does not do it. Capability is also how two entries are compared across vendors. Two agents that both publish investigation do the same kind of work against different systems, which turns the choice into a question you can answer: which system holds the evidence for the problems you get?What a card tells you
Every card carries the same four sections, so comparing two entries means reading the same fields twice rather than interpreting two different write-ups.
Each entry carries a release badge — Ready, Beta or Design partner — which describes
the entry, not your account. Whether your account has what the entry needs is settled in the
deploy wizard, one credential at a time.
The catalog is organized by problem
Entries are grouped by the operational problem they solve rather than by the vendor that published them, so several products offering the same job against different systems appear together.What stays yours after adoption
A published agent arrives with its behavior validated at the version you adopted — its instructions and its reasoning come from the published image rather than from you. Moving to a newer published version is an adoption rather than an edit, so an entry behaves the same in your account as in the vendor’s. What remains yours is everything around the behavior: the credentials behind its connections, its triggers, its labels, its permissions and the secrets it may resolve at run time, and — for an orchestrator — which specialists it may delegate to. A delegation list behaves as an allowlist: left empty, the orchestrator may use any agent that is online; once you select some, anything left out is refused on every run. If you need behavior no entry has, an agent you run yourself can be connected to KAOP and governed the same way — see Import an agent. The two mix: a published investigator does the reading, and an agent of yours does the part specific to your systems. An entry you host yourself moves to a newer published version through its Helm release — see Upgrade a self-hosted agent. An entry running on Komodor cloud is replaced by adopting the newer version, because its behavior is sealed to the one you adopted.Next steps
Connections
Connect what an entry needs before you adopt it.
The agent page
Where an adopted agent is operated from.