Specialized in .NET, system architecture and cloud, with a hands-on background in hardware and an eye for product and business. Based in Heinsberg, Germany, working with teams across Germany, the Netherlands and the EU.
Open to new projects
01 Services
Problems that stay unsolved usually sit between disciplines: code, infrastructure, devices and the business goal behind them. I work across all of them, so nothing gets lost in a hand-over.
ASP.NET Core APIs, services and integrations, built new or modernised from legacy code, with an architecture your team can keep running.
Containerised services, Kubernetes and Helm, CI/CD pipelines and observability, so deployments become boring and incidents become rare.
ESP32 firmware, BLE and Wi-Fi networking, device provisioning and edge-to-cloud integration, with one engineer for the whole chain.
02 Diagnosis
Select the symptoms you recognise. You’ll see how I would approach them, and you can send the selection to me as a starting point.
03 Case files
Every case follows the same structure: the problem, the approach, and what came out of it.
Case 01 Client work
Infrastructure for real-time video and audio communication
Angelo is easily one of the brightest software engineers I have ever met. He has helped our company Piero Infinity Control develop key software infrastructure services, always delivering elegant solutions using industry best practices. I highly recommend him to anyone looking for assistance in software development.
Case 02 Open source
High-performance Lavalink client for .NET
// Program.cs
builder.Services.AddLavalink();
// Play a track in a voice channel
var track = await audioService.Tracks
.LoadTrackAsync(query, TrackSearchMode.YouTube);
await player.PlayAsync(track);Case 03 Open source
Expose local development servers to the internet
(tunnel online @ tunnelclient 1.0.0) https://github.com/angelobreuer/localtunnel.net Tunnel Id my-app-preview URI https://my-app-preview.loca.lt/ Online since 0 days, 0 hours, 0 minutes, 11 seconds Port 44641 Max concurrent connections 10 Current active connections 2
04 The stack
Concrete tools I use in production, organised by the layer of the system they live in.
L4
Web, desktop and mobile interfaces for the systems below.
Typical workWeb apps, internal dashboards, product front-ends and companion apps.
L3
Where services run, ship and get observed.
Typical workAutomated releases, reproducible environments, incident diagnostics.
L2
APIs, business logic, data and the contracts between services.
Typical workService architecture, legacy modernisation, integrations.
L1
Firmware and connectivity, when a product reaches into hardware.
Typical workDevice firmware, provisioning and edge-to-cloud integration.
05 How I work
And you know that effort before we start. Every project begins with the goal behind it, then the system, then a written estimate.
A free intro call about the goal behind the project, then a close look at your system, code and constraints to find the actual root cause.
→ Free intro call
A written proposal with scope, risks, milestones and effort, weighed against what the result is worth to you.
→ Written estimate
Iterative delivery with visible progress every week, clean code, tests and direct communication.
→ Weekly progress
Documentation, knowledge transfer and a system your team can run and extend without me.
→ You own the result
06 FAQ
Short, direct answers for engineering leads and founders evaluating senior freelance support.
Usually when things are stuck or moving too slowly and the cost of waiting starts to hurt. I step in quickly, understand the system and take ownership, so progress picks up again without a long onboarding phase.
Most clients reach out when something is not working as expected: unstable systems, scaling issues, or integrations that keep breaking. Often there have already been attempts to fix it, but the root cause was never fully addressed. That root cause is what I look for.
I join where needed and adapt to how your team already works. You can expect clear communication, clean code and solutions your team can maintain after I am gone.
More clarity in the system, faster progress and fewer recurring issues. I focus on durable improvements, so things keep working and scale reliably over time.
No. Most problems I get called in for are not purely technical. I also help shape product and roadmap decisions where technology and business goals meet, and I look at every technical choice in terms of what it costs and what it is worth.
Mostly remote, with on-site days by arrangement when they add value, for example for kick-offs, workshops or hardware work. I am based in Heinsberg on the German–Dutch border, close to Aachen, Düsseldorf, Cologne, Maastricht and Eindhoven.
English and German, both in writing and in meetings. My working hours follow Central European Time (CET/CEST).
Ongoing support is billed on a daily or hourly rate; clearly scoped work can be done at a fixed price. After a free, no-obligation intro call you receive a written estimate with scope, risks and cost before any work starts.
Send a short description of your project. You get a reply within 24 hours with my current availability, a first assessment and proposed next steps.
Contact
Tell me what you are building and where it hurts. You get a reply within 24 hours, and the first call is free and without obligation.