Modern, lightweight PHP NoFramework with Islands Architecture for real-world PHP + JS systems

Status: ✅ Production Ready (v2.5) | PHP 8.1+ | PSR-4 Compliant | MIT License

v2.5: Thin create-project — Welcome homepage (no database), optional demos as a Releases zip, migration runner, Router v2.0, package/provider architecture, AI Agent pack, and PHP + React/Vue Islands Architecture. Kernel lives in src/Etc/; modules are optional.

upMVC ships an AI-native knowledge pack — not a chatbot inside PHP, but portable rules and facts any coding assistant can load so you start in the middle of the house: say what you want to build; the agent already knows paths, bootstrap, modules, and constraints.

You do not need to explain upMVC from scratch in every chat.

1. Run php src/Tools/upmvc-next.php (or pass --goal "…").
2. The CLI scans your project (modules, .env, SaaS pack if present).
3. It writes docs/agent/generated/last-prompt.md — paste into Cursor, Windsurf, Claude, or any agent.
4. The agent follows upmvc-rules.json (must/never) and outputs a plan before multi-file edits.

General mode by default. Module scaffolds and SaaS context are optional extensions — different users use agents differently; we do not force builder mode on every session.

# Interactive — one question, then paste last-prompt.md into your agent
php src/Tools/upmvc-next.php

# Non-interactive
php src/Tools/upmvc-next.php --goal "Fix JWT on /api/auth" --stdout

# Opt-in module builder pack (replaces removed PHP generators)
php src/Tools/upmvc-next.php --scaffold --goal "Create a Blog CRUD module"

Full guide: docs/AGENT_PACK.md · Tests: vendor\bin\phpunit tests\Unit\Tools

Note: Legacy PHP module generators were removed. New modules are created by your AI assistant using the knowledge pack (and optional scaffolds), not php tools/createmodule/….

Need to build a SaaS product? upMVC-SaaS is the official fork of upMVC with multi-tenancy, platform administration, tenant isolation, plan gating, JWT auth, impersonation, and a complete signup/onboarding flow built in — ready to extend, not a starting template.

→ github.com/upMVC/upMVC-SaaS

Thin Core is enough for many apps. When you need more, compose — nothing is mandatory:

Strongest simple foundation for multi-tenant products: upMVC-SaaS + saas-pack + the API library — then SPA modules in whatever JS you like. Each layer stays in its lane; you don’t rebuild tenancy or REST from scratch.

→ Full guide: upMVC + PHP CRUD API Generator (includes the SaaS + API composition)

upMVC v1.0.3 introduces a contemporary design system while maintaining complete backward compatibility:

• 🌟 Modern BaseView: Contemporary CSS Grid/Flexbox layouts with dark mode
• 📱 Responsive Design: Mobile-first approach with modern navigation
• ⚡ Alpine.js Integration: Lightweight interactivity (~40KB vs 87KB jQuery)
• 🎯 Zero Breaking Changes: Drop-in replacement for existing BaseView

Quick Demo (with optional demos installed): /test (original) vs /test/modern (new design) Documentation: Modern BaseView Guide | Demo Instructions

A lightweight, modern PHP 8.1+ noFramework built on Modular MVC (MMVC) architecture. Designed for developers who want flexibility without noFramework bloat. Features true modularity, "PHP Islands" for frontend integration (React/Vue), dependency injection, middleware pipeline, and clean routing. No forced conventions - use pure PHP or integrate modern JS noFrameworks as needed. Perfect for rapid development while maintaining performance and flexibility.

✨ Key Features: Modular architecture • PHP 8.1+ • PSR-4 compliant • Dependency injection • Middleware support • Frontend noFramework integration • Minimal learning curve

upMVC excels at integrating pre-built JavaScript applications from any framework:

• ⚛️ React - npm run build → deploy to module/public (Guide)
• 💚 Vue - Production builds with Vite/Webpack (Guide)
• 🔥 Svelte - SvelteKit or standalone builds
• ⚡ Any Framework - Angular, Solid, Qwik, etc.

Your PHP module serves the built app - no complex webpack configs, no dev servers in production. Just build your JS app locally and deploy the static files. Your Controller exposes data via API endpoints that your JS app consumes.

