Skip to content
Development

Laravel development by senior developers in Norway

Web applications and APIs in Laravel, one of the most widely used PHP frameworks, built by senior developers who have worked with it since it launched in 2011.

  • Laravel 13 and PHP 8.5
  • Octane and FrankenPHP in production
  • Norwegian integrations ready to go

We build and run systems for

  • GlobalConnect
  • Sykehusinnkjøp
  • Home_Net
  • Telia

What we build in Laravel

From a single API to a full SaaS platform, with code that’s easy to maintain for years.

  • Web applications and SaaS

    Customer portals, line-of-business systems and SaaS platforms with sign-in, roles and payments.

  • APIs

    REST APIs with Sanctum for mobile apps, partners and other systems.

  • Admin and internal tools

    Inertia and React give admin panels that behave like an app, without a separate API in between.

  • Queues and background jobs

    Horizon and Redis handle heavy jobs such as PDFs, email and imports in the background.

  • Real time

    WebSockets with Laravel Reverb for notifications, chat and dashboards that update themselves.

  • Takeovers and upgrades

    We take over existing Laravel projects, clean up technical debt and upgrade to the latest version.

Connected to Norwegian services

We have our own packages for the Norwegian services most businesses need, so integrations go in quickly and safely.

  1. BankIDSign-in and signing with the Norwegian national e-ID, over OIDC.

  2. Vipps MobilePayPayments, recurring charges and sign-in.

  3. Tripletex and PowerOffice GoOrders, invoices and payroll kept in sync with the accounting system.

  4. Bring, PostNord and PorterbuddyShipping, labels and tracking.

Built in Laravel, with 100 in all four Lighthouse categories

The site you’re reading is built in Laravel with Inertia and React. This is how we took it from 90 to 100.

In depth

Laravel in practice

Laravel is the most widely used PHP framework in the world, and it's what we use to build web applications, customer portals and APIs. Our developers have worked with Laravel since it launched in 2011.

We pick tools based on what the project needs. For many Norwegian businesses Laravel is a good choice: it's quick to get started, security is built in, and the code stays easy to maintain for many years.

When is Laravel the right choice?

Laravel works well when a system has a lot of business logic, related data in a database and integrations with other systems. Typical examples are customer portals, line-of-business systems, booking systems and SaaS products with sign-in, user roles and payments.

Most of what you need is built into the framework, including queues for heavy jobs, scheduled tasks, email, notifications, caching and authentication. That leaves more time for the parts that are specific to your business.

Laravel isn't always the answer, though. If you need a website with a lot of editorial content, WordPress is often a better fit. If you need to train your own machine-learning models, we build that part in Python and connect it to Laravel.

PHP works for large systems too

Plenty of people still think large systems have to be built in .NET or Java, and that PHP is only for simple websites. That isn't the case. VG, Norway's largest news site, and much of Schibsted run on PHP, and both Facebook and Slack started out on it.

Laravel builds on that with current PHP 8, typed code and thousands of ready-made packages. We use it for systems that handle many concurrent users and are as easy to change after five years as after five weeks.

Faster from idea to launch

The basics of a new system, such as sign-in, access control, database setup and email, are in place in Laravel from day one. In our experience that can cut development time by up to 50% compared with similar .NET projects:

  • Security: SQL injection, XSS and CSRF are blocked by default.
  • Databases: Eloquent keeps queries readable, which means fewer bugs.
  • Queues: PDFs, emails and imports run in the background, so users don't have to wait for them.

As a result, more of the budget goes on the features users actually notice.

Inertia or a separate API?

One of the first decisions in a Laravel project is how the frontend talks to the backend. With Inertia we build the interface in React, but the pages get their data directly from Laravel. You get one codebase, no separate API to maintain, and a web application that feels like an app. It works well for admin panels, customer portals and internal tools.

If a mobile app, partners or other systems need the same data, we build a standard API with Sanctum instead. We often end up with both: Inertia for the web application and an API for everything else.

What affects the price?

Our hourly rate starts at NOK 1,500, and projects with a clear scope get a fixed price. The cost of a Laravel project depends mostly on three things: how many integrations it needs, how many user roles and permissions it has, and whether data has to be migrated from an existing system. After a short discovery phase you get an estimate, so you know what you're getting before we start.

Taking over and upgrading Laravel applications

