---
title: "Web"
updated: "2026-11-16"
url: "https://www.etheon.com/services/web"
---

# Web application development

Web development, from web apps to design systems. We build web apps, SaaS platforms, online stores and the design systems behind them.

[Contact Us](https://www.etheon.com/services/web?start=1&service=web)

### Web apps.

Portals, dashboards and tools that run in the browser, fast on every screen.

- Server-rendered and static pages
- Accessible to WCAG 2.2 AA
- Analytics only after consent

### SaaS.

Platforms with accounts, billing and roles, built to grow.

- Accounts and roles
- Billing
- Built to grow

### E-commerce.

Stores that load fast and check out cleanly.

- Pages that load fast
- A clean checkout

### Design systems.

Tokens and components that keep every page consistent.

- Tokens
- Components
- Their documentation

### Web apps. Portals, dashboards and tools that run in the browser, fast on every screen.

#### What it is

A web app is software your customers or your team use in the browser: a portal, a dashboard or an internal tool. We build web apps that render on the server for speed, meet WCAG 2.2 AA, and load analytics only after a visitor consents.

#### What we do

- Server-rendered and static pages
- Accessible to WCAG 2.2 AA
- Analytics only after consent

#### How we do it

1. Map the users and tasks: Who uses the app, and what they must get done.
2. Design: Screens and a design system, agreed before the build.
3. Build: Server-rendered pages, accessible and fast.
4. Release: In stages, each measured against its budgets.

#### Questions

**Can you take over an existing web app?**

Yes. The takeover plan on this page lists what we check first.

#### What you get

- The web app and its source code in your repository
- An accessibility and performance report at launch

#### Stack and tools

- Web frameworks
- Server rendering
- Accessibility checkers
- Consent management

#### Related

- [AI integration](https://www.etheon.com/services/ai?detail=integration#integration)
- [Cross-platform apps](https://www.etheon.com/services/mobile?detail=cross-platform#cross-platform)

### SaaS. Platforms with accounts, billing and roles, built to grow.

#### What it is

A SaaS platform is software you sell by subscription, with accounts, roles and billing built in. We build the platform and the parts every customer touches, so it can grow from its first customer to many without a rewrite.

#### What we do

- Accounts and roles
- Billing
- A platform built to grow

#### How we do it

1. Scope: The accounts, roles and plans the first release needs.
2. Build the core: Sign-in, roles and billing before the features.
3. Ship: The first customers on board, then the next release.

#### What you get

- The platform and its source code
- Accounts, roles and billing, documented

#### Stack and tools

- Web frameworks
- Authentication
- Billing platforms
- Databases

#### Related

- [Kuest AI, an AI tutor that teaches step by step](https://www.etheon.com/work/kuest-ai)
- [Product engineering](https://www.etheon.com/services/software?detail=product-engineering#product-engineering)

### E-commerce. Stores that load fast and check out cleanly.

#### What it is

An online store has two jobs: show products fast and take payment without friction. We build stores whose pages load quickly on every device and whose checkout is short, clear and tested end to end.

#### What we do

- Pages that load fast
- A clean checkout

#### How we do it

1. Map the catalogue: Products, prices and stock, and where they come from.
2. Build the store: Pages that load fast on every device.
3. Test the checkout: Every step, on the devices your customers use.

#### What you get

- The store and its source code
- A checkout tested end to end

#### Stack and tools

- Commerce platforms
- Payment gateways
- Site search
- Performance monitoring

### Design systems. Tokens and components that keep every page consistent.

#### What it is

A design system is the shared set of tokens and components that keeps every page of a product consistent. We build the tokens, the components and their documentation, and this site runs on its own design system, shown further down this page.

#### What we do

- Tokens
- Components
- Their documentation

#### How we do it

1. Audit: The colours, type and components already in use.
2. Define the tokens: One set of values every component reads.
3. Build the components: Each with its states, its story and its test.
4. Document: How and when to use each part.

#### What you get

- The tokens and components as a package
- Documentation for designers and engineers

#### Stack and tools

- Design tokens
- Component libraries
- Documentation tools
- Visual testing

#### Related

- [Discovery and design](https://www.etheon.com/services/software?detail=discovery#discovery)

## Fast and accessible, measured. Here is this page, measured in your browser as you read it.

- Largest contentful paint: Budget 2.5 s
- Interaction to next paint: Budget 200 ms
- Cumulative layout shift: Budget 0.1

Accessibility. Checked against WCAG 2.2 AA on every release.

Measured on this visit with the browser's Performance API. Nothing is sent to us.

### Speed and accessibility. What fast and accessible mean, and how this page measures itself.

#### What it is

Speed and accessibility decide whether people can use a site at all. We set a performance budget for each kind of page and test every release against WCAG 2.2 AA; this page measures its own speed in your browser, as you read it.

#### What we do

- Hold every release to its budgets
- Check every release against WCAG 2.2 AA

#### How we do it

1. Set the budgets: A budget for each kind of page, agreed with you.
2. Measure: Speed checked in the browser, on real devices.
3. Test accessibility: Against WCAG 2.2 AA, with screen readers and keyboards.
4. Hold each release: A release over its budget waits until it is fixed.

#### Questions

**Do you build accessible sites?**

Yes. We test every release against WCAG 2.2 AA: screen readers, keyboard use, contrast and text size, on the real pages.

#### What you get

- A performance budget for each kind of page
- An accessibility issue list against WCAG 2.2 AA

#### Related

- [Quality assurance](https://www.etheon.com/services/software?detail=qa#qa)

## Design systems. Tokens and components that keep every page consistent. These are this site's own.

[Read more](https://www.etheon.com/services/web?detail=design-systems#tokens)

## Taking over a web app. What we check before we change a line.

1. Repository and dependencies audit. You receive: a report
2. Accessibility audit, WCAG 2.2 AA. You receive: an issue list
3. Performance baseline. You receive: a budget
4. Deploy pipeline. You receive: a runbook
5. Analytics and consent. You receive: a consent map

[Contact Us](https://www.etheon.com/services/web?start=1&service=web&tab=takeover)

- [Software](https://www.etheon.com/services/software): Custom software and products
- [Cloud](https://www.etheon.com/services/cloud): Cloud, DevOps and SRE