Skip to content
Development

Full-stack developers from database to screen

Senior full-stack developers take the whole application, from the database to what users see. You don’t have to wait for one team to finish before the next can start.

  • 10+ years of experience, no juniors
  • One developer from sketch to production
  • Laravel, React and TypeScript

We build and run systems for

  • GlobalConnect
  • Sykehusinnkjøp
  • Home_Net
  • Telia

What our full-stack developers do

The same people own the whole application, so the parts fit together and nothing falls between two teams.

  • End-to-end development

    One team builds the whole application, from the data model in the database to the buttons on screen.

  • The modern monolith

    Laravel and React in one codebase with Inertia, without a separate API just to fetch your own data.

  • APIs when you need them

    Clear API contracts when mobile apps, partners or other systems need the same data.

  • Responsive interfaces

    Applications that work just as well on phones, tablets and large screens, built to WCAG 2.2 AA.

  • DevOps from day one

    CI/CD, automated tests and containers are there from the start instead of arriving as a separate project later.

  • Takeovers

    We take over applications whose original team is gone, and keep building in every layer.

Typical full-stack projects

We fit best when the application matters to how your business runs and has to be maintained for years.

  1. MVPs and prototypesA first version that looks finished and can be tested on real users.

  2. Customer portalsSign-in, orders, documents and payments in one place.

  3. Line-of-business systemsInternal tools that replace spreadsheets and manual routines.

  4. SaaS productsProducts with subscriptions, roles and many customers on one platform.

A modern monolith with 100 in all four Lighthouse categories

The site you’re reading is a single codebase with Laravel, Inertia and React. This is how we took it from 90 to 100.

In depth

Full-stack in practice

At PXL, the same people build the whole system, from the database to the browser. Every one of our full-stack developers has more than ten years of experience, and they know how a change in the database affects an animation in the browser, and the other way round.

Development has long been split between the people who make things look good (frontend) and the people who make things work (backend). When those two groups don't talk to each other well, you get bugs, delays and expensive misunderstandings.

What is a full-stack developer?

A full-stack developer works in every layer of an application: the interface in the browser, the business logic and APIs on the server, and the database underneath. Many people assume that means a generalist who knows a little about everything. For us it means senior developers who know the whole stack well.

When the line between frontend and backend disappears, so does the waiting. You don't pay for a frontend team to sit idle while the backend team finishes its part. One of our developers can take a feature from sketch to finished code in production.

It also means fewer bugs. The person who changes the database table also writes the controller and the form the user fills in. Nobody has to interpret a specification someone else wrote, and nothing gets stuck between two teams.

Full-stack developers or separate teams?

A full-stack team works best when you're building or extending one application and want a small team that owns all of it. That covers most customer portals, line-of-business systems, SaaS products and MVPs. Each feature is delivered finished through every layer, and you have one point of contact.

Separate frontend and backend teams make more sense when you already have a large team on one side. They also make sense when the interface and the system behind it are meant to evolve independently. In that case we can cover the side you're missing, frontend or backend.

Why we often build a monolith

For years the trend has been to split applications into lots of small services (microservices) and separate single-page applications. Companies like Netflix and Uber need that. For most Norwegian businesses it mainly adds complexity and technical debt they don't need.

We often prefer what we call the modern monolith. Inertia.js lets us use React or Vue on the frontend while keeping the simplicity of a classic server application in Laravel. For you, that means:

  • No unnecessary APIs: we don't have to build and maintain a complex API just so the frontend can fetch data from its own backend.
  • Security on the server: sign-in and permissions are handled on the server, without complicated token handling in the browser.
  • Shorter development time: with no second codebase to keep in sync, we ship features up to twice as fast as traditional headless teams.

We choose the technology that solves your problem best. Whether something else would look better on a CV doesn't come into it.

When do you still need an API?

The monolith suits the web application, but in many systems other parties need the same data. A mobile app, a partner or an accounting system needs an API with clear contracts.

In that case we build a separate API alongside it, with versioning and documentation, so the people using it can rely on it not changing without warning. We often end up with both: Inertia for the web application and an API for everything else. Because the same team builds both, they share business logic, validation and tests.

From idea to MVP

If you have an idea, we'll help you boil it down to its core. What's the smallest thing we can build to find out whether the idea is worth pursuing?

A full-stack developer can quickly put together a prototype that looks and feels like a finished product, with real sign-in, real data and real payments if you need them. You test the idea on users instead of on a slide deck. If the answer is yes, you keep building on the same code.

