Laravel data framework

Model once.
Flow everywhere.

SeviaFlow turns Laravel application data into operator-ready UI, REST APIs, OpenAPI, workflows and integrations while your code remains the source of truth.

Core-first resourcesOptional UIOptional API
YOUR SOURCE OF TRUTHApplication modelResources · relations · rules
▦
INTERFACEOperator UI
↗
APIREST API
↯
AUTOMATEWorkflows
The idea

Your data is the heart of the system.
Everything else should flow from it.

Most business applications repeat the same work across internal tools, APIs, permissions, exports and process logic. SeviaFlow centralizes resource definitions and lets UI/API surfaces grow from one consistent foundation.

What SeviaFlow does

From Eloquent model to working application surface.

Define resources, forms, tables, filters, relations, actions and API exposure in explicit PHP. Install only the packages needed for each surface, and use the free API without a separate activation.

01
◉

Data-first resources

Keep the model, relationships, validation and business rules at the center. SeviaFlow works around your Laravel application instead of hiding it behind a visual builder.

CustomerResource.php
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(),
            EmailField::make('email')->required(),
        ]);
    }
}
02
▦

Operator-ready UI

Add seviaflow/ui for Livewire resource index, create, edit and show pages, dashboards, saved views, auth screens and role management.

03
{ }

APIs without duplication

Add seviaflow/api to expose resources through REST endpoints and OpenAPI without repeating field visibility and validation decisions.

04
↯

Actions & workflows

Turn business operations into explicit, testable actions and state transitions that can run from UI and API surfaces.

05
◎

Permissions by design

Core authorization combines optional SeviaFlow role permissions with Laravel model policies, so access control does not live only in a frontend.

Architecture

One core. Many surfaces.

Core defines resource behavior. UI and API are optional adapters over the same contract. The framework package installs Core, UI and API together when you want the full runtime.

YOUR APPLICATION Models · Rules · Policies · Relations
SEVIAFLOW CORE
▦Operator UIseviaflow/ui
↗REST APIseviaflow/api
↯ActionsCore
◇WorkflowsCore
Why SeviaFlow

Fast to start.
Hard to outgrow.

Low-code tools are fast until your application becomes real. Traditional frameworks give you control, but make you rebuild the same operational infrastructure. SeviaFlow is designed for the space between those extremes.

Read the design rationale →
SpeedControlScale
Low-code●●●●○○●○○
Classic framework●○○●●●●●●
SeviaFlow●●●●●●●●●
terminal

$ composer require seviaflow/core:^0.1@dev

Installing SeviaFlow Core...

✓ Core installed

✓ Resource engine ready

✓ No UI or API dependency added

$ composer require seviaflow/ui:^0.1@dev seviaflow/api:^0.1@dev

✓ Operator UI package available

✓ REST API package available

$

Developer experience

Your code stays yours.

SeviaFlow favors explicit PHP, familiar Laravel conventions and testable building blocks. Start with Core, then add the UI or API only when the application needs those surfaces.

  • ✓ No proprietary data model
  • ✓ No business logic trapped in a UI
  • ✓ Composable resources and actions
  • ✓ Built for long-lived business systems
01

Source of truth

Your Laravel domain remains authoritative. SeviaFlow derives capabilities from it rather than competing with it.

02

Progressive power

Simple resources stay simple. Tables, filters, actions, workflows and API exposure appear only where needed.

03

Package boundaries

Core has no Livewire or API route dependency. UI and API adapters depend on Core, not the other way around.

Included in the free edition

REST API and OpenAPI, without a paid activation.

The SeviaFlow API package is free. It adds no license or subscription requirement; your Laravel authentication and policies continue to control access to application data.

Read API documentation →
SeviaFlow

Build around your data.
Let everything else flow.

Start with the current 0.1 pre-release documentation and the verified playground resource example.