# Plugin catalog

A Fayz app is a composition of plugins. Each plugin is a `@fayz-ai/*` package that declares what it is — navigation, routes, widgets, data — and the core resolves it all at runtime. But before the raw catalog, the practical question is a different one: **what product do you want to build?** Start there and the right set of plugins falls into place on its own.

## What do you want to build?

Each path below is a product type Fayz assembles today. The card carries the promise, the scaffold command that opens the project, and the plugins that make up the base.

{% product-types /%}

{% callout type="info" %}
In practice the commands use `npx` (e.g. `npx fayz create admin my-company`). Online course and website are still early surfaces (preview) — the status badges on each card tell the truth, and the [headless path](/en/docs/apps/headless) covers the website bundles (blog, payments) already published.
{% /callout %}

## Full catalog

Every published plugin, grouped by product type, straight from the SDK metadata: status, capability and version of each package. The same plugin can appear in more than one group (`plugin-inventory`, for example, serves management, e-commerce and food). Click any card to see the specs — each one carries the plugin's data model, AI tools and connectors (the contract an AI reads as a skill).

{% plugin-grid /%}

For the external providers an app can connect to — payments, scheduling, analytics, channels — see the [Integrations](/en/docs/plugins/integrations) catalog.