📖 Complete Guides:

• React Integration - React 18, Vite, Webpack, CRA
• Vue Integration - Vue 2/3, Vite, Webpack, Nuxt
• Coming soon: Svelte, Angular guides

🤔 Why Mix PHP with JavaScript Frameworks?
upMVC is a system architecture, not just a single app. Layer 1 (Main upMVC) handles security, auth, sessions. Layer 2 (Modules) are independent apps using any tech—PHP, React, Vue, Svelte. Split large monoliths into micro-frontends. Each team works independently. Deploy modules separately. One breach can't compromise the entire system. Best of both worlds: Server-side security + client-side reactivity. Read: Why Mix?

🆚 How is upMVC Different?
Unlike Laravel, Symfony, or other PHP frameworks, upMVC is a system, not a framework. No forced conventions, no ORM requirements, no framework rules. "Direct PHP First" principle means complete freedom. Want React in one module and Vue in another? ✅ Want to delete core modules? ✅ Want to split your app into multiple independent instances? ✅ True micro-frontends architecture that nobody else offers. Read: Comparison with Other PHP Projects

📌 Note: Stock upMVC ships a thin Welcome homepage only (no database). Optional demos are a separate download — not a Composer package. See Module Philosophy.

Homepage: / is owned by src/Etc/custom-routes.php → Welcome\Controller. Change or remove that entry anytime and point / at your own module.

Download upmvc-demos.zip from GitHub Releases.

