Everything I have shipped.

Declare a schema once and it generates the database columns, the REST API, the typed client and an admin panel. It sits on Drizzle, Zod and Better Auth rather than inventing its own runtime. It hosts nothing and needs no key, which is the part most alternatives get wrong.

Every event gets a social space guests join by scanning a QR code. An event is a tree of spaces that changes as it moves from pre-event to live to the recap afterwards, so a wedding and a weekly pub quiz run on the same engine with different presets.

A company as a container and its staff as agents. One Bun process watches the filesystem, runs a task state machine, spawns agents across eight roles, and commits what they produce to git. The point is that the work leaves an audit trail instead of a chat log. Built on QUESTPIE.

A local control plane for coding agents. Long-running agent work falls apart when the plan lives only in a chat log, so this keeps goals, tasks, specs and evidence as Markdown on disk, with a CLI contract that Claude Code, Codex and Cursor all drive the same way.

Drizzle diffs your schema but gives you no way to write a migration by hand or roll one back. This adds both. It is the repo of mine that other people actually depend on.

A coding agent could write a change but not see whether it worked. Probe closed that: it started the dev servers, collected the logs in one place, drove a browser, and recorded flows so they could be replayed as regression checks. We built it before the coding harnesses shipped evaluators of their own. Once they did, the gap it filled closed, so it is no longer developed. The ecosystem solved the problem, which is a fine outcome.

Nutrimeals is an EIT Food backed startup putting smart canteens and connected fridges into Slovak offices. I joined as technical partner and built the app people order from and the backend behind it. It runs multi-tenant, so Nutrimeals is one tenant of a gastro platform rather than a one-off app. The app maps the fridges, shows their stock, and keeps working when the canteen has no signal.

A booking platform for accommodation, and the first big thing we built. It taught us the lesson the studio now runs on: one boxed platform for every client means every client gets a compromise. We stopped selling it and went back to building each product on its own.

Terraform for houses. You describe a residential floor plan in a small declarative language and get a model out: 14 room types, 32 materials, a PEG parser and a VS Code extension.

Social scheduling you host yourself, for people who would rather not hand their posting queue and their audience to someone else's SaaS. Superseded by Autopilot, which does the scheduling as one of the things an agent can be told to do rather than as a product of its own.

A dependency injection container small enough to read in one sitting, with sync and async resolution kept apart in the types instead of at runtime.

A reusable e-commerce template the agency could resell, rather than one shop. I built the template, the frontend and mobile side, and the payment and order flows. Over 200 of their clients run on it, and the team kept building on it long after I left. That is the only handover test that counts.

Our first client, and the one we have kept the longest. It ran for years on the booking platform we had built around it, and in 2026 we threw that away and rebuilt the site on QUESTPIE as its own thing. A cabin that takes bookings does not need someone else's idea of what a booking is.

The planning module for the bureau's venue platform.

Filling in an accident report at the roadside, on a phone, with the details already there. Private drivers use their own data; a company owns a fleet, drivers join it with a code, and the report pulls the holder details from the company and the driver details from whoever is logged in. Shipped to both stores, now at v1.13.

Modulario is a low-code platform for building business systems. I built the Schenker logistics module and the integrations around it, and designed the MongoDB schemas the enterprise data sat in.

A usability testing platform. I built respondent recruitment against the Cint supplier API, the CRM for a client's own respondents, and a NestJS service that drove moderated sessions through the Zoom API.

CODEUPP brought QUESTPIE in as extra capacity on a build they could not staff. We started with a full audit of the codebase, then worked through it in stages, fixing the developer experience as we went and shipping features on top of it rather than after it.

An AI meal planner for households, aimed at cutting what they throw away. It suggested what to cook from what was already in the kitchen, and worked offline first because people plan meals standing in front of a fridge.

A portal for children and young people who have lost someone. Alongside the counselling and library sections it has a place to light a candle and a timeline that follows grief over time, so the build was as much about tone and WCAG 2.1 AA as about the CMS behind it. Runs on QUESTPIE.

A full platform redesign with a CMS the editors run themselves: multi-language content with an approval step before anything goes live, and a blog rebuilt so it can be found. Built and handed over; the client has not put it live yet.