Service · Web development

Custom Laravel website and web application development.

Custom PHP platforms on Laravel 11 for admin portals, B2B applications, SaaS startups and customer dashboards. Fast to production with Livewire, Filament and Octane — with a codebase your own team can take over without vendor lock-in.

Laravel 11Livewire & InertiaFilamentOctane & Forge

What Laravel is, and why it is still a sensible default in 2026.

Laravel is the leading PHP framework for modern web applications. It is a mature platform that sits somewhere between a "framework" and an "application platform": for much of what you encounter in a typical web application — authentication, authorisation, database access, queues, mailing, file storage, scheduling, payments — there is a well-thought-out, tested, conventional solution that works straight away. You write less glue code and can get to the part that sets your product apart sooner.

Since Laravel 11, the baseline has been modernised again: a slimmed-down application skeleton, first-class Vite integration, Pest as the default testing framework and Laravel Reverb as an in-house WebSocket server. Eloquent — the actively maintained ORM — treats database records as objects you can query naturally, with relationships, casts, scopes and eager loading in just a few lines. For the frontend layer you have a choice: Livewire 3 if you prefer to keep your screens entirely in PHP, with server-side rendering plus live interaction, or Inertia 2 if you want React or Vue as the view layer without the overhead of a separate SPA build with an API in between.

We build Laravel platforms for founders with a SaaS MVP, for SMEs that want to replace their Excel or Access processes with a proper portal, and for enterprises that want to modernise a legacy PHP application without a full rewrite to an entirely different stack. The broader service context is on the overarching web development page. For capacity questions, see hiring a full-stack developer.

When Laravel is the right answer.

Six patterns we come across regularly. If you recognise one of them, Laravel is almost always a pragmatic default — and we can quickly move on to discussing scope.

Admin portals

You want an internal portal for your team or suppliers

For admin dashboards, supplier portals, customer cockpits or internal management, Laravel with Filament is an exceptionally fast foundation. Filament generates CRUD screens, forms, tables, filters and role-based access from your Eloquent models, so the heavy lifting goes into business logic rather than glue code. The portal feels professional from day one and can later be extended with custom panels and widgets.

B2B platforms

You're building a platform with multiple user roles

For B2B platforms with multi-tenancy, role-based access control and business logic that differs per customer, Laravel is well positioned. Spatie Permissions provides mature role and permission management, Sanctum or Passport handles API tokens, and the queue layer processes heavy background tasks without making the user wait. For a React frontend on top, a single-page application is the logical extension via Inertia 2.

SaaS startups

You want to get from MVP to product-market fit quickly

For SaaS startups that need to iterate quickly, Laravel is one of the shortest paths to production. Cashier supports Stripe and Paddle billing with subscriptions, trials, prorations and webhooks; Jetstream or Breeze provide registration, login, two-factor authentication and team management out of the box. You build product functionality, not plumbing — and the codebase stays understandable for an in-house team.

CMS-light and marketing sites

You want a website with strong custom functionality

For websites that are more than a handful of pages — a customer portal tied into your marketing site, configurators, calculators, dynamic landing pages or your own e-commerce flow — Laravel with Statamic, or a custom content layer on Filament, is far more flexible than WordPress as an archipelago of plug-ins. You keep ownership of the codebase and write every business rule in modern PHP.

API backends

You're building a mobile app or frontend that needs an API

Laravel as a pure API backend for a React, Vue or mobile application is a strong choice: API resources for JSON transformation, Sanctum for token authentication, Octane for low latency and solid testing tools to keep endpoints contract-stable. Combining it with an Inertia 2 frontend almost always gets you to production faster than a separate React SPA with a standalone REST backend.

Marketplaces & community

You want a platform where parties meet

For marketplaces, job platforms, comparison sites or community portals where multiple parties post content and transact, Laravel is a productive choice. Multi-tenant data isolation, payment flows with escrow, search via Scout on Algolia or Meilisearch, and moderation tooling via Filament — all of these have a conventional solution, so you don't have to build them from scratch.

When Laravel is not the right choice.

Being honest saves you an expensive rethink halfway through. These are the three patterns where we'll point you towards another framework or platform.

