Projects

Systems in daily use, and the servers underneath them

Some of this was built for a client and runs inside their business. Some of it I built, launched and still operate myself. And some of it is not a screen at all: the servers, the mail and the backups that keep the rest reachable. All three are on this page, because leaving the third one out would hide the part that is hardest to copy.

Three kinds, all on this page

KindWho runs it
Built for a clientTheir business
Built, launched and still operated by meMe
The servers, the mail and the backups underneathMe

The third one is not a screen, and that is exactly why it is here: leaving it out would hide the part that is hardest to copy.

Built for a client

Running inside somebody else's business

Four businesses in two countries run part of their working day inside something I built. Two of them are car rental companies, and the second one came because the first one worked.

Custom operational platform, food production and deliveryIn daily use

PizzaMania B2B Platform

Every order in the business, from the moment a customer places it to the moment it is invoiced, moves through one system that six different roles use every day. Nobody phones anybody to ask where something is.

6roles, from the customer placing an order to accounting
Its own serverset up, hardened and operated by me
Dev, UAT, Proda release flow, not a file copied onto a live machine
What is in it
  • B2B ordering with a status the customer can see, instead of calling to ask
  • Commercial rules, prices and contracts configured once, applied everywhere
  • Production planning and delivery documents generated, not retyped
  • Automated jobs and notifications, so nobody has to remember to check
The system significantly improved our processes, reduced manual effort and increased operational transparency.
Owner and Managing Director, food production and delivery
See how it was built
Booking platform with payments, RomaniaLive

KronPara SRL

The business now sells while it is closed. Somebody buys a flight at two in the morning, pays by card, and the owner wakes up to a paid order. The date is still agreed by phone afterwards, because the weather decides it and the software was built to respect that rather than fight it.

Sells while closedorders and payments arrive at night and at weekends
Paid before the flightmoney is in the account before anyone leaves the ground
What is in it
  • Takes money at two in the morning, on a day when nobody would have answered the phone
  • Payment lands before the flight, instead of being collected at the landing field
  • Gift vouchers became something they can actually sell, especially before Christmas
  • The owner changes a price in the middle of a season himself, without asking anyone and without paying for it
See how it was built
Bilingual site with an admin panel, car rentalLive

DS Services SRL

A customer picks their dates and sees which cars are actually free, instead of phoning to find out. The company answers from a panel where the fleet, the prices and the availability are theirs to change, and nobody pays a developer to change a price.

Fewer wasted callsthe site answers what is free before anyone picks up
Never promised twiceone car, one booking, no apology
What is in it
  • Customers see what is free before they ask, so fewer calls end with "sorry, that one is taken"
  • A car cannot be promised to two people, which used to cost an apology and a customer
  • Longer rentals price themselves, so the discount conversation stops being improvised each time
  • Every enquiry lands in one place with a state, so none is lost in an inbox on a busy Friday
See how it was built
Landing page, car rentalLive

Elite Class Rentals

A rental business that lives on search. The whole job is that somebody looking right now finds the page, reads it before losing patience, and feels safe leaving a phone number.

Findable and fastpage body prerendered, images converted, sitemap and structured data
What is in it
  • Enquiries reach the owner by email in seconds, timestamped in their own timezone
  • The form is rate limited, so it cannot become somebody else’s megaphone
  • Legal identity and data handling stated where a customer can find them
And othersNot shown

Work that stays off this page

Not every client is here. Some are covered by confidentiality agreements, and their work stays off a public page for as long as those agreements say so. If what you need resembles something you cannot see here, ask, and I will tell you whether I have done it before.

Built and operated by me

The hardest things on this page

Nobody commissioned these, nobody paid for them, and nobody else has to keep them running. They sit in the same industry as one of the clients above, and as one that cannot be named. That is the point: a school, its bookings, its recordings and the camera that films them are four parts of one operation, and I have built all four.

SaaS platform, event capture and deliveryLive with real users

SmartStream

Footage is captured out in the field, often where there is no signal, and it is available to the people who were there within seconds of the event ending. It was proven in one sport and built for none: anywhere a session is recorded and the people in it want to see it while it still matters.

Minutes, not daysbetween doing something and being able to review it
Recording never waitsa connection is needed to deliver, not to capture
What is in it
  • An operator records where there is no coverage and never has to think about it, because the upload waits and catches up on its own
  • Nobody spends an evening copying files off a card, renaming them and sending links one by one
  • Each organisation and each person sees only what is theirs, so nobody has to police it
  • A participant reviews their own session before the next one, which is when it still changes something
See how it was built
Computer vision and hardwareIn development, personal R&D

SmartTrack

A camera that holds a moving subject in frame at high zoom, for a whole day, with nobody behind it. The mount, the electronics, the tracking and the zoom control were all designed from scratch, because nothing off the shelf did it. Built in my own time.

Hardware and softwareboth designed from scratch
First field testtracking, zoom and motor control worked together
What is in it
  • Custom motorised mount, designed in CAD and 3D printed
  • Subject tracking and zoom control running on the device itself
  • Aimed at a setup with no operator at all, feeding straight into SmartStream
See how it was built
SaaS platform, school operationsIn development

SmartGlide - Paragliding School Operations Platform

A flying school runs an entire day of operations from one screen: who is flying, with which instructor, on which equipment, whether the checks were done, and what the log says afterwards. Safety-critical coordination that used to live on paper and in somebody’s memory.

What is in it
  • Students, events and instructors managed together instead of in three separate lists
  • Safety checks and flight logs recorded where they can be found again
  • Weather, airspace, communication and reporting brought into the same view
  • One isolated environment per school
See how it was built

Not a screen

The part that has no interface

Everything above this line runs somewhere, and somebody set that somewhere up. It is the least visible thing on the page and the hardest to imitate, which is why it comes last and not in a footnote: it is the answer to what happens after the launch, on every project above.

Servers

Set up once, deliberately, and written down

Each server has its own documented role, a hardening record with what changed and how to undo it, and a health check installed on the machine itself rather than in somebody's notes.

What is in it
  • Key access only, root login disabled, the password left valid only in the provider's recovery console
  • A written standard, with a conformance table per server, so a gap is visible rather than remembered
Backups

Off site, encrypted, and isolated per server

One central backup hub in a different country, with a separate sub-account for every server, so a server that is compromised cannot reach anybody else's backups.

What is in it
  • Rotating retention: ten days, four weeks, six months
  • Immutability through snapshots, so a deletion cannot propagate
Mail

Client domains sending from infrastructure I run

Two of the businesses on this page send their mail through a mail server I operate, on their own domain. A confirmation, a receipt, a password reset: the messages a business cannot afford to lose land in the inbox instead of in spam, because somebody looks after SPF, DKIM and DMARC, the unglamorous records that decide whether mail is believed.

See managed hosting and security