The guide is for CTOs, product owners and operations leads deciding what staff will log in to. It sits under Netbase's web application development work and compares routes by the records they manage, the people who use them and the cost of owning them, not by product rankings.
In this guide
- What is the real difference between a Laravel CMS and a custom admin?
- How do the three main routes compare?
- Which decision criteria settle the choice?
- Can one application use a CMS and a custom admin together?
- How do you choose and prove the route?
- Where AI fits
- What delivery record exists, and what does not
- When is neither a Laravel CMS nor a custom admin right?
- Alternatives and how to select them
- What ownership and upgrade risks should you check?
- Limits of this guide
- Frequently asked questions
- Next step
What is the real difference between a Laravel CMS and a custom admin?
Laravel is a framework, not a content management system: it ships routing, an ORM, queues and authentication, but no page editor or media library for non-technical staff. Whatever admin you need is either adopted from a package or product, or written by your team on top of the framework.
The useful split is by the kind of record the admin manages. Editorial content is pages, posts, media, menus and reusable blocks that editors draft, preview and publish. Business records are orders, vendors, approvals, payouts, bookings and stock levels that follow rules and feed other systems. A Laravel CMS is built for the first kind; a panel builder or a hand-written admin is built for the second.
There are four routes, not two:
- A Laravel-based CMS product. A complete CMS that runs on Laravel, with its own admin, themes and plugins. Botble is one example and Statamic another.
- A CMS toolkit inside your own application. A package that adds editorial screens, blocks and publishing to an application you control; Twill describes itself as an open source CMS toolkit for Laravel.
- A panel builder. A framework that generates admin screens over your own models, such as Filament, which describes itself as an open-source framework for business software with Laravel, or Laravel Nova, a commercial administration panel.
- A hand-written admin. Screens, forms and permissions written with the framework alone, which fits only when no package can carry the workflow.
How do the three main routes compare?
| Criterion | Laravel CMS or CMS toolkit | Panel builder | Hand-written admin |
|---|---|---|---|
| Best at | Pages, media, blocks, drafts and previews for editors | Tables, forms, filters and actions over your own models | Unusual workflows no package models well |
| Editorial features | Shipped: media library, revisions, menus, themes | Added by you: drafts, scheduling and previews need work | Everything is written by you |
| Business rules | Limited to the plugin model; deep rules fight the CMS | Native: rules live in your models and actions | Native, with the most code to own |
| Data model | The CMS owns its tables or files; you extend them | Your schema, unchanged | Your schema, unchanged |
| Upgrade path | Follow the CMS release cycle and its plugins | Follow the panel builder and Laravel | Follow Laravel only |
| Time to a working admin | Shortest when the needs fit what ships | Short for standard record screens | Longest |
| Main risk | Lock-in to the CMS data model and plugin quality | Editorial gaps editors notice late | Maintenance load and inconsistent screens |
Which decision criteria settle the choice?
Score each criterion before any demo; when two rules conflict, the first applicable one wins.
- Record type. If most admin time is spent on pages and media, start from a CMS; if most is spent on orders, approvals or vendors, start from a panel builder.
- Who uses the admin. Marketing editors need previews, revisions and a friendly media library; operations staff need bulk actions, filters and exports. Pick the route built for the larger group.
- Depth of business rules. Commission rules, approval chains and state machines belong in application code; if a CMS would need many custom plugins to hold them, the CMS is the wrong base.
- Integration surface. If the admin must call an ERP, payment service or mobile app API on every change, keep the records in your own schema, where a panel builder or custom code can own the events.
- Permissions. List roles and what each may see and change. A CMS role model fits editor, author and publisher; per-company or per-vendor scopes usually need your own policy layer.
- Upgrade ownership. Every package adds a release cycle you must follow. Count them and name who applies each update.
- Exit cost. Ask how content and records leave the system: database tables you control, flat files, or a proprietary structure that needs an export tool.
Can one application use a CMS and a custom admin together?
Yes, and for many products the split admin is the right answer. The public site's pages, articles and landing blocks live in a CMS or CMS toolkit; the operational records live in a panel or custom admin inside the same Laravel application, with one sign-in and one role model.
The split works when three rules hold: each record type has exactly one owning screen, shared entities such as products or users are edited in one place only, and the role model covers both areas so an editor never sees payout or vendor data. Otherwise the same field gets two editors and the data drifts.
How do you choose and prove the route?
-
List the record types
Write every entity the admin will touch and mark it editorial or business.
-
Map roles to records
For each role, list read, create, change and approve rights per record type.
-
Score the seven criteria
Use the rules above and note which one decides.
-
Build a thin slice
Put one editorial screen and one business screen on the chosen route, with real roles and one integration call.
-
Test with real users
Ask an editor to publish a page with preview and an operator to process a batch of records.
-
Write the upgrade plan
Record each package, its release cycle and who applies updates, before the full build starts.
Where AI fits
AI helps around the admin rather than replacing its rules: drafting content type definitions and form fields from a written requirement, generating test cases per role, summarising a plugin's changelog before an upgrade and flagging user content for a moderation queue. Engineers still review every generated field, permission and migration, and AI tools are chosen per project rather than tied to one vendor.
- In delivered work
Recommendation engine
A recommendation engine delivered for 4over4's online store suggests products from browsing history and previous purchases.
- In delivered work
Content filtering into an admin queue
AI-powered content filtering that flags offensive posts into an admin moderation dashboard, for a classifieds client that is not named.
- Available capability
Admin assistants for editors and operators
An assistant that drafts content or explains a record from data the signed-in role may read; not yet tied to a published case.
What delivery record exists, and what does not
Netbase built RB Marketplace, a multi-vendor marketplace, on Laravel using the Botble Shofy marketplace platform. The admin covers vendor approval, product moderation and commission, payout, campaign and analytics controls, and a customer REST API serves the mobile app: an example of building on an existing Laravel platform and extending its admin with business rules.
For a classifieds marketplace whose founder is not named, Netbase delivered a Laravel backend with REST APIs, paid ad posting, ratings and messaging, and an admin moderation dashboard fed by AI-powered content filtering. For Deyar Printing & Advertising, Netbase scoped and built a bilingual web-to-print platform on a Laravel headless commerce foundation with a production back-office; its ERP and e-invoicing phase is planned, not delivered.
Laravel is among the commerce platforms Netbase has delivered, alongside WooCommerce, Magento 2 and headless commerce. Netbase's published security practices include role-based access control and multi-factor authentication for admin dashboards. Most Netbase projects are delivered on fixed-price contracts agreed after discovery. Netbase does not publish an admin build duration, an editor productivity figure or a cost comparison between routes, and this guide claims none.
When is neither a Laravel CMS nor a custom admin right?
- The content is shared by several front ends and teams outside Laravel. A hosted or Node-based headless CMS may fit better; see the headless CMS options compared.
- You have not modelled the content yet. Run a content modelling workshop first; the model often decides the route.
- The admin is a standard back-office process. Accounting, HR or CRM screens are often better bought as a SaaS product and integrated than rebuilt.
Alternatives and how to select them
| Alternative | Choose it when | Watch for |
|---|---|---|
| WordPress next to the Laravel app | Editors already know it and the site is mostly marketing pages | Two codebases, two update cycles and two security surfaces |
| Hosted headless CMS | Several front ends share content and editors need strong previews | Content lives outside your database; plan the API and exit |
| Back-office SaaS plus integration | The process is standard and not a differentiator | Data sync, role mapping and vendor terms |
| Low-code internal tool builder | Internal staff only, simple CRUD over existing data | Permissions depth and where the logic lives |
What ownership and upgrade risks should you check?
Laravel's support policy gives each major release 18 months of bug fixes and two years of security fixes, with a major release every year. PHP release branches get two years of active support and two more of security fixes only. Every CMS, panel builder and plugin adds its own cycle on top, so a stack is only as current as its slowest package.
Before you sign off a route, check:
- Who applies framework, CMS, panel builder and plugin updates, and how often.
- Whether each plugin you depend on has releases for the current Laravel version.
- Whether the content and records can be exported to tables or files you control.
- Whether role checks run in your own policies, not only in screen visibility.
- Which security requirements the admin is tested against, for example the OWASP Application Security Verification Standard.
Limits of this guide
- It compares routes, not products; feature lists change with each release, so confirm them in each product's documentation.
- It gives no cost or timeline, because both depend on the record types, roles and integrations of each project.
Plan the next step with a Netbase consultant
Frequently asked questions
Filament is a panel builder: it generates admin screens over your own Laravel models. It can host editorial screens, but drafts, scheduling, previews and a media library have to be added, so it suits business records first and content second.
If the site and the application share users, products or data, a Laravel CMS keeps one codebase and one database. WordPress next to Laravel can still fit when editors already know it and the marketing site shares little data with the application.
Yes, if the content sits in tables or files you can export and your business records were never forced into the CMS data model. Plan the exit path at the start, because moving records out of a plugin structure later is the expensive part.
Count where the admin time will go. If most of it is pages and media, start from a CMS; if most is records with rules, start from a panel builder, and add the other side only when a real record type needs it.
Next step
If you are choosing an admin route for a Laravel product, send us your record types and roles and we will reply with a proposal for a short discovery and a thin-slice build plan.
Related services and solutions
Web application development with AI built in where it converts Netbase provides web application development for product and commerce teams that need fast, maintainable web apps and storefront front ends, with AI search, assistants and automation added where they measurably help. Since 2012 Netbase has worked with 500+ businesses across 80 countries; according to its published case studies, PrintLeo's page load improved 35% and 4over4's conversion rose 48%.
Learn More
Multi-vendor marketplace development: vendors, catalog, payouts and AI search on one platform A multi-vendor marketplace is a commerce platform where many independent sellers list, sell and get paid through one storefront. Netbase's marketplace solution covers vendor onboarding, a shared catalog, split payments and payouts, with AI for search, listing enrichment and fraud checks. For an EU fashion-tech marketplace, Netbase's work grew gross merchandise value (GMV) and cut vendor onboarding time.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.