Web applications
Django platforms with a real data model behind them: back office, business rules, REST API, authentication, subscriptions and the administration screens that go with them.
Web platforms and mobile applications, designed and written in house — from the data model to the store listing. Five of them are below; the same team builds yours.
One team across the whole stack, which is what makes an application reach a store rather than stop at a prototype.
Django platforms with a real data model behind them: back office, business rules, REST API, authentication, subscriptions and the administration screens that go with them.
React Native applications published on the Play Store — and on the App Store from the same codebase — including signing, store listings and release management.
Document collection and indexing, semantic search with citations, entity extraction, LLM pipelines that answer from your own corpus instead of from the open web.
Mapping, hexagonal indexing and position checks, deployed on containerised infrastructure that we also operate once it is live.
Defence intelligence, sport, urban play, music education. The domains differ; the way they are built does not.
Open-source intelligence platform with hybrid FR/EN retrieval
Collects, indexes and cross-reads open sources for a given domain, then answers analyst questions with cited documents.
Read moreCommunity atlas of outdoor sport spots
A mobile guide to outdoor sport spots - surf, sailing, climbing, running - described and rated by the people who practise there.
Read moreA photo hunt through a city, one place at a time
The app shows photographs taken somewhere in a city; players go to each place, stand there and take the picture themselves.
Read moreLearning to sing, on your own, with feedback
A singing course on your phone: graded exercises, your voice recorded and analysed, a repertoire that grows with you.
Read moreIntelligence fusion and effects simulation for planning
Turns multi-source intelligence into a geospatial picture, then propagates the effects of competing courses of action across it.
Read moreWhat the application has to do, for whom, and what is deliberately left out of the first version.
A usable version early, on real data rather than on mock-ups, so the decisions are argued from something that runs.
Deployment, store publication, accounts and payments, legal pages: everything that stands between a working build and a live product.
Hosting, monitoring, updates and the next version — or a clean handover to your own team, documentation included.
Projects are quoted individually, after a short framing conversation about what the application has to do and who will use it.