Who is LaravelUi5 for?
LaravelUi5 runs OpenUI5 applications on Laravel, on infrastructure you already operate. It comes in three layers: an OData v4 engine (laravelui5/odata, MIT), Core, which turns PHP declarations into UI5 apps, dashboards and actions (laravelui5/core, BSL 1.1, free for production use), and the SDK, which adds authorization, tenant awareness, settings and a shell (laravelui5/sdk, commercial).
Four kinds of team get the most out of it. Each section below speaks to one of them and points to where that team should start.
SAP partners: UI5 apps without BTP or an SAP backend
Every SAP landscape has work that fits neither drawer. The first drawer is the standard. The second is what gets built around it: extensions inside the system, side-by-side work on BTP. The third drawer holds work that runs on SAP data and cannot live inside SAP, because the people doing it are in a vehicle, at a gate, on a shop floor, or at another company:
- the supplier portal
- the workshop terminal
- visitor registration
- external contractors and work permits
- the field service screen
Each has its own user group, its own data model and its own lifecycle, and each still has to look and behave like the system it draws on. These are the projects a consultancy turns down today, or hands to a web agency, because the usual route prices them above what the application is worth to the customer.
With LaravelUi5 your UI5 developers build them as UI5 applications on a Laravel backend, run them wherever the customer runs web applications, and quote them at a price the customer accepts. Where an app needs SAP data, it reaches it through the services the SAP system releases, typically OData. Where it does not, it keeps a data model of its own.
OpenUI5, not SAPUI5
LaravelUi5 runs on OpenUI5, the Apache 2.0 edition of UI5. The Smart Controls (sap.ui.comp) ship with SAPUI5 only and are not available. For tables on an OData V4 model, OpenUI5 has sap.ui.mdc; our own production applications use sap.ui.mdc.Table against this stack.
Pragmatiqu IT, who build LaravelUi5, work on exactly this seam. The third drawer, and how we work on it →
Laravel agencies: one foundation across client projects
You build business software for clients, project by project, and every project starts from zero. Roles, lists, forms, reports: each client pays again for the same foundation.
LaravelUi5 turns that foundation into something you carry from project to project. In Core, an app, its dashboards, tiles, cards, reports and actions are declared in PHP and registered in a module. A module is a Composer package, so the part you built for one client installs into the next one's Laravel app. The course's last episode installs a complete login application exactly that way. The SDK adds what enterprise clients ask for in week two: role-based authorization with time windows, settings per tenant and per user, a shell with navigation and a command palette, and in-app help.
A typical case: an agency builds an HR dashboard for a manufacturer, with working hours, project budgets and training metrics, role-based access and two languages. The client gets a desktop-first interface that matches its other business software. The agency keeps the modules for the next client.
Start with the Core quickstart, then modules and what the SDK adds.
SaaS founders: a lean enterprise stack for a vertical product
A vertical product has to be tenant-aware from day one: roles and abilities, settings per tenant, relationships to customers and suppliers. None of that is your product, and all of it has to exist before the first customer signs.
The SDK is a package you install to build an enterprise app on Laravel. Platform is the operational layer (a database per tenant routed by domain, customer onboarding, backup and restore) that turns it into a vertical SaaS, and we build it with you.
Your app runs inside its own tenant from the first install, so the step from one customer to many changes how you operate, not how you build. On the way, the SDK gives you the parts a vertical product is judged by: grants with time windows, a business partner model, and settings that resolve per scope.
A typical case: a startup builds an equipment rental product for construction firms, with assets, contracts, billing and analytics per client. The first client runs on a single installation. The second one is the point where Platform comes in.
Start with Core or SDK?, then the SDK's tenant model.
In-house IT: modernising legacy business tools
Two hundred requests, capacity for thirty. The small ones never get their turn: the workshop form, the shift plan, the fuel cost sheet. So they live on in Access databases, Excel workbooks and SharePoint lists that nobody quite understands any more.
LaravelUi5 lets your team rebuild those tools one at a time, as UI5 applications on Laravel. Each one looks and behaves like the others, runs on the servers you already have, and brings no new platform contract through procurement. With the SDK, access follows real roles with validity windows instead of a check in the controller.
A typical case: the IT department of a logistics company replaces its fleet scheduling, shift planning and fuel cost spreadsheets with three UI5 apps on one Laravel backend, and maintains them itself.
If your team runs SAP, much of that backlog is the third drawer described above.
Start with the Core quickstart, then dashboards and the video course.
Where to start
| You are | Read first | Then |
|---|---|---|
| An SAP partner | The third drawer | Core quickstart, for your developers |
| A Laravel agency | Core quickstart | What the SDK adds |
| A SaaS founder | Core or SDK? | Platform |
| In-house IT | Core quickstart | The video course |