Obsidian Admin LaravelStrictly-typed Laravel 12 admin backend baseline

Why this project exists ​

Most Laravel admin backends stop at CRUD scaffolding. This project is designed for long-lived internal platforms and SaaS control planes where tenant safety, API contracts, runtime discipline, and maintainability matter more than quick demos.

Recommended pairing ​

Use this backend with Obsidian Admin Vue if you want the full contract-driven admin stack.

What to read next ​

• Start with Getting Started
• Use Full-Stack Evaluation if you want the shortest path for frontend preview, backend runtime, or full local pairing
• Review the Compatibility Matrix and Multi-Tenancy
• Use Tenant Switching Semantics if you need the exact rules behind platform scope vs selected-tenant scope
• Use Health Model if you need the exact semantics behind live, ready, diagnostics, and CI runtime probes
• Use Runtime Topology if you need the repository's php-fpm, Octane, queue, Reverb, and health-probe model in one place
• Use Backup and Recovery when you need the database backup, restore, and runtime rollback path in one place
• Use Backup/Restore Drill when you want a repeatable rehearsal checklist with exact commands and evidence capture
• Use Security Baseline if you need the exact role of php artisan security:baseline and how it fits into release gates
• Read the Backend Architecture, RBAC and Role Levels, and OpenAPI Workflow
• Use Session and 2FA if you need the auth-session model, device management, and TOTP guarantees in one place
• Use Audit and Compliance when you need the repository's audit policy and retention model in one place
• Use Deletion Lifecycle if you need the repository's disable-first, soft-delete, and purge model in one place
• Use Testing when changing contracts, tenancy, or runtime behavior
• Review Realtime if you are pairing with the websocket-enabled frontend flows
• Choose between Production Runtime and Octane Runtime
• Use Release Artifacts when you need the exact GHCR / SBOM / attestation consumption path
• Use Open Source Launch Checklist when you are promoting the backend and frontend together
• Use Full-Stack Demo Environment when you want to move from preview-only evaluation to a real hosted demo
• Use Demo Deployment Runbook when you want the exact first-pass commands for a hosted evaluator environment
• Use Evaluator Demo Validation when you want the minimum acceptance checklist for the first hosted demo
• Use the Release Final Checklist before publishing