Skip to main content
Web engineering

Web software that's fast, accessible, and still fun to maintain.

From multi-tenant SaaS to internal tools and immersive brand sites, we build web software on boring, proven foundations, then make the interesting parts shine.

Semantic HTML first, TypeScript everywhere, tests on every merge.

Frontend
Next.js · React · TypeScript
Backend
Python · FastAPI · Node
Data
PostgreSQL · Redis

Explore web engineering

Our default web stack

Chosen for production, hiring, and longevity, not for conference talks.

Frontend

  • Next.js
  • React
  • TypeScript
  • Tailwind CSS

Backend

  • Python
  • FastAPI
  • Node.js
  • PostgreSQL
  • Redis

Delivery

  • Docker
  • GitHub Actions
  • Terraform
  • Cloudflare

How we build for the web

We start from the people who will use the software and the work they need to do, then choose the simplest technology that does it well. Most of our web work uses TypeScript, React, and Next.js on the front end, with Python or Node services and PostgreSQL behind them, deployed through automated pipelines.

Performance, accessibility, and security are part of the definition of done, not extras. Pages load fast on real phones, work with a keyboard and a screen reader, and keep customer data safe. This website is built the same way.

Which service fits

If you needStart with
A product customers subscribe toSaaS engineering
A tool for a process off-the-shelf software can't handleCustom software
An app without app stores that works offlineProgressive web apps
Consistent, accessible interfaces across productsUI/UX & design systems
A memorable interactive or 3D experience3D interactive experiences
Confidence that releases don't break thingsQA & test automation

Every web project includes

  • Discovery with real users and examples
  • Automated tests on critical journeys
  • Performance and accessibility budgets
  • CI/CD with preview environments
  • Monitoring and error tracking from day one

How a web project runs

  1. Discover

    Understand users, workflows, and constraints; agree a first release.

  2. Design

    Prototype key screens and test them with users.

  3. Build

    Two-week iterations with demos and automated tests.

  4. Launch

    Release with monitoring, then improve from real usage.

Not sure what you need?

Tell us the problem rather than the solution. We'll suggest whether it calls for custom software, configuration of an existing tool, or an integration.

Who we work with

We work with startups building their first product, established companies replacing spreadsheets and legacy tools, and teams that need extra capacity for a specific project. Many of our web projects connect to Odoo, but plenty don't; the same engineering practices apply either way.

Performance and accessibility are features

A fast, accessible site reaches more people and costs less to run. We set performance and accessibility budgets at the start of a project, check them automatically on every change, and treat a regression like any other bug.

That includes the unglamorous details: keyboard navigation, readable contrast, sensible headings, and pages that still make sense if a script fails to load.

What we check before launch

  • Core pages load quickly on a mid-range phone
  • Keyboard and screen-reader paths work end to end
  • Forms validate clearly and fail gracefully
  • Errors are logged and alert a person
  • Backups and a rollback path are tested

Built to be handed over

We build on widely used frameworks with typed code, automated tests on the paths that matter, and documentation for deployment and common changes. Your team, or the next partner, should be able to pick it up without us. That's also why we avoid clever abstractions that only make sense to the person who wrote them.

Frequently asked questions

Do you only use Next.js?
It's our default for content and app frontends. We pick other tools when the project calls for them.
Can you take over an existing web app?
Yes, starting with a code and architecture review.
Do you design as well as build?
Yes, through design systems and UX work, or we can work from your designers' files.
How do you ensure accessibility?
Semantic HTML, keyboard testing, automated checks, and screen reader passes.
Do you host what you build?
We deploy to your cloud accounts so you own the infrastructure.
Do you build marketing websites?
Yes, when they need custom functionality, performance, or integrations. For simple brochure sites, a website builder may serve you better, and we'll say so.
Can you work with our in-house developers?
Yes. We can lead, pair, or review, and leave your team owning the code.
Do you maintain sites and apps after launch?
Yes, through maintenance plans covering updates, security patches, monitoring, and small improvements.
Can you take over a project from another agency?
Yes. We start with a code and infrastructure review, then agree a plan to stabilize and continue.
Which hosting do you recommend?
It depends on the project: managed platforms for simplicity, your cloud account for control, or self-hosting for specific policies.
Do you work with fixed budgets?
Yes. After discovery we can fix the price for a defined scope, or agree a monthly team budget for evolving work.
How do you handle SEO?
Server-rendered pages, clean URLs, fast loading, structured data, and sensible headings are part of every build. Content strategy stays with you or your marketing partner, with our support.
Can you build a customer portal on top of Odoo?
Yes. Portals that show orders, invoices, and support tickets from Odoo are a common project, with access rules enforced on the server.