Skip to main content
Fluid supports two Widget Package lifecycles. Both use the Widget Worker SDK, but their owners, configuration, and publication commands differ. Both models define package metadata through DefineWidgetPackageOptions.

​
Choose a company package

Use a company package when the widgets belong to one company’s portal development project and should publish through that portal’s widget catalog.

Company package quickstart

Create and publish widgets from a portal project.

​
Choose a Droplet package

Use a standalone package when the package belongs to an existing Droplet and needs its own source repository and release lifecycle.

Droplet package quickstart

Link a standalone project to a Droplet and publish an immutable package version.

​
Keep the lifecycles separate

Do not copy configuration between the two project types. A standalone fluid.widget.config.ts does not configure a company package, and fluid portal deploy does not publish a Droplet package. Use a server application instead of either package model when you need secrets, OAuth, private APIs, webhooks, or background work.