# Products (https://upapi.io/docs/platform/products)



A product is a named bundle of operations. It is an organizational tool: when a
workflow reaches for the same six operations every time, a product keeps them
together instead of leaving you to rediscover the set.

Products are created and managed at
[Dashboard → Products](https://app.upapi.io/dashboard/products). How many you
may create depends on your [plan](https://upapi.io/docs/plans).

## What a product does not change [#what-a-product-does-not-change]

Bundling is presentational. It does not affect the call path, authentication,
metering or limits:

* You still call each operation at its own slug.
* Cost is still per call, at each operation's own
  [unit weight](https://upapi.io/docs/rate-limits).
* Nothing about a product grants or removes access to an operation.

<Callout title="Products are private">
  Every product is private to the organization that created it, and there is no control today for
  publishing one. If you need a public offering, that is not a feature that exists yet — do not
  design around it.
</Callout>

## What controls visibility [#what-controls-visibility]

An operation's reach is set by its **publish targets**, not by any product it
belongs to. An operation with no publish targets is hidden from the marketplace,
the docs and the OpenAPI document, and returns `404 NOT_FOUND` at the gateway —
the same response as a slug that was never created, so its existence is not
disclosed.

This is why an operation you can see in one place and not another is a publishing
question rather than a permissions one. See [Errors](https://upapi.io/docs/errors#404-does-not-distinguish-missing-from-not-yours).