All articles
I design backend and AI systems on AWS that perform under real load, grow with your business, and can be operated by your own team. Built with agentic methods that add speed without costing quality.
An AI demo always works. Production is the other question. I build the infrastructure behind agentic systems: MCP servers, secure tool access, clean LLM integration into existing backends. Scalable, locked down, with costs you can predict. What goes live holds up under real load.
A process that runs on spreadsheet exports, email and three departments works until volume grows or someone is off sick. I replace it with a service that plugs into the software you already run. With permissions, a traceable log, and no tool chain that belongs to nobody.
Cloud costs grow quietly. Until the invoice hurts. I find where your budget leaks away: oversized instances, unused resources, forgotten environments. Measurably reduced, without giving up performance or availability.
The trigger is usually a date: the data centre contract runs out, the hardware is end of life, the virtualization licence suddenly costs three times as much. I plan and run the move to AWS. With the cost calculation done before the move, and a way back for every step.
Rewrites fail. Standing still does too. I modernize grown systems step by step. Day-to-day operation untouched, first measurable results from week four.
Peak traffic is not an accident. It arrives. I build backends for SaaS products and platforms that survive that moment: event-driven on AWS, in Go and PHP 8, with tenant isolation and a rehearsed recovery. Built for millions of users and for your team to run.
Greenfield build of a central, multi-tenant gRPC service in Go. A manual process spread across several departments, replaced by highly available infrastructure in the EU and the US, with a layered cache architecture delivering under 10 ms per request..
A payment API for millions of users that had stopped scaling. Every load spike was a risk, every new payment provider integration weeks of work.
A newly formed team inherited grown legacy code running revenue reporting for a global AdTech platform with nine-figure turnover. The brief: modernize it and migrate it into a scalable AWS environment while it kept running.
A pending PHP 8 upgrade was the trigger for modernizing a publishing platform grown over more than 20 years. PHP 8 migration, a new search architecture on Manticore Search, a move to Kubernetes and technical SEO work, all while the editorial team kept publishing, without a single day of downtime..
A digital catalogue written in Perl, with no real e-commerce behind it, replaced by a full in-house online shop. Deeply integrated with inventory management and point of sale, with ML-driven product recommendations and an international rollout..
I am Tim Rutte. More than 20 years in software development. Today I build business-critical systems on AWS.
What drives me: systems I touch should end up better than I found them. More stable. More maintainable. More scalable. Not for its own sake, but because bad systems carry a real cost, for teams, for budgets, and for decisions that keep getting postponed.
I work directly, with focus, and with an eye on what pays off. Technically right and commercially sensible are not opposites to me.
Remote, without overhead, since 2003.