Not 01

Heavy real-time or WebRTC apps

For applications with large-scale bidirectional communication — video conferencing, live game states, collaborative editing à la Figma, signalling servers for WebRTC — Node.js with Socket.IO, or a Go or Elixir (Phoenix) backend, is a more natural choice. Laravel Reverb covers many real-time use cases, but for deep event loops with thousands of concurrent connections per server, an event-driven runtime is fundamentally better suited.

Not 02

CPU-intensive computation or data engineering

For heavy computer-vision pipelines, machine-learning training, numerical simulations or ETL on large datasets, PHP — and therefore Laravel — is not the right runtime. Python with NumPy, pandas and PyTorch, or Rust for maximum performance, are the logical answers. We often work in a hybrid setup: Laravel as the application layer, with a Python or Rust service alongside it for the heavy compute.

Not 03

Gaming and graphics-heavy frontends

For browser gaming, 3D render pipelines, WebGL or WebGPU applications or native mobile gaming, Laravel is a backend layer — never the runtime of the game itself. For the game client, Unity, Unreal or platform-native rendering with Metal and Vulkan are the right choices. In that scenario, Laravel can handle player accounts and the matchmaking API perfectly well.

Laravel, Symfony, Node or Django — a sober comparison.

The four alternatives that regularly come up in our intake conversations. In the first meetings we'll help you choose which one fits, based on your stack, team composition and product ambitions.

Criterion
Laravel
Symfony
Node / Express / NestJS
Language
PHP 8.3+
PHP 8.3+
TypeScript / JavaScript
Best for
SaaS, portals, B2B platforms, MVPs
Enterprise, complex domain models
Real-time, event-driven, high concurrency
Dutch talent pool
Large — PHP and Laravel specialists
Medium-sized, often senior-only
Large, shared with frontend developers
Time to MVP
Short — lots of functionality out of the box
Longer — more configuration, more abstraction
Variable — depends on your choices
ORM
Eloquent (Active Record)
Doctrine (Data Mapper)
Prisma, TypeORM, Drizzle
Admin tooling
Filament — mature, fast
EasyAdmin, Sonata — capable
AdminJS, Refine — younger ecosystem
Real-time
Reverb / Pusher / Soketi
Mercure, Symfony Messenger
Native via Socket.IO, ws
Convention vs. configuration
Strongly convention-driven
Configuration-driven, flexible
No framework, you choose every layer

The modern Laravel stack in 2026.

Our default setup for production applications. Depending on your scope we swap out components, but these are the building blocks we start with by default.

Core & runtime

Laravel 11+, PHP 8.3+, Eloquent

We start on the latest Laravel version with PHP 8.3 or newer. Eloquent as the ORM, with explicit relationships, casts to value objects where it makes sense, and a disciplined approach to eager loading to prevent N+1 problems. PHPStan at level 7+ for static typing checks in CI.

Frontend layer

Livewire 3, Inertia 2, Vite, Tailwind

For most projects, Livewire 3 with Volt and Alpine.js: server-rendered PHP components with live interaction, without an SPA build. Where React or Vue is required as the view layer, we use Inertia 2 as an adapter, so we keep Laravel routing and controllers and don't have to maintain a separate API. Vite for assets, Tailwind v4 for styling.

Admin & CMS

Filament 3, Statamic, Nova

Filament 3 as our default for admin panels: mature, quick to configure and extensible with custom pages, widgets and form fields. Statamic as a CMS on top of Laravel for content-driven marketing sites. Laravel Nova as a licensed alternative for clients who prefer the official Laravel tooling.

Performance & queues

Octane (FrankenPHP), Horizon, Pulse

For high-load applications, Laravel Octane runs on top of FrankenPHP, Swoole or RoadRunner: the application stays warm between requests instead of booting again on every call. Horizon for managing queues on Redis, Pulse for real-time insight into slow queries, slow routes, exceptions and cache hits.

Packages & integrations

Spatie, Cashier, Scout, Sanctum

