Web platforms with real engineering behind them.
I build custom applications where the backend actually matters — real-time data systems, payment integrations, and the infrastructure to keep them running. Not templates, not page builders. Systems you own, in code you can hand to anyone.
Systems built end to end.
Architecture, backend, frontend and the servers underneath — each of these was designed, built and deployed by me.
A search platform for UK professional firms, built around authenticated client accounts, credit-based access control and live integrations with public registers including the SRA and FCA APIs. Server-rendered PHP with a hardened admin layer.
Read case study →Built and ran a UK hosting company end to end — physical hardware colocated at Volta Data Centres in London, transit and peering arranged with Cogent, virtualisation, WHMCS billing automation and customer provisioning. Infrastructure I owned at the rack level, not a reseller panel.
Read case study →Tracks large-value Bitcoin transfers as they hit the mempool, classifies the wallets behind them, and pushes signals to a live web dashboard and a Telegram channel within seconds. Continuous ingestion, WebSocket fan-out, no polling.
Read case study →Pulls roughly a hundred RSS feeds from global publishers on a scheduled cycle, normalises and de-duplicates them into a flat-file cache, and serves seven categories plus topic routing with no database and no ad tracking. Rebuilt and migrated to new infrastructure in 2026.
Read case study →A Bitcoin-to-airtime gateway: take a digital currency payment, confirm it on-chain, then trigger prepaid mobile credit delivery across international carrier networks automatically. Payment settlement and third-party fulfilment, wired together in 2015.
Read case study →A Quran reader serving all 114 chapters from a single structured dataset, with grid navigation and instant chapter access. Content is data-driven, so the whole index can be reordered or extended from one configuration file without touching markup.
Read case study →What I'm usually hired for.
Work that needs a developer rather than a plugin — where the requirements don't fit an off-the-shelf product.
Real-time systems
Live dashboards, event streams and push notifications over WebSockets. Continuous ingestion pipelines that stay up, recover from upstream failure and don't hammer their sources.
Payments & integrations
Payment gateways, webhooks and third-party APIs wired into your own systems — with the retry logic, idempotency and reconciliation that separate a demo from something you can bill through.
Custom platforms & portals
Client portals, admin systems and internal tools: authentication, roles and permissions, audit trails and reporting. Built around your actual process rather than a template's assumptions.
Data platforms
Aggregation, normalisation and scheduled processing at volume. Turning messy external feeds and APIs into something clean, cached and fast enough to serve directly.
Legacy PHP rescue
Inherited a codebase nobody understands? I work through undocumented systems, stabilise them, close the security holes and modernise incrementally — without a rewrite you can't afford.
Infrastructure & deployment
Linux servers, web stacks, TLS, mail, DNS, CDN and backups. I deploy and operate what I build, so performance and uptime aren't somebody else's problem after launch.
Fixed scope. Visible progress. Code you own.
Scope & proposal
We talk through the problem before anything is quoted. You get a written scope with deliverables, assumptions and a fixed price — not an hourly estimate that drifts.
Architecture
Data model, integrations and failure modes agreed up front. This is where the expensive mistakes get caught, while they're still just a diagram.
Build in milestones
Work lands on a staging environment you can use throughout. Milestone payments tied to working software, so you're never paying for progress you can't see.
Launch & handover
Deployment, monitoring and a documented handover. Full source and infrastructure access transfers to you — no lock-in, no proprietary layer you have to keep paying for.
Eleven years of shipping.
I've been building and running web systems since 2015 — starting with a cryptocurrency payment gateway when that meant writing the settlement logic yourself, and later running a UK hosting company with hardware colocated in a London data centre.
That background shapes how I build. I've been the person on call when a server fails at 3am, so I write code that fails predictably and logs enough to diagnose. I've integrated payment rails and third-party APIs that break in production, so I plan for retries, partial failures and reconciliation from the start.
I work solo and take on a small number of projects at a time. You deal with the person writing the code — no account manager, no handoff to a junior team after the pitch.
- Backend
- PHP, Node.js, Python, MySQL, SQLite, REST & WebSocket APIs
- Frontend
- JavaScript, HTML5, CSS3, responsive and accessible interfaces
- Infrastructure
- Linux, Apache/Nginx, Postfix, TLS, Cloudflare, VPS & colocation
- Integrations
- Payment gateways, blockchain APIs, government & registry APIs, webhooks
Built for working with international clients.
I work in English and I’m based in Istanbul on UTC+3 — two hours ahead of London, one ahead of most of Europe. That means a normal shared working day: same-day answers, calls at sensible hours, and no waiting overnight for a reply to a blocking question.
Every project runs on a written contract with a fixed scope and milestone payments. Where personal data is involved, I work to a written data processing agreement and the transfer safeguards UK and EU GDPR require — prepared up front, not negotiated afterwards.
Tell me about the project.
What you're building, roughly when you need it, and any budget you have in mind. I reply to every genuine enquiry within one working day.
- [email protected]
- Phone
- +90 531 454 80 21
- Telegram
- @jeemo51
- Hours
- Mon–Fri, 09:00–18:00 Istanbul (UTC+3)
- Response
- Within one working day
Prefer to talk it through first? Say so in your message and I'll send a couple of times for a call.