I build it myself, and I'm ten minutes away

Background

I've spent my career building backend systems for banking and fintech, where an integration that works most of the time is an integration that doesn't work. Payment rails, identity systems, the plumbing nobody sees until it fails. Day to day I work in .NET and Next.js, with PostgreSQL behind most things.

The other half of my work is AI image and video. I run a production pipeline across the current generation of image and video models, and I've built a library of tools for campaign direction, storyboards and photoreal rendering. It's why Plaios projects look finished rather than functional.

Why Plaios

Every small business I talked to had the same two things: AI tools that did one job, and a chat window where the founder re-explained the company every morning. What was missing was the layer underneath, the business written down so the AI could read it, connected to the tools, keeping a record. I built that for myself first. Then for a physiotherapy practice. Then it became the product.

Plaios runs on its own AI operating system. This site was planned, researched and written inside it. The demo you'll see is that workspace, doing its normal work.

How I work

• Demos and build sessions happen in the evenings and at weekends, and I'll say that plainly on the first call. The build is done with you, in sessions, not disappeared into for a month.
• Malta first. In person for anyone here, remote across Europe.
• Fixed written quotes before any work. No retainer required to keep what you've got.
• You own everything: the folder, the code, the accounts.
• If a chatbot would do, I'll tell you, and point you at a cheaper way to get one.

Elsewhere

LinkedIn is where the build logs and teardowns go. Email is hello@plaios.com.