Products

I build products the same way I run programmes: the interesting version is the one that survives contact with a real user, so each of these has been pointed at a real problem before it had a landing page. None is on general sale. Where a launch date exists I’ve said so; where it doesn’t, I’ve said that too.

If one of these is closer to your problem than a consulting engagement is, get in touch — early access is a conversation, not a waiting list.

GeoDrillDraw drawing a lithological borehole section and casing diagram in a browser tab

GeoDrillDraw

Working application · in development

Borehole logs and well-casing diagrams, in a browser tab.

Every water-well project produces the same two drawings: the λιθολογική τομή, showing what the drill passed through layer by layer, and the σωλήνωση, the well-casing and piezometer construction diagram. The software for producing them is desktop software — Windows-only, installed, tied to one machine. The observations are made somewhere else entirely: at the wellhead, in a site office, in a truck.

GeoDrillDraw produces both drawings in the browser. No install, no account, no server — and because there is no server, nothing is uploaded.

  • Twelve standard Greek materials, one click each
  • Piezometer and monitoring-well arrangements
  • Vector SVG and PDF export
  • Imports legacy .gdr files
  • Greek and English
  • Not on sale
Virtual Food Studio showing generated dish photography produced from a parsed menu

Virtual Food Studio

Live application · in development

A restaurant’s menu in. Professional dish photography out.

Photograph or paste a menu, and it parses the dishes and generates food photography for each one — in a chosen style, and optionally anchored to the restaurant’s own dish photos and venue so the results still look like the real place. Print-ready menu and a ZIP of the images at the end.

For a small restaurant the alternative is a photographer for a day, a stylist, and a shoot that covers a fraction of the menu. This covers all of it, and can be redone when the menu changes.

  • Menu parsed from a photograph or paste
  • Style selection per shoot
  • Anchored to the venue’s own photos
  • Print-ready menu plus a ZIP
  • Every model call runs server-side
  • Not on general sale
Diagram: a daily check-in call, and the three independent channels it escalates through

The Caretaker

MVP in build · not accepted yet

A companion and safety net for people who can’t have someone with them around the clock.

The elderly first, but the same need exists for anyone living semi-independently — with a disability, a chronic illness, or a recovery that isn’t finished. It runs a daily check-in call in Greek or English, and if the check-in fails it escalates through three independent channels rather than one. It also remembers previous conversations, so it’s a presence rather than an alarm.

This is best-effort assistance, not a medical or emergency device. It complements emergency services — it never replaces them, and every user is told so directly.

  • Daily call in Greek or English
  • Three independent escalation channels
  • Remembers previous conversations
  • Cloud-first and model-agnostic
  • Safety spine code-complete, 193 tests passing
Four before-and-after pairs of restored family photographs

Replay the Past

Moving toward public launch

Point your phone at an old printed photograph and get it back as if it were taken today.

No scanner, no upload queue, no editing skills. A photograph of a photograph is enough — the restoration handles the fading, the creases, the colour shift and the loss of detail that fifty years in a drawer produces.

Built as a progressive web app so there’s nothing to install, with every model call running on the server. No API key ever reaches the browser.

  • Works from a phone photo of a print
  • Progressive web app — nothing to install
  • Full test suite
  • Model calls run server-side
Diagram: fifteen inheritance steps grouped into four phases, with the roles that share the case

Οδηγός Κληρονομικής Διαδοχής

In development · pending legal review

Fifteen steps, one family, one shared view.

A Greek inheritance is a sequence: ληξιαρχική πράξη θανάτου, πιστοποιητικό εγγυτέρων συγγενών, αποδοχή, δήλωση φόρου, κτηματολόγιο. Fifteen steps across four phases, and typically several relatives, a δικηγόρος and a συμβολαιογράφος all holding different pieces of it. Families lose time not because the steps are hard, but because nobody has the whole sequence in one place.

The app gives them one shared case: fixed roles, per-step file uploads, a comment thread on each step, and timing derived from the case rather than from memory.

It is not legal advice, and it does not replace the δικηγόρος or the συμβολαιογράφος — it keeps the family organised around them.

  • One shared case, not per-person checklists
  • Roles including δικηγόρος and συμβολαιογράφος
  • Files attached to the step that produced them
  • A comment thread per step
  • Nothing ships until a practising Greek lawyer reviews the process model
Google Takeout to Markdown converter, running locally in four steps

Google Takeout → Markdown

Working application · in development

Your Google export, as files you can actually read.

A Google Takeout archive arrives as a pile of split ZIPs full of formats built for machines. This merges the parts, walks you through four steps — upload, configure, convert, download — and gives back clean Markdown: Gmail, Keep, Photos metadata and the rest, in files that drop straight into Obsidian, NotebookLM or any AI assistant.

It runs entirely on your own computer. A Google export is among the most personal archives a person owns, so nothing is uploaded anywhere: the app is a local web UI in front of a local processor.

  • Merges split archives
  • Four steps: upload, configure, convert, download
  • Clean Markdown out
  • Runs entirely on your own machine
Diagram: anything captured goes in as it arrived, is categorised automatically, and is retrieved by asking

Cortex II

Running as a working system

Capture once, organise never.

Personal knowledge management fails at the filing step. Cortex II removes it: notes, files and documents go in as they arrive, get read and analysed on the way in, and become searchable by meaning rather than by remembering where you put them. You ask it questions instead of browsing folders.

Answers come back with citations to the items they were drawn from, so you can check the source rather than trust a summary.

  • Text, voice, camera images, files and PDFs
  • No folder or tag decision at capture
  • Automatic project/area/resource/archive structure
  • Search by meaning, not exact wording
  • Answers cite your own items
  • Productisation not started
Diagram: 1,083 documents and 13.5 GB in, a reconstructed inventory of accounts, policies, vehicles and properties out

Estate Analyzer

Pre-MVP · in active development

What someone leaves behind, turned into something their family can use.

After a death, the hard part is rarely the paperwork you know about. It’s the account nobody mentioned, the subscription still billing a closed card, the portal login that exists only on a sticky note. Estate Analyzer ingests the documents, photographs and cloud exports and reconstructs a searchable, categorised picture of the accounts, assets and obligations that make up an estate.

It was built against a real estate rather than from a specification, which is why it survives the input real estates actually produce.

Local-first by design. The database is a file on your own machine; the only thing that leaves it is document text sent for processing.

  • Classifies each item and recognises duplicates
  • Phone photographs treated as a normal input
  • Searchable, categorised estate view
  • Local-first: the database is a file on your machine

Nothing here is for sale yet. If one of them is the shape of a problem you have, tell me about it — that is how these get built.