Download the PHP package bayuasrori/ultramod without Composer

Why Ultramod?

Every Laravel project rebuilds the same things: auth, roles, settings, audit logs, file handling, a dashboard, a navigation menu. Ultramod ships all of that as platform capabilities — and gives you a module system where applications are regular Laravel code living in apps/, independently installed, enabled and removed.

The one thing you must see: an app can extend another app without touching its source code. Upgrade the base app; the extension keeps working. That is the whole point of this project.

It's just Laravel

No DSL. No visual builder. No schema builder. No magic abstraction layer.

An Ultramod app contains the things you already know:

Open any app and you will think: "this is just Laravel." That is deliberate.

Start a project

That is the whole install. create-project generates the app key, creates database/database.sqlite, runs the migrations, seeds the admin account and scans apps/ — so the platform is up on the first run.

Not on Packagist yet? Point Composer straight at the repository:

Log in at http://localhost:8000 with the seeded admin:

The first user to self-register on a fresh install automatically becomes the super admin.

A new project starts with every bundled app discovered but not installed — the launcher is empty on purpose. Install what you actually want:

...or do it from Apps in the navbar.

Prefer a different database? Set DB_CONNECTION in .env before the first php artisan migrate --seed.

Working on Ultramod itself

Meet the starter apps

Six working applications ship in the box — not skeletons, real features:

Enable what you need, ignore the rest:

The showcase: Notes + Notes Status

This is the architectural proof the platform is built around.

notes-status is a separate package that adds a status workflow (Draft → Review → Published → Archived) to Notes. It owns its own tables (note_statuses, note_status_assignments), defines its own permissions, and injects its UI into Notes pages — without changing a single line of Notes code.

Try the full lifecycle yourself:

• Create a note → it automatically gets a Draft badge and a status dropdown.
• Disable notes-status → the status UI vanishes. Notes keeps working, data intact.
• Re-enable it → status returns instantly.
• Try php artisan platform:app:disable notes while the extension is enabled → rejected: "Cannot disable Notes because Notes Status depends on it."
• Upgrade Notes 1.0 → 1.1 → Notes Status doesn't need a single change.

How extensions plug in

Four small, intentional mechanisms — all Laravel-native:

Build your own app in 60 seconds

Scaffolds a working skeleton under apps/weather/ — service provider, controller, route, view, migration folder, manifest, Composer autoload entry — then install & enable it from the dashboard or CLI.

Want full CRUD? Use the scaffolder in the web UI (/platform/apps/create): enter a table name and columns, and Ultramod generates migration, model (fillable + casts), controller, form request with validation, resource routes and Bootstrap index/form views. Generated code is ordinary Laravel — edit it freely.

Column types are the common ones only: string, text, integer, float, decimal, boolean, date, datetime. id, created_at and updated_at are generated for every table and cannot be declared by hand.

Core capabilities

Infrastructure every app consumes — no app rebuilds these:

All admin pages (users, roles, apps) are Bootstrap, responsive, and permission-gated.

App lifecycle

Upgrading an app

Bump the version in platform.json, ship the new code, and the dashboard shows 1.0.0 → 1.1.0 · upgrade available next to the app with an Upgrade button. Clicking it opens the plan — pending migrations, upgrade steps, permission changes, apps that have to come along — and confirming runs the whole thing:

Data migrations that belong to one version live next to the app, and are returned the way a Laravel migration is returned — no autoload entry needed:

Going from 1.0 to 1.2 runs the 1.1 steps and then the 1.2 steps — versions are never skipped. Every step is recorded in platform_app_upgrades, so a step that already succeeded is not run again and a half-failed upgrade can simply be retried. If a step throws, the version is not bumped, the migration batch is rolled back and the error is shown on the dashboard.

An app that depends on the one being upgraded either comes along in the same plan or the upgrade is refused — notes-status ^1.0 will not be left behind on notes 2.0.

Manifest presentation fields

How an app shows up in the launcher and the navbar is declared, not hardcoded:

These are mirrored into the registry by discovery, so editing them takes effect on the next page load — no upgrade, no cache clear.

Dependencies are declared in the manifest and enforced in every direction:

Project layout

Core owns platform_* tables. Apps own their own tables (notes, kanban_*, calendar_events, …). Extensions own the data they introduce — Notes Status never adds a column to notes.

Testing

Coverage includes app lifecycle & dependency rules, the Notes ⇄ Notes Status extension contract (install/enable/disable, data isolation, upgrade safety), auth (login, rate limit, registration), role/permission enforcement, and end-to-end feature tests for all starter apps.

Non-goals (on purpose)

Ultramod is a modular monolith, not a framework factory. It will never grow into a marketplace, low-code builder, plugin sandbox, or microservice runtime. If you're looking for Filament/Nova-style admin generation or a visual app builder, this is not that — and that's the point.

License

MIT