Community
LaravelUi5 is built by one person against real applications. That shapes what this page can honestly offer: there is no forum, no Slack, no newsletter. What there is, is a short list of places where a message actually reaches someone.
Where to bring what
| You have | Bring it to |
|---|---|
| A bug in Core, or a feature request | laravelui5/core issues |
| A bug in the OData engine | laravelui5/odata issues |
| A question about something you're building | The video course's demo repository — its Discussions tab is the place for "how do I…" |
| Something you built, or a complaint | Same Discussions tab, or email — the address is in every package's composer.json |
| A question about a licence or an account | The address above; account and billing questions are not public |
Well-described issues are the most valuable thing you can send. A reproduction, the versions involved, and what you expected instead — that is worth more than a patch, for the reason in the next section.
Contributing
This is the honest picture, and it differs per package.
Core is source-available, not open-source. It ships under BSL 1.1: you may use it in production to build applications and services, and each release converts to Apache 2.0 four years after it ships. What you may not do is repackage it as a competing framework, library, SDK or toolkit.
Reading the docs is free. Installing needs a free account: it gives you a named installation and its token for composer require. Core comes from the private registry at packages.pragmatiqu.io, not from Packagist.
A consequence worth stating plainly: github.com/laravelui5/core hosts no source. It is the public home for issues, the changelog and releases. The code itself installs into your vendor/ when you composer require laravelui5/core, so you can read every line — but there is no public tree to fork, and pull requests are not the contribution path for Core. Issues and reproductions are.
laravelui5/odata is MIT and fully public. Source, issues and pull requests all live at github.com/laravelui5/odata. If your contribution is to the OData engine, the ordinary open-source flow applies: fork, branch, PR. Please open an issue first for anything larger than a fix, and follow PSR-12 and the surrounding conventions.
laravelui5/auth is MIT and on Packagist. A self-contained UI5 login application that installs with composer require laravelui5/auth and registers itself. It requires Core, so the host needs Core's registry and token in place first. Source and issues at github.com/pragmatiqu/laravelui5-auth.
What's coming
The roadmap is maintained in public, per package, and it says what is frozen, what is provisional, and how a provisional surface graduates:
- Core roadmap
- Core changelog — release notes, newest first
- OData changelog
Releases are announced on the repositories' Releases feeds. There is no mailing list; if one ever exists, it will be announced there first.
The SDK
Core is free and stays free. Where it stops is authorization at scale — Core is stateless, knows nothing about users or roles, and leaves who may to you. When the answer to that stops being a gate or a policy and becomes a table of roles, organizations and permissions that expire, that layer is the commercial SDK.
That is the whole boundary. Nothing you have built on Core needs it, and nothing about Core changes if you never buy it.
License
Core is licensed under the Business Source License 1.1. Production use for building applications and services is permitted; repackaging as a competing framework, library, SDK or development toolkit is prohibited. Each release converts to Apache 2.0 four years after it ships.
laravelui5/odata and laravelui5/auth are MIT.
Licensed Work © 2026 DMG Beteiligungs GmbH — originally developed by Michael Gerzabek.