Introducing dpkit Terminal and TypeScriptSee the announcement
Datist

What we build

Multi-platform products

One product across a consumer site, an operator dashboard, a mobile app and partner microsites — sharing one data model, so they cannot drift apart.

starts fromdatist · pricing
€10,000
fixed price from
4 weeks
delivery from
Both agreed in writing before anyone starts

What it is

One system that appears in several places at once: a public site, an internal dashboard, a mobile app, and sometimes a site per partner on their own hostname. Each surface has its own audience and its own permissions, and every one of them reads and writes the same data.

What you get

One data model and one set of API contracts behind every surface, so changing a rule changes it everywhere rather than in the three places somebody remembered. Permissions that differ per surface without a second authorisation system to keep in step.

How we build it

Contract-first, with the types generated from the contract and shared across web, mobile and the backend, so a mismatch between two surfaces is a compile error rather than a support ticket. Mycarro runs a consumer marketplace, a dealer back office and per-dealer microsites off one schema; the regulated platform runs an operations dashboard and an iOS and Android app off one contract-first backend.

Where we have built it

capturemycarro.app
The Mycarro car search engine as it runs today, searching across its live Portuguese listings.

Mycarro — car marketplace and dealer CRM

A used-car marketplace live in Portugal. Consumer search over listings gathered from across the market, a dealer back office for leads, inventory and invoicing, and a mobile app — built end to end.

we built

under NDA
Work we cannot show
ND

NDA — Swiss fintech platform MVP

Lead architect on a regulated financial services platform: a contract-first backend, an operations dashboard, and an iOS and Android app. MVP delivered.

client · NDA

What we build it on

  • Full-stack web applications

    Server-rendered React with typed routing and data loading in one project, not two.

  • Mobile & desktop

    Native apps sharing the web product's types and rules instead of forking them.

  • Typed APIs

    One definition generating the server, the client and the docs, so drift is a build error.

  • Identity & access

    Sign-in, organisations and permissions bought in rather than rebuilt badly.

Get in touch

Tell us what you need built.

We are a small team in Portugal, working London hours. A site, an app, an internal tool, or the platform behind them — start with a sentence about the problem and we will take it from there.

Start a conversationView on GitHub
All services
Get a quote