Dark Blue
Two team members chatting on a sofa, one working on a laptop. Software Engineering.

Software Engineering

We're a technical partner to some of the world's biggest companies. People like Intuit, Deliveroo, Omnicom and GroupM trust us to build and look after their websites, tools and platforms.

Our developers aren't tied to one language or framework, so every project starts with the right tools for the job. Most of the time that's React and Next.js, with Sanity as the CMS. It's fast, secure and widely used, so you're never locked in to us.

Launch is covered too, from content migration to redirects and DNS. Afterwards we're on hand with hosting, support and 14 days of aftercare.

  • Fast, secure websites that your team can update without a developer. Built with React, Next.js and Sanity, with solid SEO and accessibility foundations from day one.

    Learn more

Software Engineering projects

  • Fintech & BankingUX & Product DesignMachine Learning & AI

    QuickBooks

  • Food & DrinkUX & Product DesignBrand & Visual Design

    Deliveroo

  • SportsMedia & EntertainmentAudience Research

    New York Yankees

Common questions on "Software Engineering"

What tech stack do you build with?

Modern JavaScript, usually React with Next.js, styled with Tailwind. We stick with widely adopted, well-supported tooling so the code we hand over stays maintainable and you can hire for it later.

Where a project genuinely calls for something different, we use something different — we're technology agnostic rather than locked into a house framework.

Why do you recommend Sanity as a CMS?

It's headless, so your content sits on separate infrastructure from the public site — that alone removes a large class of attacks on the published application. Editors preview changes before publishing, and most people are comfortable with it within ten minutes.

Server updates, backups, versioning and image handling become Sanity's responsibility rather than a maintenance line on your budget. A single day of agency support on any one of those tasks costs more than years of hosting.

Can editors update the site themselves without a developer?

Yes. We build sites from a library of content blocks, from simple layout blocks through to one-off components for specific parts of the site. Editors combine them to create new pages on their own.

The library grows as the site does, and when further development is needed, existing blocks can usually be reused or extended rather than rebuilt from scratch.

How do you approach security?

A lot of it comes from the CMS itself: enterprise authentication, access control you can grant and revoke yourself, and no database for an attacker to inject into.

On the application we use a Content Security Policy and the recommended security headers, and we host on established platforms like Vercel and Cloudflare, which keep their own hardware and software current. Traffic runs through Cloudflare, giving us DDoS protection and visibility into what we're blocking.

How do you handle performance and SEO?

We build to score well against Core Web Vitals and Lighthouse, and give editors a dedicated interface for the metadata on every page, article and case study.

Accessibility and schema markup are part of the build itself rather than a pass we do at the end.

Want to chat about a build?

Give our founder, Iggy a shout…

iggy@wearedarkblue.com