Skip to content

Software · Product · Engineering

We build software people want to use.

Brevalen is a product and engineering company building web applications, mobile products and the systems behind them — from first idea to production.

Engagements
Product teams, embedded
Typical start
Two to four weeks
Disciplines
Design, web, mobile, backend
Based
Remote, Europe & South Asia
console.brevalen.dev/atlas/services
⌘K

atlas / services

Service health

Last 24h

Uptime

99.98%

+0.02

p95 latency

142 ms

−18 ms

Error rate

0.031%

−0.004

14:20 UTC

1,284 req/s

ingest-apiproduction142 ms
ledger-syncproduction88 ms
report-builderstaging310 ms

Trusted to turn complex ideas into usable software.

  • Product design
  • Web applications
  • Mobile apps
  • APIs & backends
  • Cloud architecture
  • Applied AI
  • Design systems
  • Data platforms

We work with a small number of clients at a time, usually as an embedded product team alongside founders and internal engineering.

Software should feel inevitable.

Philosophy

The best products don't feel designed. They feel like the only sensible way the thing could have worked. Getting there is slow, specific work: understanding the problem properly, cutting what isn't needed, then building the rest carefully.

We do that work in small teams, close to the people who will use the software, with a running build from the first weeks.

Case study · Depot

From a paper plan to a product six depots run on.

We took the whole problem — research, interface, architecture, delivery — and shipped it as one product team.

  1. 01

    The problem

    Six depots planned a day on paper. Nobody could see the whole picture.

    Depot · Tue 14 Oct

    6 routes

    06:00
    Route A · 12 stops
    08:00
    Route B · 9 stops
    10:00
    Route C · 15 stops
    12:00
    Maintenance
  2. 02

    The direction

    One screen for the plan. Everything else moved behind it.

    console.brevalen.dev/atlas/services
    ⌘K

    atlas / services

    Service health

    Last 24h

    Uptime

    99.98%

    +0.02

    p95 latency

    142 ms

    −18 ms

    Error rate

    0.031%

    −0.004

    14:20 UTC

    1,284 req/s

    ingest-apiproduction142 ms
    ledger-syncproduction88 ms
    report-builderstaging310 ms
  3. 03

    The design

    Keyboard-first interactions, designed around how dispatchers already worked.

    Depot · Tue 14 Oct

    6 routes

    06:00
    Route A · 12 stops
    08:00
    Route B · 9 stops
    10:00
    Route C · 15 stops
    12:00
    Maintenance
  4. 04

    The engineering

    Event-sourced routes, so any plan can be rewound and audited.

    Request path

    EdgeAPIQueueStoreauthzp95 142 ms · 0 dropped events
  5. 05

    The result

    A product real users run their day on, rolled out with no parallel spreadsheets.

    console.brevalen.dev/atlas/services
    ⌘K

    atlas / services

    Service health

    Last 24h

    Uptime

    99.98%

    +0.02

    p95 latency

    142 ms

    −18 ms

    Error rate

    0.031%

    −0.004

    14:20 UTC

    1,284 req/s

    ingest-apiproduction142 ms
    ledger-syncproduction88 ms
    report-builderstaging310 ms

Services

What we build

Four areas of work. Most projects touch more than one.

React · TypeScript · Postgres

src/usage/pipeline.ts
⌘K
01export const usage = pipeline(
02 source.events({ since: '24h' }),
03 group.by(['account', 'metric']),
04 rate.limit({ burst: 200 }),
05)
06

React Native · Swift · Kotlin

9:41▮▮▮

Today

$18,420

Northwind Co.+$2,400
Halden Group+$860
Vero Labs+$1,150
Approve payouts

Retrieval · Evals · Guardrails

Triage · queue 42

Refund request0.94

routed → Billing

Contract question0.88

routed → Legal

Integration bug0.41

needs a human

Go · Node · AWS · Terraform

Request path

EdgeAPIQueueStoreauthzp95 142 ms · 0 dropped events

Why Brevalen

Good software is felt in the details.

01

Clarity

Remove complexity before adding complexity. Most product problems are decision problems.

02

Craft

Every interaction deserves attention — empty states, latency, keyboard paths, the second visit.

03

Engineering

The system should be as thoughtful as the interface.

04

Partnership

Build alongside people, not just for them. We'll tell you when we disagree.

Approach

How we work

  1. 01

    Understand

    We learn the problem, the users and the business context before proposing anything.

  2. 02

    Define

    We turn ambiguity into a clear product direction, written down and agreed on.

  3. 03

    Design

    We design the experience before over-engineering the solution.

  4. 04

    Build

    We engineer carefully and iteratively, in production from early on.

  5. 05

    Refine

    We test, measure and keep improving after launch.

We keep the loop short: a working build every week, a decision log you can read, and no phase that ends in a slide deck.

Technology

Built for the real world.

We choose tools our clients' teams can still maintain in three years — and we design the whole stack, not just the surface.

  1. Experience

    Interfaces, design systems, accessibility

  2. Application

    Product logic, state, integrations

  3. Services

    APIs, jobs, events, authorisation

  4. Data

    Postgres, analytics stores, modelling

  5. Infrastructure

    Cloud, pipelines, observability

Each layer is designed to be readable on its own. No hidden magic, no framework that only one person understands.

Frontend

TypeScript · React · Next.js · Tailwind

Backend

Go · Node.js · Python

Cloud

AWS · Cloudflare · Terraform

Mobile

React Native · Swift · Kotlin

AI

Retrieval · Evaluations · Structured output

Data

Postgres · ClickHouse · dbt

Infrastructure

Docker · CI/CD · Observability

About

A small team that would rather ship one good thing.

Brevalen is a product and engineering studio. Designers and engineers work in the same room on the same problem, which is why our interfaces and our systems tend to agree with each other.

We like problems where the domain is messy and the software has to make it feel simple: operations tools, financial workflows, logistics, anything with real users who spend their working day inside the product.

We take a small number of projects at a time. We say no often. When we take something on, we treat it as ours — including the parts nobody enjoys, like migrations, access control and the third round of edge cases.

We are not interested in being the biggest studio. We are interested in the software still being good two years after launch.

Brevalen's studio: a quiet desk with a monitor showing a product interface, notebooks and printed wireframes
Design and engineering, one desk apart.

The best software doesn't ask to be noticed.

It simply makes difficult things feel easier.

Contact

Have something worth building?

Tell us what you're working on. We'll figure out the next step together — even if that step isn't us.