The Spatie packages for permissions, query builder, media library, activity log and backup are among our defaults. Laravel Cashier for Stripe or Paddle billing, including webhooks, Scout for full-text search via Algolia, Meilisearch or Typesense, Sanctum for lightweight API token auth and Passport for full OAuth2 when third parties need to be able to integrate. Socialite for SSO via Microsoft, Google or your own OIDC provider.

Quality & testing

Pest, PHPStan, Laravel Dusk

Pest as our testing framework for its readable syntax and native parallel execution. Architecture tests via Pest's arch plugin to enforce dependency boundaries, for example that models don't make HTTP calls or that controllers don't write directly to the database. Dusk for browser end-to-end tests, Larastan for static typing checks. CI on GitHub Actions with matrix builds against multiple PHP versions.

Hosting & deployment

Forge, Vapor, Laravel Cloud, Kubernetes

For server-based hosting, Laravel Forge on top of DigitalOcean, Hetzner or AWS: simple provisioning, zero-downtime deploys via Envoyer, automatic SSL. For serverless, we host on Laravel Vapor (AWS Lambda) or Laravel Cloud. For enterprise environments with strict isolation requirements or existing Kubernetes infrastructure, we deploy Octane containers via Helm charts on your own cluster.

Monitoring & observability

Sentry, Pulse, Telescope, Cronitor

Sentry for errors and performance tracing, with source maps and breadcrumbs set up. Laravel Pulse for real-time stack stats (slow queries, slow jobs, exception counts, cache hit rates) in the Laravel dashboard. Telescope in staging and locally only. Cronitor or Healthchecks.io for scheduled job monitoring, so a stalled queue or silenced cron doesn't quietly hang unnoticed.

Three flavours of Laravel projects.

It depends on where you are now and what it needs to deliver. We'll advise which approach fits in the first conversation — no fixed packages, but clear outlines.

MVP · fixed sprint budget

SaaS MVP on a Laravel foundation

A first working version of your SaaS product on a production-grade foundation. Registration, login, two-factor auth, team management, Stripe billing, a working admin panel via Filament and an initial set of features. Not a "throwaway MVP" but a codebase that grows with you, so after validation you can keep building instead of rebuilding.

Breeze / JetstreamCashierFilamentForge
Production platform · fixed sprint budget

B2B platform or customer portal

A Laravel application that belongs to an existing product or business. Deep integrations with your ERP or CRM, identity provider (Azure AD, Okta, your own IdP), payment flows and analytics. We build on the production stack above from day one and deliver with monitoring, alerting and a release pipeline your own team can run themselves. SSO, role-based access and multi-tenancy where needed.

SSO / OIDCSpatie PermissionsOctaneSentry
Migration · pragmatic approach

Migrating from legacy PHP, WordPress or Symfony

You have an existing PHP platform, such as an old custom application, a WordPress site that has got out of hand, or an early Symfony project, and want to move to a modernised Laravel stack. We work pragmatically: keep what works, replace what hurts, and move towards the new stack module by module rather than in a big bang. Production stability is maintained throughout the entire project.

Strangler figSchema migrationCo-existenceCo-ownership
Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

What you get at the end.

A production-ready Laravel project, plus everything around it so you can run and extend the application yourself. Nothing in what we deliver depends on staying with Appfront, because vendor lock-in is not the aim.

  • The Laravel application in productionA running application on your own hosting (Forge, Vapor, Cloud or Kubernetes), with TLS, a production database and a staging environment that mirrors production.
  • Codebase with PHPStan and a test suiteThe full source in your Git repository, with PHPStan in CI, a Pest test suite for critical flows and GitHub Actions or GitLab CI as the orchestration layer.
  • Documentation and architecture recordsA build and deployment runbook, an overview of environment variables, ADRs for key architectural decisions and an overview of third-party services.
  • Monitoring from day oneSentry for errors and performance traces, Pulse for real-time stack stats, health checks for the scheduler and queues. Set up before go-live, not sometime afterwards.
  • Handover to your teamKnowledge transfer sessions, a video walkthrough of the codebase, and pair programming with your developers who will be involved in maintenance or further development.
  • Maintenance contract (optional)Ongoing monitoring, dependency updates, security patches and further development. You can take over yourself at any time, with no exit fee and no exclusivity clause.

