Requirements & Installation

SeviaFlow 0.1.x-dev is pre-release software. Core, UI, API, Framework and DevTools are licensed under MIT, including commercial use and redistribution with the license notice. The API package is free and requires no licensing or activation dependency.

Supported beta runtimes

Laravel 12 requires PHP 8.2+; Laravel 13 requires PHP 8.3+. UI is tested with Livewire 3 and 4. Laravel 11 is outside the beta support scope because its security support ended on March 12, 2026. Package tests use SQLite; Northstar integration and browser tests use MariaDB 10.11. PostgreSQL remains unverified.

License and support

MIT usage rights apply to the five free packages; retain the copyright and license notice when using or redistributing them. Pre-release status does not include a production support SLA.

• Free beta edition: Core, UI, API, Framework and DevTools do not require a paid license or activation. They use MIT; retain its copyright and license notice.
• Pre-release: the examples use 0.1.x-dev; they do not promise a stable tag or a support SLA.

Install Core

composer require seviaflow/core:^0.1@dev

Core publishes config/seviaflow.php and loads Core migrations for permissions and workflow activity storage.

php artisan vendor:publish --tag=seviaflow-config
php artisan vendor:publish --tag=seviaflow-migrations
php artisan migrate

Core does not add UI or API routes.

Install UI (Core + UI technical profile)

composer require seviaflow/ui:^0.1@dev

php artisan vendor:publish --tag=seviaflow-ui-config
php artisan vendor:publish --tag=seviaflow-ui-migrations
php artisan vendor:publish --tag=seviaflow-ui-assets
php artisan migrate

The UI defaults to /admin, route names prefixed with seviaflow., and admin middleware web + auth.

Install API

API is free and does not require a project token, purchase or licensing adapter. Install it from Composer, then publish its configuration:

composer require seviaflow/api:^0.1@dev
php artisan vendor:publish --tag=seviaflow-api-config

The default API middleware remains api + auth:sanctum; install and configure Sanctum in the host or select another real authentication guard. A free API is still authenticated: it does not expose application data anonymously. OpenAPI and docs remain authenticated.

On upgrade, remove the obsolete licensing block and SEVIAFLOW_API_LICENSE_ENFORCE setting, then clear host config and route caches. The old seviaflow.api.license alias is a compatibility pass-through. Remove the licensing package only when no other installed package requires it.

Install DevTools

composer require --dev seviaflow/devtools:^0.1@dev
php artisan seviaflow:doctor
php artisan seviaflow:status

The DevTools installer can publish package artifacts it finds:

php artisan seviaflow:install --with-stubs
php artisan seviaflow:install --migrate

Full Runtime

composer require seviaflow/framework:^0.1@dev

Use the framework metapackage when the app should receive Core + UI + API together. It is free and has no licensing or activation requirement. DevTools remains a development dependency.

Configure a basic Resource

After installing the package profile, define a Resource in the host application and opt into only the surfaces it needs. The complete runnable example is Your First Resource.

final class CustomerResource extends Resource
{
    protected static string $model = Customer::class;

    public static function form(Form $form): Form
    {
        return $form->fields([
            TextField::make('name')->required(),
        ]);
    }
}

UI and API exposure remain explicit host decisions. Configure the Core admin gate and the host authentication/policy layer before exposing records.

Remove a package without deleting data

composer remove removes package code; it does not drop application tables. Before removal, disable the package routes and workers, export or retain data required by the application, and remove published config/assets only after the host no longer references them.

composer remove seviaflow/ui
# remove only the package-owned migration files from your application if they are no longer needed
# do not run migrate:fresh or drop shared tables as part of package removal

Schema rollback and data deletion are application-owner operations. They require a backup and an explicit, reviewed migration plan; package uninstallation never assumes permission to destroy business data.