Choosing Packages

Choose packages by runtime surface, not by repository name. These profiles describe dependencies. Core, UI, API, DevTools and Framework use MIT; see Requirements & Installation for supported runtimes and setup commands.

Core-only Applications

Use seviaflow/core when you want Resources, forms, tables, filters, relations, workflows, actions, events, permissions and CSV import/export primitives without a bundled UI or API.

Operator UI Applications

Add seviaflow/ui when operators need browser screens for resources. UI provides Livewire resource index/create/edit/show pages, dashboard, navigation, saved views, auth/profile screens and role management.

UI depends on Core and does not require API.

Headless API Applications

Add seviaflow/api when integrations need REST endpoints, flow transition endpoints or OpenAPI schema output.

API depends on Core only, does not require UI or a licensing adapter, and belongs to the free edition. API is part of the free edition.

Full Runtime Applications

Use seviaflow/framework when a new app should install Core, UI and API together. Core is still the shared contract, while UI and API are adapters.

Framework is the free Core + UI + API entry point. It requires no paid module or licensing adapter.

Development Tooling

Add seviaflow/devtools in require-dev for diagnostics, model discovery, generators and cache commands.

Install the package set

Choose one runtime profile below. UI, API and Framework pull in Core automatically; add DevTools separately when you need local diagnostics and generators.

# Choose one runtime package
composer require seviaflow/core:^0.1@dev
composer require seviaflow/ui:^0.1@dev
composer require seviaflow/api:^0.1@dev
composer require seviaflow/framework:^0.1@dev

# Optional developer tooling
composer require --dev seviaflow/devtools:^0.1@dev

Run the line for your chosen profile rather than installing all four. Then follow Requirements & Installation to publish the configuration or migrations required by that package set.