# Laravel *PHP framework for web applications* Laravel is a PHP framework for building web applications — the kind with accounts, permissions, a database and work that runs in the background. It supplies the parts every application needs so they are not rebuilt by hand on each project. **Canonical:** https://spoko.space/glossary/laravel/ **Language:** en **Category:** Technology **Also known as:** Laravel framework, PHP framework **Published:** 2026-09-22 **Glossary:** https://spoko.space/glossary/ --- ## What it is {#what-it-is} A framework for the kind of software where a website stops being documents and starts being a system: people log in, they have different permissions, data is created and edited, something has to happen on a schedule, and a slow task must not make the page wait. Laravel provides those parts — routing, the database layer, authentication, validation, queues, scheduled jobs, mail — so a project starts at "what does this business do" rather than at "how do users log in". ## Why it matters if you are paying for a website {#why-it-matters-if-you-are-paying-for-a-website} It probably does not, if what you need is a website. A company site, a blog, a landing page — none of that wants an application framework, and quoting one for that work means paying for machinery that will never turn. It matters when the brief contains a verb: orders that get *processed*, stock that gets *reserved*, messages that get *sent*, reports that get *generated*. That is when a site becomes an application, and an application without a framework becomes a pile of scripts nobody dares to change. ## What I have built with it {#what-i-have-built-with-it} An SMS platform that sends messages for businesses, where the interesting part is not the sending but everything around it — accounts, credit, delivery reports, retries when the operator is unreachable. A garage inventory system. The backend of a parts catalogue with its own admin panel. Two pieces of Laravel earn their keep on every one of those. **Queues**, because anything slow — sending, generating, calling somebody else's API — belongs outside the request, and a visitor should never wait for it. And **the testing setup**: those projects run their end-to-end suites in parallel against the framework's own test tooling, which is the only reason a suite that takes half an hour stays something anyone runs. ## What Laravel is not {#what-laravel-is-not} It is not a CMS and it is not a WordPress replacement. Editing content is not what it does; if a client's main need is "I want to change this text myself", Laravel means building that editor, and a CMS already has one. It is also not a reason to rebuild a working WordPress site. The right question is whether the thing you have is a document that needs editing or a system that needs rules — and the answer is usually visible in the brief. ## Related terms {#related-terms} - [Vue](https://spoko.space/glossary/vue/): Vue is a JavaScript framework for building interfaces out of components whose display updates automatically when their data changes. It can run a whole application or a single widget inside a page that is otherwise plain HTML. — Markdown: https://spoko.space/glossary/vue.md - [headless CMS](https://spoko.space/glossary/headless-cms/): A headless CMS stores and edits content but does not render the website. The pages are built by something else, which reads the content over an API — so the editing tools and the front end can be changed independently of each other. — Markdown: https://spoko.space/glossary/headless-cms.md - [Astro](https://spoko.space/glossary/astro/): Astro is a web framework that renders pages to HTML at build time and ships no JavaScript unless a component asks for it. Interactive pieces are declared one by one as islands, so a page carries the code for those and nothing else. — Markdown: https://spoko.space/glossary/astro.md - [CMS](https://spoko.space/glossary/cms/): A CMS is the software that lets someone change a website without touching code. The word covers three separate jobs — editing, storing and displaying content — and most arguments about which CMS to use are really arguments about which of the three you need. — Markdown: https://spoko.space/glossary/cms.md ## Where I write about this {#related-posts} - [Modern Car Blog](https://spoko.space/modern-car-blog/) — Markdown: https://spoko.space/modern-car-blog.md Headless automotive blog built with Astro, Vue3, UnoCSS, and a WordPress REST API backend — static performance with a familiar CMS for content editors. - [GotowySMS: A Platform for Ready-Made SMS Texts](https://spoko.space/gotowysms/) — Markdown: https://spoko.space/gotowysms.md Static site with ready-to-use wish texts and SMS templates, powered by a custom CMS on Laravel 13 + FilamentPHP. Architecture built to withstand seasonal traffic spikes. - [E2E Testing with AI and Playwright (2026) — Practical Guide](https://spoko.space/blog/e2e-tests-ai-playwright-guide/) — Markdown: https://spoko.space/blog/e2e-tests-ai-playwright-guide.md Where AI actually saves time in Playwright E2E tests: selector strategy, prompt patterns, MCP integration, and real ROI numbers from production projects. - [7× Faster E2E Tests: Solving a Laravel Session Bug That Looked Like Flaky Playwright Tests](https://spoko.space/blog/playwright-laravel-parallel-e2e/) — Markdown: https://spoko.space/blog/playwright-laravel-parallel-e2e.md How a session architecture problem masquerading as flaky Playwright tests brought a Laravel CI suite to its knees — and how per-worker sessions, a seed API, and a tuned PHP server fixed it. ## See also {#see-also} - [Web development](https://spoko.space/web-development/) ## Sources {#sources} - [Laravel documentation](https://laravel.com/docs) — The framework, feature by feature. - [Laravel — queues](https://laravel.com/docs/queues) — The background-work model that keeps slow tasks out of the request.