Projects · In-house R&D

We research before we build.

Every product starts as a question. We investigate it, prototype an answer, build the ones that hold - and ship them to the Apps page. This is the workbench: the research and the building, in the open.

The pipeline

From a question to a shipped app.

Four honest stages. A project only appears once it has something real to show.

01

Researching

A question, investigated. Findings, no committed build.

02

Prototyping

Testing an approach in a rough build to see if it holds.

03

Building

Committed and in active development - also on the Apps page.

04

Graduated

Shipped as an app. The Apps page becomes its home.

Nothing here yet - the first graduation will be Kept.

In the pipeline

What we're working on, and why.

Researching Informs the whole catalogue

The question

Is the old trade-off between intelligent and private still real - or is it collapsing?

What we found

For most of the cloud era you could build software that was intelligent or private, not both. That trade-off is now narrowing for a specific class of work - latency-sensitive, privacy-critical, structured around your own data - so a privacy-first product can finally offer understanding, not just storage, without sending anything anywhere.

Working paper · June 2026 The Edge Moves In How intelligence is migrating to the device, and what it means for privacy-first software. Read the paper ›
Prototyping Early development

The question

Can a story-driven, narrative path take a true beginner to real coding fluency where reference-style courses lose them?

Where it stands

Foundations is built and running - proving the story-driven approach with real learners. The rest of the curriculum is early and phased, with no launch date and no research paper yet. We'd rather prove the idea than rush the rest, which is why it sits here rather than on the Apps page.

Working paper Story-driven learning How a narrative path can teach a beginner to code - being written up. In progress
Building Becomes Kept

The question

Why does so much life admin - warranties, receipts, documents, subscriptions, expiry dates - slip through the cracks?

What we found

The failure is not discipline, it is architecture: the records that govern your obligations are scattered with no trusted home, the consequences of losing track arrive late, and nothing watches a deadline before it lapses. The analysis points to a single, private, on-device system of record that does the watching - and prepares the action for you to approve.

Working paper · June 2026 The Unkept Life The cognitive burden of life admin, and the case for a private, on-device system of record. Read the paper ›
Building Becomes Veyago travel

The question

Why do group trips stall in decision paralysis - and could a swipe-and-eliminate mechanic turn that into a shared decision?

Where it stands

Group trips stall not on logistics but on the decision: where do we even go? The working thesis is that a four-round elimination bracket turns paralysis into a decision a group can actually reach together. The full research write-up is in progress.

Working paper The decision problem Why group trips stall, and the bracket thesis - being written up. In progress

Research index

The papers behind the products.

Long-form working papers - the research that justifies each build. More as we publish them.

Building in the open

Follow the build.

We'd rather show the work than a highlight reel. For investors and partners weighing what's next, the research above is the honest version of where we are.