# Martis vs Laravel Nova

> Compare licensing, stack, workflow and extensibility.

Source: https://getmartis.com/compare/nova

Explicit comparison

# Martis vs Laravel Nova

Two resource-driven approaches with different licensing, frontend and ownership models.

Decision snapshot

## Choose Martis for an open React foundation your agency can standardise across clients. Choose Nova when first-party Laravel stewardship and its established commercial model matter more.

Choose Martis when…

## Your agency wants an open React foundation.

- You want an MIT foundation with no paid tier.
- Your frontend team works in React and TypeScript.
- You need a reusable baseline across many client projects.
- You want client handover without a product licence dependency.

Choose Laravel Nova when…

## Its delivery model is closer to your team.

- You prefer an official first-party Laravel product.
- A commercial licence fits your procurement model.
- Your team is already invested in Nova resources and Vue tooling.
- You value Nova’s established Laravel-specific workflow.

What changes in practice

## Ownership and cost

Martis makes the commercial model predictable when the same baseline is reused across many clients.

Martis

MIT licensed with no paid tier or per-project fee.

Nova

A commercial product governed by its production licensing terms.

## Frontend architecture

The practical choice follows the frontend skills your agency wants to compound across projects.

Martis

React and TypeScript with an explicit API boundary.

Nova

A Vue interface integrated with Nova’s resource conventions.

## Custom product work

Martis favours agencies that expect the interface to become a distinctive client product.

Martis

Themes, tools, fields and component overrides are part of the core extension model.

Nova

Custom fields, cards and tools extend the Nova product surface.

## Delivery posture

Nova reduces product selection risk; Martis prioritises reuse, control and an open handover.

Martis

Built to be maintained as an agency-wide starting point.

Nova

Built as a first-party administration product for individual Laravel applications.

Practical questions

## Is Martis a drop-in Nova replacement?

No. Both are resource-driven, but their frontend stacks and extension contracts differ. Treat migration as a product transition, not a package swap.

## Does Martis require a commercial licence?

No. Martis is MIT licensed and has no paid tier.

## Which is better for an agency baseline?

Martis is explicitly designed for repeatable multi-client delivery. Nova may be preferable when clients request the official Laravel product.

Methodology

## A dated comparison, not a winner badge.

This is editorial guidance based on publicly documented product information. Capabilities change and the right choice depends on the team and delivery model.