The app catalog

Catalog in the account menu opens a list of ready-made apps: expenses, helpdesk, fleet, and more. Each entry is a description of what the app knows and does.

What an entry is, and is not

It is not an installer. Nothing is copied into your workspace when you open one.

It is a brief. Open an entry, read what it covers, and press Build with Extend: the description goes into an Extend conversation as the starting request, and the agent builds it in your workspace — with your tables, under your rules, in your language.

Which means you can argue with it before it exists: "We do not need the approval step", "Call it Fuhrpark, and add the inspection date".

Bundles

Some entries are bundles: several apps that belong together for one line of business. Same mechanism, more at once.

Why not just install it?

Because a copied app is somebody else's app. The version you get through Extend is fitted to what your company calls things and to the data you already have — the customer it points at is your customer table, not an imported list.

It also means an entry cannot break anything by existing. Nothing changes until you build.

Where the catalog comes from

kyte maintains it. New entries appear without an update to the app; the list is fetched, not shipped.