Nevela, the fullstack framework for Laravel and Next.js
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-nevelanevela new my-appnevela resource Product --fields="name:string, sku:string!, price:money"nevela seed Product --count=1000nevela upgradenevela resource Contact \
--fields="name:string,
email:email!,
phone:tel?,
status:enum(lead|customer)"- nevela/resources/contact.jsonDescriptor
- app/Models/Contact.phpEloquent model
- database/migrations/…_create_contacts_table.phpMigration
- app/Http/Requests/Nevela/ContactRequest.phpValidation
- app/Http/Resources/Nevela/ContactResource.phpAPI shape
- app/Http/Controllers/Api/ContactController.phpREST API
- app/Policies/ContactPolicy.phpAuthorization
- routes/nevela.phpRoutes
- web: resources/contact.resource.tsDashboard descriptor
- 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.
- 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.
- 01DashboardTable, forms, record page, import and export
web: app/dashboard/contacts/page.tsx - 02REST APIPaging, sorting, search, filters, bulk create
app/Http/Controllers/Api/ContactController.php - 03PolicyA permission for each action, held through a role
app/Policies/ContactPolicy.php - 04ValidationA form request, its messages on the right field
app/Http/Requests/Nevela/ContactRequest.php - 05DatabaseModel, table, indexes and the migration
database/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.
- REST APIList, read, create, update and delete for every resource, with paging, sorting, search, filters and bulk create.
- ValidationA Laravel form request per resource. Its messages show next to the right field in the dashboard.
- DashboardTables, charts, forms, detail pages, import and export for every resource, from its descriptor.
- Roles and permissionsA permission per resource and action, roles to group them, and a Users screen. Laravel decides; the dashboard shows the answer.
- Sign-inPasswords, passkeys, two-factor, emailed links and codes, Google and GitHub. The browser never sees the token.
- RelationshipsbelongsTo between resources, and line items: an order's items edited as a table in its form, with their total.
- Files and imagesUploads on any resource. Images are resized and compressed as they arrive; private files stay private.
- TrashDeleted records wait 30 days and can be restored, with their files. Closed accounts too.
- Notifications and activityA bell for what needs you, and a log of who created, changed and deleted what.
- A public sitePublic pages and forms on the same API, a blog with a feed and a sitemap, and forms protected from bots.
- SeedingFill a resource with plausible records in one command, and see how long it took.
- Your code is keptRegeneration rewrites only its marked blocks, and skips one you edited inside. An upgrade keeps the dashboard files you changed, and saves its own version for you to compare.
[ 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 referencenevela 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
Describe a resource once. Nevela writes the Laravel side and the dashboard side from it.
Read the referencenevela resource Product --fields="name:string, sku:string!, price:money, kind:enum(stock|digital)"- created app/Models/Product.php
- created database/migrations/…_create_products_table.php
- created app/Http/Requests/Nevela/ProductRequest.php
- created app/Http/Controllers/Api/ProductController.php
- created app/Policies/ProductPolicy.php
- created ../web/resources/product.resource.ts
- created ../web/app/dashboard/products/page.tsx
Change the descriptor and run it again. Generated blocks follow; your own code stays where it is.
Read the referencenevela generate- updated app/Models/Product.php
- updated app/Http/Requests/Nevela/ProductRequest.php
- exists (yours) app/Policies/ProductPolicy.php
- updated ../web/resources/product.resource.ts
- exists (yours) ../web/app/dashboard/products/page.tsx
Fill a resource with records that follow its descriptor, timed.
Read the referencenevela seed Product --count=1000- info Seeded 1,000 Products in 114 ms (8,809 rows/s).
- Products in the database .......... 1,000
And what you write stays small
{ "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 } }}class ProductPolicy{ // A permission, held through a role. Laravel checks it on every request, // and the dashboard hides what a person can't use. public function delete(User $user, Product $product): bool { return $user->can('products.delete'); }}class Product extends Model{ // nevela:generated:start hash=4f1c2a9b7e31 protected $fillable = ['name', 'sku', 'price', 'kind', 'notes']; // nevela:generated:end
// Yours. Regeneration never touches what is outside the markers. public function scopeDigital($query) { return $query->where('kind', 'digital'); }}curl -g "http://127.0.0.1:8000/api/products?sort=-price&q=lamp&filter[kind]=stock" \ -H "Accept: application/json" -H "Authorization: Bearer $TOKEN"[ 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.
The dashboard uses the same REST API you can call from a mobile app, a script or another service.
REST API referenceSeed a thousand records that follow the descriptor, and see the time it took.
nevela seed ProductSeedingQuestions
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

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.