Platforms · Applications · Websites
Foundations already running in production, AI-accelerated delivery, and architecture a human is accountable for.
— Small team / Direct with the engineers / You own the code
What we build
We start from foundations already running in production, so your budget goes into what is actually yours — not into plumbing you would be paying us to rebuild.
Data layer through to interface: search, integrations, background jobs, and the infrastructure to keep it running.
React · Postgres · Kubernetes
The internal tool your industry actually needs — leads, deals, inventory, invoicing, permissions, an audit trail. Built around how you work rather than around a template.
Postgres · Role-based access · Audit logs
iOS and Android from one codebase, sharing types with your backend so the two cannot drift apart. Through the stores, or over the air.
React Native · Expo · TypeScript
Fast, prerendered sites that load instantly and cost almost nothing to run. Content you can edit yourself, in as many languages as you need.
TanStack Start · Tailwind · Cloudflare
Our work
Products we own, work we did for clients, and the tools we publish. Each one says which it is.
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
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
A specification for describing tabular datasets, with reference implementations in TypeScript and Python.
we author
The site you are reading. Prerendered in two languages with translated URLs, served as static files from the edge, and built on the same stack we sell.
we built
How we work
Most software projects go wrong in the same three places: nobody agreed what finished meant, nothing was visible until the end, and the client could not run the result without the people who built it.
We agree what finished looks like before the first commit. If we cannot estimate something confidently, we say so rather than padding the number.
Something you can open and click, every week. No long silence ending in a demo that turns out to be the wrong thing.
Your repository, your accounts, your infrastructure, from the first day. Handed over with documentation and tests — not rented back to you.
The difference
We are the people writing the code, not a layer in front of them. Here is what that actually changes.
How to start
You will know what it costs and how long it takes before you commit to anything. The scoping call is free and there is no obligation after it.
A few sentences is enough: what you want built, roughly when, and what it has to do.
Free, about an hour. We work out what is tractable, what is not, and what the hard parts really are.
A written scope with a fixed price and a delivery date. If something cannot be estimated confidently, we say so instead of guessing.
Weekly increments in your own repository, then documentation, tests and a handover to whoever maintains it next.
The principle
Software you cannot run without us is not finished. Everything we build ends up in your repository, on your accounts.
— How we decide what finished means
Writing
· news
Introducing Extension DP (Data Package Extension Template), a GitHub repository template for rapid Data Package extension development.
· news
dpkit is a fast data management framework built on the Data Package standard and Polars DataFrames, for CSV, JSON and Parquet, with CKAN and Zenodo support.
· news
Data Package export is now publicly available on zenodo.org. You can export any dataset as a data package or access it programmatically using a direct endpoint.
Get in touch
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.