Scaling and maintenance

When the users arrive, the system has to cope with them. We optimise database queries, move heavy jobs into queues and add caching where it makes a difference. We also set up the infrastructure to scale automatically as traffic grows. Because the same team knows the whole stack, we find bottlenecks quickly, whether it's a slow query, a heavy page in the browser or a server running out of memory.

A system that isn't maintained falls apart. Frameworks and packages need updating, security holes need closing, and the business will want new features. You don't need a new team for each layer of the system, and you avoid handovers where knowledge gets lost. Read more about how we run our systems under infrastructure and DevOps.

What does a full-stack developer cost?

Our hourly rate starts at NOK 1,500. You can hire us by the hour for ongoing development and maintenance, or we can take on a defined project at a fixed price when the scope is clear.

The cost of a full-stack application depends mostly on how many user roles and screens it has, how many integrations it needs, and whether data has to be migrated from an existing system. An MVP with a clear goal costs less than a business system replacing several old tools. After a short discovery phase you get an estimate, so you know what you're getting before we start.

Taking over existing projects

Many companies have an application whose original developer has left. Others have one where the frontend and backend were built by separate teams that no longer exist. We can take over either and keep developing it.

We start with a thorough code review to understand the system. We look at the code, dependencies, tests and hosting in every layer, and only suggest improvements once we know how it all fits together. You get a prioritised list you can use whoever does the work.

Security and privacy

When one team owns the whole system, one team is also responsible for security in every layer. Sign-in and permissions live on the server, each user only gets the access they need, and we keep frameworks and packages up to date.

Personal data is stored in the EU/EEA. We build in logging, deletion and data access requests so you can comply with GDPR. If you need an independent review, we have separate IT security services.

Quality in every layer

The code behind the scenes should be as tidy as the interface is polished. That's why we stick to a few habits:

  • Tests: Pest tests for the backend and tests for the frontend, run automatically in CI/CD before every deploy.
  • Static analysis: PHPStan and TypeScript catch errors before the code runs.
  • Code review: another senior developer reads the code before it goes to production.
  • Deploys: containers and Kubernetes, with new versions going live without downtime.

The interfaces we build are responsive and meet WCAG 2.2 AA, so they work on any screen size and for all users. You won't get juniors on the project.

Are we the right fit?

PXL is a good fit for businesses building something their operations depend on. If you need a simple blog, we're probably more than you need, and WordPress is often a better choice. If you're building a business system, a customer portal, a SaaS product or another application your business relies on, that's what our full-stack team does best.

We're based in Hamar, speak Norwegian and know how Norwegian businesses work. To see how a monolith performs in practice, read how we got this site to 100 in Lighthouse.

Our stack

These are the tools we use in most full-stack projects, layer by layer.

Have an idea, or a system that needs a steady team? Book a chat and we’ll look at it together.

How we work

Book a call
  1. smallest testable version

    Narrow down the idea

    We find the smallest thing we can build to test whether the idea holds up.

  2. data model

    Data model and architecture

    We sketch the data model and decide how frontend and backend fit together.

  3. working features

    Whole features at a time

    Every delivery goes through all layers, so you can test something that works.

  4. ongoing
    same team

    Scaling and maintenance

    The same team tunes, updates and keeps building as the users arrive.

    ongoing

Frequently asked questions

What is a full-stack developer?

A developer who works in every layer of an application: the interface in the browser, the logic and APIs on the server, and the database. With us that means senior developers with deep knowledge of the whole stack, not generalists who know a little about everything.

What are the benefits of full-stack development?

When one team owns the whole stack, the road from idea to production gets shorter and the application hangs together from database to screen. You also avoid most of the misunderstandings between a separate frontend team and backend team.

What does it cost to hire a full-stack developer?

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 technology stack do you use?

We prefer Laravel with React, TypeScript and Tailwind CSS, but we adapt to what you already have. We also work with Node.js and Vue.

Can you take over existing projects?

Yes. We start with a thorough code review to understand the system, and only suggest improvements once we know how it fits together.

What is a modern monolith?

An application where backend and frontend live in the same codebase. With Inertia we build the interface in React while the data comes straight from Laravel, with no separate API in between.

Can you build an MVP quickly?

Yes. We help you find the least that has to be built to test the idea, and set up a first version that looks and feels like a finished product.

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

Need full-stack developers?

Tell us about the project, and we’ll work out together how to take it from idea to launch.