How a Laravel project works.

1

Introduction and scoping

A conversation in which we understand what you want to build, for whom, and which stack and organisation it needs to fit into. We test whether Laravel is the right answer, and tell you honestly when Node, Symfony or a Python layer is a better fit.

2

Planning, architecture and stack choices

We work out a sprint plan, sketch the architecture and choose the stack components (Livewire or Inertia, Filament or Nova, Forge or Vapor). For production platforms, we run a spike in parallel on the heaviest integration or the most critical performance path, so assumptions are validated up front rather than only during the build.

3

Building in sprints with staging deploys

Every sprint delivers a working build on staging for your team and stakeholders. Feedback goes into the next sprint or a hotfix deploy. Code reviews, automated tests with Pest and PHPStan, and performance checks are part of the cycle, not something done once at the end.

4

Go-live with close monitoring

Production deployment via Envoyer or the hosting pipeline of your choice, with a blue-green or canary rollout where the scope justifies it. We monitor closely during the first few days, paying particular attention to slow queries, queue lag and exception spikes. For B2B platforms we often use a phased rollout: internal users first, then a pilot, then general availability.

5

Management and further development

After go-live, the team keeps monitoring closely, acts on feedback and makes sure dependencies, PHP versions and the Laravel LTS cycle keep pace. Further development runs in new sprints, with clear prioritisation based on data and user feedback.

Who we build Laravel platforms for.

Four audiences for whom Laravel, and the way we work with it, has proven its value.

Founders & SaaS

Reaching product-market fit fast

You're building a SaaS product and want to avoid starting from scratch without boilerplate. With Laravel, the foundations — auth, billing, admin, queues, mail — are up and running quickly, on a production-grade base, so you can go live after every sprint rather than only at the end.

SMEs with legacy platforms

Excel or Access replacements and portals

You're still running on an Excel chain, an Access database or an outdated custom PHP application. For replacing these, Laravel with Filament is disproportionately productive — the broader web development process often revolves around a core portal like this. We advise on the data migration and keep your operations running throughout the process.

B2B and marketplaces

Platforms with multiple roles and parties

For B2B platforms with multi-tenancy, marketplaces or comparison sites, Laravel is a productive choice. It can be combined with SSO, identity providers and existing back-office systems. For capacity questions, we look at full-stack developer hire.

Enterprise & modernisation

Migrating legacy PHP platforms

You already have a production PHP application on an older framework and want to move to Laravel without a big-bang release. We work module by module using the strangler fig pattern, preserving production stability and phasing features out of the old codebase towards the new stack — at a pace your organisation can handle.

Fabian van Dijk Business developer · Appfront

Your first point of contact for Laravel projects at Appfront. You can reach him at fabian.vandijk@appfront.nl for a no-obligation introduction on when Laravel fits your stack and organisation — and when Symfony, Node or a Python layer is the honest answer.

Frequently asked questions about Laravel.

What clients usually want to know before we start.

