Solo engineer, shipping production code since 2003. I write the code, run the boxes, and pick up the pager. 40+ servers under management across 8+ datacenters, eight production ML services, multi-source data warehouses — kept alive by one person who knows every layer.
Every figure below comes from infrastructure I personally provision, patch, monitor and back up. These aren't claims — they're the contents of a running operations log.
Stylised view of a single platform I run end-to-end: parsers feed a master DB, ML enriches lots, an internal API serves three consumer products, edge proxies bypass regional blocks, and a backup orchestrator pulls everything home every 30 minutes.
Five active verticals. Some are public products with my name on them; others are operational platforms for businesses across LatAm, Asia and Europe. All shipped, all running, all watched by me.
End-to-end ingest: 24+ parsers across multiple regions and verticals, normalised into a unified data model, served via internal REST APIs to multiple consumer products and mobile apps.
Eight production ML services on a single GPU server. Not Jupyter demos — FastAPI endpoints behind health probes, deployed via Gitea Actions, tracked in MLflow.
Multi-source ETL into 4.6 B+ rows across two ClickHouse warehouses. Custom analytics UI with a natural-language → SQL → chart pipeline powered by GPT and a read-only SQL validator.
Operations as a first-class deliverable. Two independent monitoring stacks, custom backup orchestration, edge proxies, ISP-grade subscriber control planes (RADIUS, Juniper provisioning), bare-metal hosting because cloud bills are not a feature.
WebSocket pipes that survive proxy bans and exchange rate-limits. Multi-exchange aggregation, copy-trading routing, payment gateways, on-chain wallet monitoring — for platforms where milliseconds and uptime equal money.
Internal workbenches with role-based access, KPI dashboards, approval workflows. Multi-brand mail infrastructure (IMAP/SMTP daemons), recruitment data scrapers, trader desks — boring, lean, kept simple.
No religious wars. Node for I/O, Python for ETL and ML, Go where latency matters, PHP for classic sites and admin panels, bare-metal where the cloud bill stops being a feature.
Roles that map to deliverables. I can step into any of these on day one and stay there for years.
Design data flow, service boundaries, ownership lines, failure modes. Pick the right database and the right protocol the first time, not the third.
Write the React component, the API endpoint, the SQL migration and the deploy pipeline in one branch. No handoffs, no waiting on another team.
Provision bare-metal, set up TLS, harden SSH, schedule backups, watch metrics, get paged at 3 AM and fix it before sunrise. Day-zero through year-five.
Build ETL that survives schema drift. Tune MySQL replication, partition ClickHouse, model warehouses for analysts that actually want to query them.
Not "we'll train a model." Models behind FastAPI, version-pinned, health-probed, retraining tracked, costs monitored. The model is the easy part; shipping it is the job.
For founders without a CTO: I'll spin up the whole technical side, take it to product-market fit, and either hand it cleanly to a team or keep running it.
Servers across 3 continents, products in 7+ countries, fluent in shipping under sanctions and through every kind of regional friction.
Not a manifesto. The actual heuristics that let one person hold this much production code in their head.
I write code knowing I'll be the one paged a year later. That changes how careful you are about logs, defaults, and silent failures.
Vanilla PHP, FastAPI, nginx will outlive any npm apocalypse. I add libraries when they pay rent, not when they're popular.
Tests fail — you fix the code. Data lost — you're done. Backup orchestration is the first thing I set up, not the last.
I don't watch dashboards. Systems write me on Telegram when something breaks. Anything else is dashboard theatre.
Anyone can train a YOLO. Putting it behind FastAPI, version-pinning, monitoring drift, autoscaling on a GPU box you actually own — that's the job.
Bare-metal that I rack-monitor myself beats a cloud bill that doubles every quarter. Boring tech that I've run for a decade beats hype tech the conference loved last week.
Legacy CMS rewrites (WordPress · Bitrix · Joomla). Pure design without code. Native Swift / Kotlin from scratch. Gambling, casino, NFT / Web3 launches, equity-only deals. Micro-tasks. Cowboy-rescue jobs without discovery — we look at the state first, then talk numbers.
Long-running projects where I own code AND operations. Serious platforms under NDA. Systems built to run for years. With a normal contract and a real client behind it.
I take on a small number of projects at a time. If you need someone who can own the full stack from the bare metal up — write.