Bladewell vs Mary UI
Mary UI is a free set of Livewire components styled with daisyUI, installed as a package. Bladewell is free, plain Blade with vanilla JavaScript and Tailwind, and copies its components into your app.
Side by side
Mary UI's column is taken from its own docs, repository and Packagist page as they read on 7 October 2026, each linked as its source. Something out of date? Tell us.
| Topic | Bladewell | Mary UI |
|---|---|---|
| Price and licence | Free, MIT licensed. Every component, no paid tier. | Free, MIT licensed. Source: Price and licence, Mary UI |
| How you install it | php artisan bladewell:add copies each component's Blade, JavaScript and CSS into your app. You edit them like your own code; bladewell:add --installed updates the files you haven't changed and lists the ones you have. The package can stay a dev dependency. | A Composer package your app runs, with each component's markup inside its PHP class. You customise it through daisyUI themes and classes; there's no option to publish the views. Source: How you install it, Mary UI |
| Without Livewire | Yes: plain Blade. The same components work inside Livewire 3 and 4 components too. | Built for Livewire: its installer adds Livewire, and the table, file upload and modal rely on it. Source: Without Livewire, Mary UI |
| JavaScript it brings | One small vanilla JS module per component, bundled by your own Vite build. No Alpine, no Livewire, nothing from a CDN. | Livewire and Alpine. The date picker loads flatpickr from a CDN. Source: JavaScript it brings, Mary UI |
| CSS | Tailwind CSS 4.1 or later, with a theme file of colour tokens. | Tailwind CSS 4 plus daisyUI 5. Source: CSS, Mary UI |
| Laravel and PHP | Laravel 12 or 13, PHP 8.3 or later. | Laravel 10 to 13. Source: Laravel and PHP, Mary UI |
| Date range picker | Yes, free. | Yes: the flatpickr date picker in range mode. Source: Date range picker, Mary UI |
| Data table | Yes: sorting, filters with option counts, row selection and pagination, run by your controller or Livewire component, with the URL kept in step. | Yes: sorting, pagination, selectable and expandable rows, through Livewire. Source: Data table, Mary UI |
| File upload | Yes, including direct upload with progress and retry. | Yes, using Livewire's file uploads. Source: File upload, Mary UI |
| Under a strict CSP | No inline scripts, onclick or style attributes, and no eval: nothing needs 'unsafe-inline' or 'unsafe-eval', and there's no nonce to set up. | Not documented. Its components use Alpine expressions, and Alpine's standard build needs 'unsafe-eval'. Source: Under a strict CSP, Mary UI |
| Accessibility | Keyboard support and ARIA in every component. Every example is checked with axe, light and dark, closed and open, on every change. | Not documented. |
| Latest release | 1.0.0, 9 October 2026. 42 components so far. | 2.9.10, 3 September 2026. Source: Latest release, Mary UI |
Which to pick
Mary UI, if
- Your app is all Livewire, and you like daisyUI's themes.
- You want more components than Bladewell has today.
- You're on Laravel 10 or 11.
Bladewell, if
- Some of your pages are plain Blade, or you'd rather not use Livewire and Alpine at all.
- You want Tailwind without daisyUI, and no scripts from a CDN.
- You want to edit the components' markup directly, and still get updates.
- Your Content Security Policy has no 'unsafe-eval'.
Also compared: Flux, WireUI, Blade UI Kit and BladewindUI.