Back to home

One Mac mini runs the company.

No platform bill that grows with traffic. A single machine in Tallinn runs every site and service, a standby server outside the home network is ready to take over, and tooling we wrote ourselves keeps both healthy without anyone watching.

services, 25 environments
21
health checks in a week
~250,000
deploys recorded since May 2026
411
of media on the CDN, inside the free tier
~30 MB

Figures from our own monitoring database, read on 26 October 2026.

The path of a request

VisitorA browser anywhere
Cloudflare
EdgePages pass through, media stops here
TunnelDialled out from home, no open ports
Media cacheA Worker serves images, video and fonts from R2
Home, Tallinn
Mac miniWeb server and every service

What keeps it running

  1. 0165 KB/supload from home, too slow to serve media

    The edge

    Nothing at home listens on the open internet. One Cloudflare tunnel carries traffic for 25 hostnames to a web server on the Mac. The Mac's upload through the tunnel is slow, about 65 KB/s, so images, video and fonts never come from it: a small Worker serves them from R2, reads through to the Mac on a miss, rechecks freshness every ten minutes per location and falls back to the Mac on any error.

  2. 0263 saverage successful deploy

    Deploys

    A deploy builds with secrets pulled from an encrypted vault (AES-256-GCM), writes into a fresh folder, swaps it in atomically and restarts the service. If several changes arrive at once, the latest wins. A failed install is retried once. The average successful deploy takes 63 seconds.

  3. 0360 sbetween health checks, every environment

    Watching itself

    Every environment is health-checked every 60 seconds. Two failures in a row send an alert to a phone, and error rates in the web server logs raise alerts too. Services run under launchd with KeepAlive, so a crash is a restart, not an outage.

  4. 042 minbetween watchdog runs

    Repairing itself

    A watchdog runs every two minutes and restarts the web server or the private network if they stop answering, with a ten-minute cooldown so it cannot thrash. A separate check confirms every deploy is still healthy every 15 minutes.

  5. 05~5task board sweeps a day

    Agents on the dross

    Routine work goes to automated harnesses. An agent sweeps the task board about five times a day, closing what is verifiably done and flagging what is not. Others keep the books and draft routine replies. Decisions, taste and anything a customer sees stay with a person.

  6. 060per-request fees

    What it costs

    No per-request pricing and no fleet to rent. The running costs are a few small subscriptions, one small standby server and the electricity for one Mac mini, so nearly all of what a product earns is margin. It also means a product can stay alive for years without needing to grow to pay its hosting bill.

If the Mac mini goes down

Mac mini, TallinnServes everything day to day
Edge watchdogChecks from outside both machines
Standby serverTakes over after 5 minutes down

A single machine at home would be a single point of failure, so it has a standby. A rented server outside the home network keeps an up-to-date copy of every public site, forms included. A watchdog on Cloudflare's edge, independent of both machines, checks the sites from outside. If they stay unreachable for 5 minutes, it moves traffic to the standby on its own, and moves it back once the Mac answers again. The same server also runs the heavier work: high-load services, APIs for larger enterprise applications and customer-facing services.

Have something worth building?