1. Paste Modules/* into src/Modules/ (next to Welcome)
2. Import demo SQL if needed (demo-modules.sql is in the zip, or database/demo-modules.sql in the repo)
3. composer dump-autoload — optional; App\ → src/ usually already covers new folders
4. Done — routes appear (/test, /auth, /admin, …)

Take / try / drop: delete any demo folder under src/Modules/ anytime.

• 📋 First Steps Guide - Get running in 5 minutes
• 📘 How-To Guide - Complete development guide
• ❓ FAQ - Common questions and solutions
• 📚 Documentation Index - Complete documentation map

• 🌟 THE COMPLETE PICTURE - ⭐⭐⭐ START HERE! Everything from .htaccess to controller - Why each piece exists, when to use each strategy
• 📖 Routing Documentation - Complete routing documentation hub
• 📋 Routing Guide - All 5 routing types with decision tree
• 🚀 Router V2 Examples - Type casting, validation, named routes

• JWT Authentication Guide — Opt-in JWT support: issue tokens with JwtService, protect API routes with ['jwt'] middleware, refresh token flow. Sessions are unaffected — JWT is an additional option for APIs and SPAs.

• Database Guide — Two ways in: import database/schema.sql + database/seed.sql for an instant working install, or run php src/Tools/migrate.php for tracked, repeatable migrations. Packages register their own migration paths and are picked up automatically. schema.sql is generated on every run, so it never drifts.

• Agent Pack Guide — Full guide: core JSON pack, upmvc-next.php, optional scaffolds, Cursor/AGENTS.md
• AGENTS.md — Root entry for cloud agents

• 🎨 Pure PHP Philosophy - The upMVC NoFramework approach
• 🧩 Module Philosophy - Modules as reference implementations
• 🔄 Configuration Fallbacks - NEW! Three-level fallback system explained
• 🏝️ Islands Architecture - NEW! Complete guide to PHP + React Islands
• ⚛️ React Integration Patterns - Five ways to integrate React/Vue/Preact
• 🔥 ReactHMR - Hot Module Reload - Demo module in the optional Releases zip (see Reacthmr README inside the pack)
• 📦 Integration: upMVC + PHP CRUD API Generator - Compose with SaaS pack + API (full API plane, not a toy helper)
• 🎯 JavaScript Framework Integration - NEW! Deploy React, Vue, Svelte, or any JS framework build
• ⚛️ React Build Integration - Complete React deployment guide (Vite/Webpack/CRA)
• 💚 Vue Build Integration - NEW! Vue 2/3 deployment guide (Vite/Webpack/Nuxt)
• 🆚 Comparison with Other PHP Frameworks - NEW! Why upMVC is unique
• 💪 Architectural Strengths - What makes upMVC powerful
• 🛣 Routing Capabilities - Understanding the routing system
• �️ Routing & .htaccess System - NEW! Complete guide with module examples (test, moda, userorm, admin)
• �🔧 URL Handling Explained - Request flow and middleware

• 🔐 Authentication Redirect Fix - Session intended_url handling
• ⚙️ Assignment Operator Fix - Comparison vs assignment
• 🚪 Missing Exit Statements - Proper redirect handling
• 📤 Output Before Header Fix - Header redirect timing
• 🔗 Trailing Slash Fix - URL normalization
• 🧹 Debug Code Cleanup - Production-ready code

• 🔍 Pre-Release Verification - Complete verification report
• 🚀 Ready for Main - Production readiness checklist
• 📋 Verification Checklist - Step-by-step validation
• ✨ Enhancements - Latest improvements

• 🐛 /zbug Folder - Debug files and development utilities (excluded from Git)

• 🌟 THE COMPLETE PICTURE - ⭐⭐⭐ Everything explained - .htaccess, Router, all 5 strategies, when to use each
• Complete Routing Guide - Unified guide covering all 5 routing types, decision tree, when to use each
• Router v2.0 Examples - Complete Router V2 usage guide (type casting, validation, named routes, grouping)
• Router v2.0 Changelog - What's new in v2.0
• Implementation Report - Technical implementation details
• Parameterized Routing Guide - Full parameterized routing documentation
• Evaluation Report - Grade: A+ (90/100)
• Future Recommendations - v2.1+ roadmap
• Helpers Class Usage - OOP helper methods guide
• Helper Functions Guide - HelperFacade reference: routes, URLs, CSRF, config, responses

upMVC now features a modern PSR-4 compliant modular helper system:

• Modular Structure: Each helper in its own class (RouteHelper, UrlHelper, FormHelper, etc.)
• Facade Pattern: Unified access via HelperFacade
• Auto-loaded: No manual require_once needed
• Type-Safe: Router V2 integration for named routes
• Scalable: Easy to add new helpers
• View Helper Classes - PSR-4 helper architecture

upMVC provides 5 routing strategies for different scenarios:

1. Simple Static Routes - Fixed URLs (/about, /contact)
2. Parameterized Routes - URL placeholders (/users/{id})
3. Router V2 Enhanced - Type casting + validation + named routes ⭐ NEW!
4. Database-Driven Routes - Dynamic routes from DB
5. Cached Database Routes - DB routes with file caching

Router V2 Enhanced Features:

• ✅ Type Casting: {id:int}, {price:float}, {active:bool} - automatic type conversion
• ✅ Validation: Regex constraints at router level (['id' => '\d+'])
• ✅ Named Routes: addParamRoute(...)->name('user.edit'), then $router->route('user.edit', ['id' => 5])
• ✅ Prefix Grouping: routes are bucketed by first segment internally to speed up matching — an optimisation, not a group() API

Only addParamRoute() is chainable (it returns $this). addRoute() returns nothing, so addRoute(...)->name(...) is a fatal error — attach middleware and methods through its 4th and 5th arguments instead.

Quick Example:

// Router V2 - Type-safe with validation
$router->addParamRoute('/users/{id:int}', User\Controller::class, 'show', [], [
    'id' => '\d+'
])->name('user.show');

// Controller - no manual casting needed!
public function show() {
    $id = $_GET['id']; // Already an integer!
    $user = $this->model->getUserById($id);
    // ...
}

// Generate URLs with named routes
$url = HelperFacade::route('user.show', ['id' => 123]); // /users/123

See: Complete Routing Guide for decision tree and when to use each type

Demo: https://upmvc.com/demo/

Rasmus Lerdorf: PHP NoFrameworks all suck!

Rasmus Lerdorf: PHP NoFrameworks all suck!

Entry Point
The only HTTP entry point is public/index.php. There is no index.php at the project root. Point your web server's document root at public/ — never at the project root, which would expose src/Etc/.env.

Add upMVC to your existing project:

# Step 1: Install via Composer
composer require bitshost/upmvc
# Alternative versions:
# composer require bitshost/upmvc:^2.4  (pin the current minor)
# composer require bitshost/upmvc:dev-main  (bleeding edge - risky!)

# Step 2: Copy the entry point into your own public directory
cp vendor/bitshost/upmvc/public/index.php public/
cp vendor/bitshost/upmvc/public/.htaccess public/

# Step 3: Create the .env the framework reads
cp vendor/bitshost/upmvc/src/Etc/.env.example vendor/bitshost/upmvc/src/Etc/.env
# Edit that file with the required settings:
# - SITE_PATH=/your-folder-name (e.g., /myproject)
# - DOMAIN_NAME=localhost (or your domain)
#
# Database configuration is optional (uses src/Etc/ConfigDatabase.php fallback)
# - Configure only when your modules need database access
# - Framework works without database for static/API projects

Note on .env location. The Environment class currently reads src/Etc/.env relative to the package, so on a library install that file lives inside vendor/. See docs/install-as-library/ for the full picture and an advanced Environment variant that supports a per-install .env outside vendor/.

Run it with:

php -S localhost:8080 -t public

Visit: http://localhost:8080 — Welcome homepage loads with no database. Optional demos (if installed) are discovered automatically.

Create a complete upMVC project in 4 simple steps:

# Step 1: Create project
composer create-project bitshost/upmvc yourProjectName
# Or in current directory:
# composer create-project bitshost/upmvc .

# Step 2: Navigate to project
cd yourProjectName

# Step 3: Configure .env — note the destination: src/Etc/.env, not the root
# cp src/Etc/.env.example src/Etc/.env
# Edit these 2 required settings:
# - SITE_PATH=/yourProjectName/public   # document root should point at public/
#   or SITE_PATH=                       # if the app is at domain root
# - DOMAIN_NAME=http://localhost

# Step 4: Open the site
# Welcome (`/`) needs no database. You can browse immediately after
# configuring DOMAIN_NAME / SITE_PATH.
#
# When you add your own modules (or the optional demo pack) that use PDO,
# point .env at a database — an EMPTY database is enough to avoid
# SQLSTATE[HY000] [1049] Unknown database:
#
#   CREATE DATABASE upmvc CHARACTER SET utf8mb4;
#
# - DB_NAME=upmvc
# - DB_HOST=127.0.0.1
# - DB_USER=root
# - DB_PASS=
#
# Kernel tables and demo logins: see database/README.md
#   mysql -u root -p upmvc < database/schema.sql
#   mysql -u root -p upmvc < database/seed.sql
#
# Optional demo modules (Auth, Test, Admin, React, …):
#   1. Download upmvc-demos.zip from GitHub Releases
#   2. Paste Modules/* into src/Modules/ (next to Welcome)
#   3. mysql -u root -p upmvc < database/demo-modules.sql   # or the copy inside the zip
#   4. composer dump-autoload   # optional
#   Userorm also needs: composer require gabordemooij/redbean
#
# Database settings are optional because upMVC has smart fallbacks:
# - If .env database settings are missing, it uses src/Etc/ConfigDatabase.php
# - Framework will work even without database (for static/API projects)
# - Configure database only when you need it for your modules

That's it! 🎉 Run with:

php -S localhost:8081 -t public

-t public is required — public/index.php is the only entry point, so serving the project root returns 404 for every URL, including /.

Visit: http://localhost:8081 (or adjust for SITE_PATH)

Note: Stock install is Welcome + kernel only. Demo modules are the optional Releases zip (steps above) — not bundled in create-project.

Optional - Keep dependencies updated:

# Update autoloader when adding new modules
composer dump-autoload

# Update dependencies
composer update

You can now declare routes with simple placeholders instead of only exact paths or .htaccess rewrites.

Examples:

// Exact route (unchanged)
$router->addRoute('/users', User\Controller::class, 'index');

// New: parameterized routes
$router->addParamRoute('/users/{id}', User\Controller::class, 'show');
$router->addParamRoute('/orders/{orderId}/items/{itemId}', OrderItem\Controller::class, 'detail');

How it works:

• Exact routes are checked first (fast hash lookup).
• If no exact match, parameterized routes are evaluated (segment by segment).
• Extracted parameters are injected into $_GET (e.g., $_GET['id'] = '123') and also available to middleware via $request['params'].
• Controllers keep their simple signature: action($route, $method) and read params from $_GET.

Benefits:

• Cleaner route declarations for resource-like URLs.
• Fewer .htaccess patterns; less boilerplate loops.
• Backward compatible; you can mix exact and param routes.

Notes:

• Placeholder syntax: {name} (letters/digits/underscore, must start with a letter/underscore).
• Exact routes always win over parameterized routes (e.g., /users/profile).
• Type validation remains in your controller (e.g., ctype_digit($_GET['id'])).

Use the cache maintenance utility to inspect and clear caches (module discovery, admin dynamic route cache, and configured cache stores).

# List available commands
php src/Tools/cache-cli.php list

# Show cache statistics
php src/Tools/cache-cli.php stats

# Clear only module discovery caches
php src/Tools/cache-cli.php clear:modules

# Clear Admin module dynamic route cache
php src/Tools/cache-cli.php clear:admin

# Clear everything (modules + admin + cache stores)
php src/Tools/cache-cli.php clear:all

Windows PowerShell example:

php .\src\Tools\cache-cli.php clear:all

Affected components:

• Module discovery cache used by src/Etc/InitModsImproved.php in production mode.
• Admin dynamic route cache file: src/Etc/storage/cache/admin_routes.php.
• All instantiated cache stores via App\Etc\Cache\CacheManager::clearAll().

Exit codes: 0 success, 1 failure, 2 unknown command.

See AI Agent — built-in context above for the full picture. From src/Tools/:

php src/Tools/upmvc-next.php
php src/Tools/upmvc-next.php --goal "Audit my .env wiring" --stdout
php src/Tools/upmvc-next.php --scaffold --goal "Add Api/Bookings module"

Output: docs/agent/generated/last-prompt.md (gitignored). Details: docs/AGENT_PACK.md.

upMVC uses a smart layered configuration system with automatic fallbacks:

Edit .env (at project root) for environment-specific settings:

• Required: SITE_PATH, DOMAIN_NAME, APP_ENV
• Optional: Database, mail, cache, session settings

upMVC has intelligent fallbacks that let the system work immediately without complete configuration:

1. Path & Domain → .env or Config.php fallbacks
2. Protected Routes → .env or start.php defaults
3. Database → .env or ConfigDatabase.php fallbacks
4. Session Configuration → Config array or hardcoded defaults (lifetime, secure, httponly)
5. Security/Middleware → .env ConfigManager or defaults (CORS, CSRF, rate limiting)

Why? Start coding immediately, configure gradually as you need features!

📖 Complete Fallback Documentation - Detailed guide with examples and troubleshooting

If something doesn't work as expected, check:

1. .env file (highest priority)
2. Config.php fallbacks (path/domain + session)
3. start.php defaults (protected routes + security)
4. ConfigDatabase.php (database credentials)
5. ConfigManager.php (all .env-based defaults)

💡 Pro Tip: Start with just SITE_PATH and DOMAIN_NAME, add database later when needed!

upMVC v2 uses a Router v2.0 + auto-discovery model – you configure the core router once and let modules register themselves.

1. Global Routes → src/Etc/Routes.php
   • Application-wide routes (health, home, system-level endpoints).
2. Router v2.0 → src/Etc/Router.php
   • Exact routes + parameterized routes (typed, validated, named).
3. Module Auto‑Discovery → src/Etc/InitModsImproved.php
   • Scans src/Modules/* and automatically wires module routes.

Composer now handles everything via a single PSR‑4 root:

"autoload": {
    "psr-4": {
        "App\\": "src/"
    }
}

• No per‑module namespace entries needed in composer.json – all modules live under the single App\ tree.
• Inside your module code you still declare normal namespaces like App\Modules\Blog, App\Modules\Shop, etc. – Composer autoload will resolve them automatically.
• After adding new modules, run: composer dump-autoload

1. Create your module under src/Modules/Yourmodule/ (Controller, View, etc.).
2. Expose routes from the module via its Routes/routes method (see docs and examples).
3. Ensure InitModsImproved is in use – it will auto‑discover and register the module.
4. Visit the module URL; Router v2.0 + middleware handle the rest.

Examples & Guides:

• Optional demos (Test, Admin, …) ship in the Releases zip — not in a stock clone.
• Read: docs/routing/ROUTING_GUIDE.md, docs/routing/ROUTER_V2_EXAMPLES.md, and docs/routing/ROUTER_V2_CHANGELOG.md.

Note:

A friendly URL is a short and simple web address that redirects to a longer web address. Friendly URLs are called Aliases in Sitecore.

We achieve this by combining some .htacces rules with module routes. Check modules/test/routes/Routes.php and the .htaccess file - you will notice the rules established in the.htaccess file for these specific routes - you may build as many as you like.

In the same file, modules/test/routes/Routes.php, you will see for demonstration purposes how you may handle a large number of URLs with parameters (such as an idProduct) in a very straightforward way.

• Copy src/Etc/.env.example to src/Etc/.env — it stays in that folder, which is where Environment reads it — and fill in SITE_PATH, DOMAIN_NAME, and database credentials.
• For mail: configure src/Modules/Mail/MailController.php with your SMTP settings (or use .env MAIL_* keys).
• Make your module in the MVC style (model, view, controller).
• You may or may not wish to utilize BASE MODEL, BASE VIEW and BASE CONTROLLER from src/Common/Bmvc/.
• BaseModel contains all of the data required for CRUD OPERATIONS; simply expand it in your module model and you have a CRUD ready-made module; see example module src/Modules/User/.
• Make a distinctive namespace for each module under App\Modules\YourModule.
• Your module routes should be kept under src/Modules/YourModule/Routes/Routes.php.
• InitModsImproved (src/Etc/InitModsImproved.php) auto-discovers and registers routes — no manual wiring needed.
• After adding new modules, refresh the autoloader:
• composer dump-autoload

• Model, View, Controller - will be called without using module name in their name. For example, module name = books:
• Model.php - class Model; View.php - class View; Controller.php - class Controller;
• and make a distinctive namespace for each module, mirroring its folder - e.g. namespace App\Modules\Books;
• Your module routes should be kept under src/Modules/YourModule/Routes/Routes.php:
  • Routes.php class Routes in src/Modules/Books/Routes/
  • namespace App\Modules\Books\Routes

Diagram:

File Structure:

All NoFramweworks: "achieve this simplicity by sacrifizing flexibility and performance" Rasmus Lerdorf

upMVC - MMVC, PHP MVC with modules. Modular MVC(Model, View, Controller) derive from Hierarchical Model‐View‐Controller (HMVC).

Introducing MODULAR MVC - Empowering Your Development

In the realm of modern noFrameworks, it often feels like they do everything except what truly matters. These noFrameworks tend to add layers of abstraction that demand you to learn new skills and pathways whenever you decide to switch. They also tend to clutter themselves with superfluous options, solving simple problems in needlessly convoluted ways.

Consider PHP, including its blade templating engine. Why introduce yet another template engine when PHP is already equipped for the task? Delving into a new noFramework often necessitates a substantial relearning effort, pushing you far beyond your existing PHP knowledge.

So, why should you choose MMVC?

MMVC, standing for Modular Model View Controller, is not about reinventing the wheel. Instead, it's about optimizing the use of exceptional components. It offers a structured, straightforward approach, and its versatility proves invaluable for project management and development.

But why MMVC specifically?

1. Modularity: MMVC allows you to work on a module without impacting the rest of your project. Modules can be interchanged and integrated seamlessly, enhancing your development agility.

2. Language Freedom: Perhaps most importantly, you have the freedom to write your modules in your preferred language, whether it's PHP, JS, PYTHON, or modern technologies like TS, React, Vue, Preact. There are no constraints on your creativity.

3. Development-Centric: MMVC was designed with development in mind. You can steer your project in any direction you desire, utilizing your own autoloader or composer autoload. Composer/packagist usage is optional, not obligatory.

4. "Islands" of Interactivity: Within this PHP-generated HTML, you strategically place interactive components built with noFrameworks like React, Vue, Preact or Svelte. These components handle dynamic elements, such as user interactions, real-time updates, and animations. Read here: The Rise of "PHP Islands": A Hybrid Approach to Web Development

What truly sets MMVC apart is its ability to harness the latest PHP capabilities without constraint. No more endless loops, as this noFramework liberates your development possibilities.

BitsHost Team