# Compare Martis > An evidence-based comparison of Laravel admin foundations. Source: https://getmartis.com/compare Compare the trade-offs # Choose the foundation that fits how you ship. A practical decision matrix for agencies—licensing, architecture, extension and long-term handover without invented scores or winner badges. | Criterion | Martis Open foundation | Laravel Nova | Filament | | --- | --- | --- | --- | | CommercialLicenceDetermines whether the foundation can be reused across client projects without recurring product fees. | MIT, with no paid tier | Commercial licence | MIT core | | CommercialCost modelAffects margin and procurement when the same baseline is delivered repeatedly. | No licence or per-project fee | Licence required for eligible production use | Core is free; commercial ecosystem products may be optional | | ArchitectureFrontend stackShapes hiring, component reuse and how product teams extend the client interface. | React + TypeScript | Vue | Livewire + Alpine.js | | ArchitectureUI execution modelChanges where interaction logic lives and how frontend-heavy workflows are built. | Client application backed by explicit APIs | Resource-driven Vue application | Server-driven Livewire components | | ArchitectureLaravel boundaryDefines how clearly backend capabilities and frontend experiences can evolve independently. | Explicit REST boundary with Laravel resources | First-party Laravel product conventions | Laravel and Livewire component boundary | | ProductVisual customisationMatters when the admin must feel like the client’s own product rather than a standard panel. | Design tokens, themes and component overrides | Custom cards, tools and Vue components | Themes, panels and Livewire components | | ProductExtension modelControls how far a team can go beyond the packaged resource experience. | Tools, fields, React components and four-tier overrides | Fields, cards, tools and resource tooling | Resources, widgets, plugins and custom components | | OperationsAccess controlDetermines how much of the security baseline is ready before client-specific policy work begins. | Policies, roles, permissions, SSO, 2FA and impersonation | Laravel policies plus application-level authentication | Laravel policies with panel and plugin options | | OperationsEcosystem postureBalances breadth of existing integrations against control of a smaller, coherent foundation. | Focused foundation with package-owned primitives | Laravel first-party ecosystem | Large community and plugin ecosystem | | Agency deliveryCross-project reuseShows how naturally the product supports a maintained baseline shared across many clients. | Designed explicitly as a reusable agency foundation | Reusable through application conventions and packages | Reusable through plugins, presets and team conventions | | Agency deliveryBest-aligned teamThe best choice usually follows the team’s frontend model and delivery constraints. | Laravel agencies with React capability | Teams wanting an official Laravel product | Teams committed to Livewire and server-driven UI | | Agency deliveryClient handoverAffects long-term ownership, licensing expectations and the skills needed after launch. | Open codebase with no product licence dependency | Ongoing use follows the commercial licence | Open core maintained through Laravel and Livewire skills | Commercial ## Licence Determines whether the foundation can be reused across client projects without recurring product fees. Martis MIT, with no paid tier Nova Commercial licence Filament MIT core Commercial ## Cost model Affects margin and procurement when the same baseline is delivered repeatedly. Martis No licence or per-project fee Nova Licence required for eligible production use Filament Core is free; commercial ecosystem products may be optional Architecture ## Frontend stack Shapes hiring, component reuse and how product teams extend the client interface. Martis React + TypeScript Nova Vue Filament Livewire + Alpine.js Architecture ## UI execution model Changes where interaction logic lives and how frontend-heavy workflows are built. Martis Client application backed by explicit APIs Nova Resource-driven Vue application Filament Server-driven Livewire components Architecture ## Laravel boundary Defines how clearly backend capabilities and frontend experiences can evolve independently. Martis Explicit REST boundary with Laravel resources Nova First-party Laravel product conventions Filament Laravel and Livewire component boundary Product ## Visual customisation Matters when the admin must feel like the client’s own product rather than a standard panel. Martis Design tokens, themes and component overrides Nova Custom cards, tools and Vue components Filament Themes, panels and Livewire components Product ## Extension model Controls how far a team can go beyond the packaged resource experience. Martis Tools, fields, React components and four-tier overrides Nova Fields, cards, tools and resource tooling Filament Resources, widgets, plugins and custom components Operations ## Access control Determines how much of the security baseline is ready before client-specific policy work begins. Martis Policies, roles, permissions, SSO, 2FA and impersonation Nova Laravel policies plus application-level authentication Filament Laravel policies with panel and plugin options Operations ## Ecosystem posture Balances breadth of existing integrations against control of a smaller, coherent foundation. Martis Focused foundation with package-owned primitives Nova Laravel first-party ecosystem Filament Large community and plugin ecosystem Agency delivery ## Cross-project reuse Shows how naturally the product supports a maintained baseline shared across many clients. Martis Designed explicitly as a reusable agency foundation Nova Reusable through application conventions and packages Filament Reusable through plugins, presets and team conventions Agency delivery ## Best-aligned team The best choice usually follows the team’s frontend model and delivery constraints. Martis Laravel agencies with React capability Nova Teams wanting an official Laravel product Filament Teams committed to Livewire and server-driven UI Agency delivery ## Client handover Affects long-term ownership, licensing expectations and the skills needed after launch. Martis Open codebase with no product licence dependency Nova Ongoing use follows the commercial licence Filament Open core maintained through Laravel and Livewire skills Detailed comparison ## Martis vs Nova Two resource-driven approaches with different licensing, frontend and ownership models. Detailed comparison ## Martis vs Filament Two open approaches separated primarily by React versus Livewire and by foundation versus ecosystem posture. Reviewed 24 September 2026. Product capabilities change. [Report a correction](https://getmartis.com/contact?topic=correction) or [discuss your agency’s use case](https://getmartis.com/contact).