Laravel or Symfony — which should we choose?
Both are mature PHP frameworks sitting at different points on the convention-versus-configuration spectrum. Laravel is strongly convention-driven: you get a lot out of the box and get going faster. Symfony is configuration-driven and more loosely coupled, which gives more flexibility but requires more explicit choices. For SaaS, portals, MVPs and B2B platforms, we almost always choose Laravel. For enterprise environments with complex domain models, Symfony — often combined with Doctrine and DDD patterns — can be the right choice.
Laravel or Node.js — what's the difference in practice?
PHP and Node run fundamentally differently: PHP is shared-nothing per request, while Node uses an event loop with persistent state. For traditional web applications — CRUD, dashboards, B2B portals — the difference is small in practice, especially with Laravel Octane. For real-time, high concurrency or long-running connections, Node is fundamentally better positioned. We often work in a hybrid setup: Laravel for business logic and UI, with a Node service alongside it for the real-time components.
What about Laravel performance under heavy load?
Laravel on Octane (FrankenPHP, Swoole or RoadRunner) stays warm between requests, which significantly reduces latency compared with the classic PHP-FPM cycle. We resolve N+1 problems with explicit eager loading, catch slow queries early via Pulse, and cache where it makes sense via Redis. For extreme scale: horizontal scaling via Vapor or Kubernetes clusters of Octane containers, with a read replica for analytics.
What's the difference between Livewire and Inertia?
Livewire keeps the view layer entirely in PHP — Blade templates with server-rendered components that get live updates and form bindings through a thin JavaScript layer (Alpine.js). No separate API, no SPA build, no frontend router. Inertia uses React, Vue or Svelte as the view layer but keeps server-side routing and controllers — you pass props instead of JSON, but otherwise it feels like an SPA. Our default is Livewire for portals and admin flows, and Inertia for projects where the frontend team works in React or where the design calls for interactive components that are more naturally written in JavaScript.
Use Filament or build a custom admin?
In almost all cases, Filament. Filament 3 delivers mature CRUD screens, forms, tables, filters and role-based access from your Eloquent models, with extension points where the standard pattern no longer fits (custom pages, widgets, form components). You don't build an admin from scratch; you tune an existing admin pattern. Building your own admin only makes sense if the admin is a core function of your product and differs strongly from the CRUD model, for example a trading cockpit or a visual workflow builder.
What about Laravel hosting in the EU?
Laravel Forge on top of an EU VPS (Hetzner Falkenstein, DigitalOcean Amsterdam, Scaleway Paris) is the route we use most often: affordable, fast, and EU data residency taken care of. Laravel Vapor runs on AWS Frankfurt or Ireland; Laravel Cloud is a newer managed service that we assess case by case. For healthcare or finance clients with strict isolation requirements, we deploy on a dedicated Kubernetes cluster with an ISO 27001- or HDS-certified provider.
How do you handle security in a Laravel project?
Laravel has plenty of security measures built in: CSRF protection by default, prepared statements against SQL injection, Blade escaping against XSS, and strong encryption helpers for data at rest. On top of that, we apply OWASP checks in CI, use Spatie ActivityLog for audit logging in sensitive contexts, provide two-factor authentication out of the box via Fortify or Jetstream, and run security headers through a middleware layer (CSP, HSTS, frame options, referrer policy).
Can we migrate our WordPress or legacy PHP website to Laravel?
Yes, and in almost all cases we use the strangler fig approach: we run Laravel alongside the existing application, gradually route parts of the URL path to the new stack, and deprecate the old codebase module by module. For WordPress, marketing content often moves to Statamic or another lightweight CMS, while the portal or web application part is built in Laravel with Filament. No big bang, and production stays stable throughout the project.
Does Laravel work alongside our Python data pipeline?
Yes. We see this pattern regularly: Laravel as the application layer for authentication, authorisation and UI, with a separate Python service for the heavy compute, such as machine-learning inference, data engineering and scientific computing. The integration runs through an internal REST or gRPC API, a shared queue (Redis or SQS) or a shared object store.
What about TypeScript and React in a Laravel project?
With Inertia 2, you connect React directly to Laravel controllers: you send props instead of JSON and keep server-side routing and auth. TypeScript for the frontend is standard, with type generation from Laravel form requests. For projects that want to move to a fully decoupled single-page application, we can swap Inertia for a separate React SPA with Laravel as a JSON API, but in most cases Inertia is the more productive choice.
Do you work with our in-house developers?
Almost always. We transfer knowledge throughout the project, schedule pair programming sessions with your developers, and make sure the codebase is understandable for whoever works on it after us. For longer-term support, we look at hiring a full-stack developer. The ultimate goal is always that your team can manage and further develop the application itself.
What if we want to move away from Laravel later?
Laravel is open-source PHP: no licence, no vendor lock-in on the framework itself. Your codebase lives in your own Git repository, your database is a standard PostgreSQL or MySQL cluster, and deployment runs on standard infrastructure. Where the added complexity is worth it, we keep domain logic explicitly separate from the framework-dependent layer, so a future migration to another framework or language remains possible.

Talk to us about your Laravel platform.

A no-obligation half-hour introduction. We listen to what you want to build, look at how it fits into your existing stack and organisation, and give honest advice (Laravel, Symfony, Node or a hybrid setup) rather than automatically selling our own work.

Edit content