What's possible

Concept work runs alongside the client work here: things built to find out how far something goes. Three of them below.

NPAural

Custom store, built from scratch and run by me: product pages, Stripe checkout, customer accounts, licences and downloads. This one sells six audio plugins for macOS, Windows and Linux, three of them free, three paid.

Alongside, a synth is in the works, meant to take drum & bass and electronic music in a new direction.

• Checkout:Stripe, right on the page. Paid once, no subscription.
• Account:One login for licences, approved machines and downloads.
• No dongle:The licence is a signed file the buyer's own machine checks against a key built into the binary. No account inside the plugin, works offline.
• The products:Every plugin is C++ on DPF, built from one codebase for VST3, CLAP and AU.

trydotto.live

The precursor to an app in the store, built in the browser because everything that gets expensive after submission can be answered here: how the environment feels, which interactions people actually accept, where they drop out. What holds up here goes into the app; what doesn't cost nothing but the week it took to build.

The shape it runs in: a dot on a screen. Every so often it goes hollow, leaving a couple of seconds to tap. A tap at any other moment, one missed dot, or leaving the screen ends the run. Nothing in it distracts — the phone it runs on already does that.

• The engine:Pure TypeScript with the clock and RNG injected, so a whole run is deterministic and testable without a browser.
• A test inside the test:Half of all sessions never get asked to predict how long they'll last. The arm is sticky and rides on every event, so the funnel splits by it and the mechanic has to earn the friction it adds.
• Analytics with nothing to consent to:No cookies, no device storage, no person profiles, EU host. The Meta pixel is geo-gated at the edge and never loads in the EU, so the page needs no banner.

Automated content pipeline

Runs a niche Instagram account on its own: finds topics, writes, renders, blind-judges its own output and only then publishes. Each further account is a folder with its own voice, niche and credentials.

The framework is deliberately plain. How fine the output gets depends on the effort put in, not on the architecture.

• Topics:A miner pulls threads from the niche's subreddits, an LLM distills them into concrete pain and wish signals.
• Voice:The writer is locked to one system prompt per account, so every post sounds like the same character.
• Render:Carousels in headless Chromium, reels from a script, TTS voiceover, stock b-roll and captions as a 9:16 MP4.
• Judge before publish:A blind multimodal judge scores every finished piece, anything below the threshold is discarded.
• Autopilot:A daily planner spreads the slots, a per-minute ticker generates, judges and posts just-in-time.
• Learning:Every week reach, saves and shares flow back, re-weight formats, shift posting times and hand the writer fresh angles.

All three are examples, not a ceiling. If something surfaced while reading — an idea, a process that eats a day every week, a thing nobody is sure is even possible: let's talk about it.