Skip to content
Nevela 0.33.1: New: customers get a shop in the mobile app, each sees only their own orders, and an administrator manages people and roles from the phone. Build it in the new drinks-app tutorial.A drinks app on the phone

Nevela, the fullstack framework for Laravel and Next.js

v0.33.1A shop on the phone, and people and roles to run it

The fullstack frameworkfor Laravel and Next.js

Describe a resource once. Nevela writes the table, the API, the validation and the policy in Laravel, and the dashboard screens in Next.js. Laravel stays the only place your rules live.

npm install -g create-nevela
Terminal, anywhere in the appyou write
nevela resource Contact \
  --fields="name:string,
            email:email!,
            phone:tel?,
            status:enum(lead|customer)"
Laravel and Next.jsNevela writes
  1. nevela/resources/contact.jsonDescriptor
  2. app/Models/Contact.phpEloquent model
  3. database/migrations/…_create_contacts_table.phpMigration
  4. app/Http/Requests/Nevela/ContactRequest.phpValidation
  5. app/Http/Resources/Nevela/ContactResource.phpAPI shape
  6. app/Http/Controllers/Api/ContactController.phpREST API
  7. app/Policies/ContactPolicy.phpAuthorization
  8. routes/nevela.phpRoutes
  9. web: resources/contact.resource.tsDashboard descriptor
  10. web: app/dashboard/contacts/page.tsxTable, forms, detail

Edit the descriptor and run nevela generate: the generated blocks follow, and your own code outside them is kept. A new column needs a migration of your own.

Built on
  • Laravel
  • PHP
  • Next.js
  • React
  • TypeScript
  • Tailwind CSS
  • Radix UI
  • Flare dashboard
  • Expo
  • SQLite
  • PostgreSQL
  • MySQL
  • MariaDB

[ How it works ] Layers

One file at the top,
every layer underneath

The descriptor is the only thing you write. Each layer below is real code in your repository, Laravel's and the dashboard's, written from it and kept in step with it.

  1. 01DashboardTable, forms, record page, import and exportweb: app/dashboard/contacts/page.tsx
  2. 02REST APIPaging, sorting, search, filters, bulk createapp/Http/Controllers/Api/ContactController.php
  3. 03PolicyA permission for each action, held through a roleapp/Policies/ContactPolicy.php
  4. 04ValidationA form request, its messages on the right fieldapp/Http/Requests/Nevela/ContactRequest.php
  5. 05DatabaseModel, table, indexes and the migrationdatabase/migrations/…_create_contacts_table.php

[ 01 / 03 ] Describe

Everything a resource needs,
from one description

nevela resource turns a list of fields into a working feature on both sides: the Laravel code that owns the data, and the screens people use to work with it.

[ 02 / 03 ] Generate

One command to start,
one for each thing you add

Each one writes plain, readable files into your project. Change them, or regenerate: Nevela keeps your edits and tells you when it skipped a file.

A new app in one command: a Laravel API and a Next.js dashboard, installed and connected.

Read the reference
nevela new my-app
  • ✔ Creating the Laravel app
  • ✔ Setting up the database
  • ✔ Installing dashboard packages (pnpm)
  • ✔ Created my-app
  • Sign in with admin@example.com / password

And what you write stays small

nevela/resources/product.json
{
"name": "Product",
"icon": "package",
"group": "Catalogue",
"fields": {
"name": { "kind": "string" },
"sku": { "kind": "string", "unique": true },
"price": { "kind": "float", "format": "money" },
"kind": { "kind": "enum", "options": ["stock", "digital"] },
"notes": { "kind": "text", "required": false }
}
}

[ 03 / 03 ] Run

Laravel decides,
the dashboard shows

The Next.js server holds the sign-in token and calls Laravel for everything. The browser never talks to Laravel, and no rule is written twice.

curl -X POST /api/products -d '{"name": "", "sku": "L-1"}'
  • 422 Validation failed.
  •   name: The name field is required.
  •   sku: The sku has already been taken.
  •   price: The price field is required.
  • The same messages appear next to each field in the dashboard form.

Questions

Is it production-ready?

Yes, with one thing to know: it is still 0.x. Sign-in (passwords, passkeys, two-factor, Google and GitHub), roles and permissions, relations and line items, uploads, the trash and the activity log are all there, and every change is tested on SQLite and Postgres, and in a newly created app, before it is released. Being 0.x means a minor version can still change something: the changelog says what and how to deal with it, nevela upgrade keeps the dashboard files you changed, and nevela deploy:check tells you what a server is missing.

What isn't there yet?

Many-to-many relations (make a resource for the link, with a belongsTo to each side), saved table views, and deleting a public file along with its record. The introduction keeps the list.

Can I use it with an app I already have?

Yes. nevela adopt makes a resource of a table you already have, as it is, numbered ids included, and changes nothing in the database. One thing to know first: if the table already soft-deletes, with a deleted_at column, the rows deleted before are in Nevela's trash from the start and are removed for good after 30 days, unless you set trash.days to null first. The guide to an existing app covers the rest.

Where do the rules live?

In Laravel only. Validation is a form request, authorization is a policy, and the dashboard shows what Laravel answers. No rule is written twice.

Can I edit the generated code?

Yes. Generated code lives inside marked blocks; everything outside them is yours and is never touched. If you edit inside a block, Nevela skips that file and tells you instead of overwriting it.

How does it relate to Flare?

The dashboard is Flare's Next.js frontend by Muke Johnbaptist, used under the MIT license. Nevela replaces its database and sign-in layer with calls to Laravel, and generates Flare's resource descriptors from Laravel.

Which databases work?

Any that Laravel supports: SQLite, MySQL, MariaDB, PostgreSQL and SQL Server. The Laravel app ships set up for SQLite, which needs no installation.

[ The maker ] Why Nevela exists

MarkCole MUKISA, the creator of Nevela
started here

One place to change it.
That was the whole idea.

I built Nevela because, every time I started a new application, I found myself wishing the same things were already there.

Authentication. Imports and exports. Permissions. Notifications. APIs. Dashboards. The building blocks that keep showing up in real applications.

I didn’t want to rebuild them every time. I wanted one place where I could enable what I needed, use it, and move on — then turn it off when I didn’t.

So I built the framework I kept wishing I had.

That’s Nevela.

MarkCole MUKISA

Creator of Nevela Framework

Follow him on

Create your app
in the next five minutes