Many businesses have a Laravel application that's a few years old and whose original developer has moved on. In that case we start with a technical review. We read the code, look at dependencies, tests and hosting, and give you a prioritised list of what needs doing. The list is yours to use, whoever ends up doing the work.

We upgrade one major version at a time, and before we start we write tests for the most important user flows. That's how even old Laravel 5 projects get safely up to Laravel 13 and PHP 8.5.

When an older PHP application moves to Laravel, we migrate it piece by piece. The old and new versions run side by side until everything has moved, so users don't notice the switch.

Norwegian integrations

Almost every Norwegian system needs some of the same integrations. We have our own packages for the most common ones, so they're quick and safe to put in place:

  • Identity: BankID, the Norwegian electronic ID, for sign-in and signing over OIDC.
  • Payments: Vipps MobilePay, for payments, recurring charges and sign-in.
  • Accounting: Tripletex and PowerOffice Go, for orders, invoices and payroll.
  • Shipping: Bring, PostNord and Porterbuddy.

Hosting and performance

Standard PHP boots the application from scratch on every request. With Laravel Octane and FrankenPHP it's loaded into memory once and stays ready:

  • Faster responses: the boot time disappears from every request.
  • More users per server: the same hardware handles far more concurrent users.
  • Lower power use: efficient code uses less energy in the data centre.

We run the applications on Kubernetes in the EU/EEA, with automated deploys that don't cause downtime. Horizon shows how the queues are doing, and monitoring alerts us before users notice a problem. Read more about infrastructure and DevOps, or see how we reached 99.99% uptime with Kubernetes.

Security and privacy

Laravel protects against the most common attacks, but security depends just as much on how an application is built and run. We keep the framework and packages up to date, scan dependencies for known vulnerabilities and give each user only the access they need.

Personal data is stored in the EU/EEA. We build in logging, deletion and data access requests so you can comply with GDPR. Interfaces are built to WCAG 2.2 AA, so they work for everyone and meet accessibility requirements.

How we write Laravel code

Code should be as easy to change in five years as it is today, so we stick to a few habits:

  • Tests: Pest tests for every important flow, run automatically before each deploy.
  • Static analysis: PHPStan, and a consistent code style with Laravel Pint.
  • Clear structure: validation in Form Requests, heavy work in queues and thin controllers.
  • Code review: another senior developer reads the code before it goes to production.

Everyone on our team has more than ten years of experience. You won't get juniors on the project, and you won't lose time to handovers along the way.

Our stack

These are the tools we use in most Laravel projects, layer by layer.

Wondering whether Laravel is right for your project? Book a chat and we’ll go through it together.

How we work

Book a call
  1. success criteria

    Insight and scoping

    We find out why the system is needed, who will use it and what success looks like.

  2. data model

    Architecture and technology

    We sketch the data model, choose the technology and plan security, privacy and accessibility early.

  3. regular releases

    Development in short iterations

    You see working software often and can adjust course along the way.

  4. ongoing
    automated tests

    Operations and maintenance

    Readable code, automated tests and a structure that’s easy to change later.

    ongoing

Frequently asked questions

Why choose Laravel over other frameworks?

Laravel lets you build quickly and still copes with large systems. The framework is mature, the documentation is good, and there are ready-made packages for most needs. For PHP projects it’s often the safest choice.

Can you take over an existing Laravel project?

Yes. We start with a technical review of the code, dependencies, tests and operations, and then propose the way forward.

What does Laravel development cost?

Our hourly rate starts at NOK 1,500. Projects with a clear scope get a fixed price, and you get an estimate before we start.

Which Laravel versions do you work with?

New projects start on Laravel 13 and PHP 8.5. We upgrade older projects one major version at a time, with tests along the way.

Do you use Inertia.js or API-first?

It depends on the project. For admin panels and internal tools we often use Inertia with React. For mobile apps and integrations with other systems we build plain APIs.

How do you test and deploy?

We write tests with Pest, and a pipeline runs them before every deploy. New versions go out with zero downtime.

How do you handle operations and hosting?

We can run the Laravel application on our own Kubernetes infrastructure, or set it up on Laravel Forge, Vapor or another cloud platform.

Who owns the code?

You own the code we write for you, and it can live in your own repository if you prefer.

More specialist areas

Planning a Laravel project?

Tell us about the project, and we’ll work out together whether Laravel is the right choice.