- What is badaso/core used for?
- Badaso Core is the Laravel backend of the Badaso headless CMS. It provides an API-first admin panel, a CRUD and API generator, media management, role-based access control, and extensible modules. Teams typically use it to build back-office admin screens and content workflows quickly on top of a relational database. It is best treated as an accelerator for commodity admin and CRUD surface area rather than as a domain architecture.
- Is badaso/core a drop-in Composer library or a full application scaffold?
- It is a Laravel platform-builder and CMS, so you should validate it as a platform or starter-style integration rather than assume it is a drop-in library. Composer-based integration into a Laravel project is technically feasible, but a proof of concept should confirm how it installs and coexists with your application. Decide early whether Badaso is the application shell or a bounded back-office module inside an existing app.
- Which Laravel and PHP versions does Badaso Core support?
- The package is MIT-licensed and has a recent release, but you should verify the supported Laravel and PHP version ranges against the repository's composer.json and release history rather than relying on the overview. Confirm that your target Laravel version is actually tested, not just permitted by constraints. Pin versions and keep a lockfile so future Laravel upgrades are predictable.
- Does Badaso support SSO, OIDC or SAML login and granular RBAC?
- Badaso ships role-based access control and standard Laravel authentication, and authentication hooks are a key integration point to validate. Enterprise SSO protocols such as OIDC or SAML are not something to assume out of the box, so confirm support or plan to bridge them through Laravel auth guards and middleware. Prototype one auth path end to end before committing, and check how granular the permissions model needs to be for your use case.
- What happens to my customized CRUD and API code when I upgrade Badaso?
- Generated CRUD and API code becomes application-owned once you edit it, which creates upgrade friction when Badaso changes its conventions. The practical approach is to isolate generated code, avoid editing it in place where possible, and layer customizations in your own classes. Establish and test the upgrade path from both your current Laravel version and the Badaso release you are pinned to before you depend on it.
- Can Badaso run as an internal admin panel alongside my existing Laravel domain code?
- Yes, the recommended fit is a Laravel monolith or modular monolith where Badaso handles back-office CRUD, admin workflows, and rapid API scaffolding while core domain services and public APIs stay in application-owned code. Integrate it as a bounded back-office module or sidecar admin surface rather than making its conventions the contract for external APIs. Start with one admin module, one API resource, one auth path, and one media workflow as an isolated pilot.
- Does Badaso support multi-tenancy, audit logging and queues?
- These are areas the technical evaluation flags as validation items rather than guaranteed capabilities. Multi-tenancy, granular authorization, audit logging, and event-driven workflows are exactly where an opinionated CMS can constrain a complex or regulated platform. Confirm queue, cache, and object storage behavior in a spike, and do not migrate core transactional flows until authorization, audit, and rollback behavior are proven.
- How do I install badaso/core and what frontend build requirements does it have?
- Installation is via Composer into a Laravel project, but confirm whether the workflow expects a fresh starter application or an existing app before you begin. Badaso pairs a Laravel backend with a Vue admin frontend, so verify whether the admin stack introduces Node or asset-build requirements in your deployment pipeline. Check PHP and Laravel constraints, the Composer dependency graph, database version, and deployment target during a short proof of concept.
- Is Badaso actively maintained and are there production references?
- The project has roughly 1.2k GitHub stars and a recent release, which signals community interest, but zero Packagist dependents means there is little evidence of downstream package-level adoption. Treat production references, maintainer responsiveness, and the support model as explicit validation items before relying on it for critical back-office functionality. The ecosystem appears small and likely community-supported, so budget for a fork-and-maintain contingency.
- Is Badaso a good fit for a complex, API-first, multi-tenant platform?
- It is a weaker fit as the foundation for a complex, API-first, multi-tenant, or highly regulated domain platform unless your team explicitly accepts its opinionated conventions. It is strongest as an accelerator for admin panels, CRUD screens, and internal back-office APIs over relational data in an existing Laravel stack. Migration away is feasible if you keep domain logic and public APIs in your own code, but plan the exit path and version pinning from day one.