badaso is an open-source, MIT-licensed Laravel and Vue headless CMS, admin panel, dashboard and CRUD API generator for PHP teams that need to build application backends and admin interfaces without hand-writing them.

What it is

badaso is a PHP application built on the Laravel framework, with a single-page dashboard written in Vue.js and delivered as a progressive web app. It ships under the MIT licence, is maintained by uasoft, and is distributed as source from the GitHub repository uasoft-indonesia/badaso, with the project homepage and live demonstration hosted at badaso.uatech.co.id. The registry entry records 1,255 stars, 227 forks and no open issues, and the topic list covers api, cms, crud, dashboard, generator, graphql, headless, laravel, low-code and ncpd. It presents itself as an API and platform builder rather than a single-purpose content tool.

The concrete problem it solves is the repeated scaffolding work that a Laravel team performs at the start of every project. Rather than writing an admin panel, user and role tables, permission checks, form screens, media handling and a CRUD API by hand, the project generates them: the README lists an advanced CRUD generator, an API generator exposing REST and GraphQL, user, role and permission management, menu management, database migration from within the application, activity logging, a log viewer and daily database backup. In effect it replaces the custom admin layer and bespoke REST API that a Laravel developer would otherwise build per application, while leaving the underlying Laravel stack intact.

Key capabilities

• Advanced CRUD generator that produces application screens and data operations instead of requiring hand-written admin code.
• API generator that exposes application data over both REST API and GraphQL for mobile, desktop and IoT clients.
• Headless operation using JWT authentication and authorisation as the default access mechanism.
• User management plus separate role management and permission management, so each role carries its own access permission set.
• Database management that handles migrations from inside the application, alongside activity logging, a log UI viewer and daily database backup.
• Media manager for local and cloud media, and menu management for application navigation.
• Vue.js dashboard delivered as a PWA, installable natively on Windows, Linux, MacOS, Android and iOS, and able to run offline.

Who uses it and how

• Laravel teams that want an admin panel and data API generated from the framework they already use, rather than adopted alongside a separate stack.
• Product teams connecting mobile, desktop and IoT clients to a backend, since the README frames the API generator as the integration path for those clients.
• Operations and support staff who need to view application logs without opening the server, use the log UI viewer, and rely on daily database backup.
• Teams with intermittent connectivity, because the PWA dashboard works offline and installs natively on desktop and mobile operating systems.
• Long-running projects, which the README targets directly by describing maintenance by uasoft as long-time support.

Getting started

The README directs readers to the official badaso documentation for installation, usage and further detail, and offers a live demo at badaso.uatech.co.id that resets every hour. No package name, Docker image or compose file is given in the README excerpt, so installation follows the project documentation.

How it compares

No list of paid products that badaso replaces is provided in the facts, and no comparable CMS is named there either, so it stands alone in this registry. Its distinguishing position is simply its foundations: it is built on laravel/laravel and vuejs/vue, with vuesax for the interface, so it inherits conventions from those projects rather than introducing a bespoke stack.

When to use it — and when not to

A self-hoster takes on a Laravel application together with its database, media storage locally or in the cloud, and the backup schedule the software runs daily, so the operational surface is that of a normal Laravel deployment. It is a poor fit for teams outside the PHP and Laravel ecosystem, or those who require a documented install command, published package or container image before adopting a tool. The README itself is broad on claims and thin on specifics: it points outward to separate documentation for installation, names no versioned release, and warns that the public demo may throw errors because random visitors test it continuously.