← Labs · the three

Labs · the whole product

Platform Development

Web and app from one core. One build, one standard.

The site your clients read and the app your people carry are not two projects — they are two faces of one system. We build them on a single measured core, so they never drift, and one hand answers for the whole of it.

You are reading one of ours — built, not themed; served from the edge — ·

One core, two surfaces

The site and the app read the same truth. Change it once, and both move together.

THE CORE one contract · one source of truth 🌐 WEB SURFACE HTML · server-rendered at the edge · 0 JS 📱 APP SURFACE Rust core · native · works offline ONE GATE neither surface ships below the line Two vendors give you two truths that drift. One core gives you one.

Measured, not claimed

Four figures from a platform built as one.

1
core
one contract feeds both surfaces — the site and the app cannot disagree
0
drift
change the truth once; the web and the app both move, in the same commit
100ms
to first paint
the same budget gate stands over both — slow never ships, on either face
1
hand answers
one engineer signs the whole system — no seam to point fingers across

The build — one core, two surfaces, one gate

The same four pieces that make this real. Read them in order: the truth, the two faces that obey it, and the gate that lets neither ship slow.

// MatchTop · the core — one definition both surfaces obey.
// Written once. The portal and the field app read the same truth — they cannot drift.

type Case = {
  id:       Uuid,
  status:   "open" | "review" | "closed",
  locale:   Locale,        // one language list, honoured by both surfaces
  updated:  Instant,       // stamped at the edge — one clock for web and app
}

service Portal {
  get  case(id)           -> Case
  list cases(for: Holder) -> Case[]
}

What cannot be copied

Why one house for the whole beats two vendors stitched at a seam.

Two vendors
One platform, here
The truth
The web team and the app team each keep their own copy — and they drift by the week.
One core. The site and the app read the same definition, so there is nothing to drift.
When it breaks
The site blames the API, the app blames the site, and you sit in the seam between them.
There is no seam. One engineer built both faces and answers for the whole system.
A change
Two backlogs, two sprints, two invoices — and a release where only half of it moved.
One commit moves both surfaces together. The gate holds them to the same line.

This is not a discount for buying two things at once. It is a different shape: a single system with two faces, not two systems taped together. A shop that sells the site and sub-contracts the app cannot hand you one core — they do not have one. That is the part that cannot be out-bid.

Held in confidence

Before a line is written, how your work is kept. This part is not negotiable.

Yours alone

An NDA is the default here, not an upsell. What you share is read by one engineer and no one else — nothing is sold, shared, or passed on.

NDA by default · one reader · never resold

Your keys, your data

Credentials and records stay in your house, under least privilege. We keep no copy we do not need, and nothing leaves your reach without your word.

Least privilege · no hoarding · your house

Readable, not blind trust

What runs in your house is yours to read and audit — no black box you must trust unseen. The engine room stays ours; what you run is yours.

Auditable · no black box · signed

Tell us what must be built.

The whole product, in two lines. We read them ourselves and answer ourselves — there is no queue behind this window.

It reaches one person, and that person answers. Nothing here is shared, sold or passed on.

Mr. MatchTop · matchtopalgorithm.ai