QSP GmbH

I build the layers everyone else takes for granted.

Database, UI framework, real-time sync, container registry, gateway — written in C# and .NET, running in my own production. When off-the-shelf building blocks stop fitting, most people keep searching. I build the one that fits.

28
years of code, since 1998
5
stack layers written myself
4
products in focus

The stack, top to bottom

Most developers use these layers. I wrote five of them.

This is not a skills list. It is a map of what actually runs inside my own products — and therefore the answer to how deep I can reach into yours.

Interface L5

What the user sees and touches.

PlusUi Blazor SkiaSharp Silk.NET
Real-time sync L4

How client and server stay in agreement.

AutoPatch SignalR JsonPatch
Application L3

Where the business logic runs. The one layer I buy in.

ASP.NET Core .NET Aspire MCP
Data L2

Where everything sits once the process is gone.

SproutDB PostgreSQL SQL Server MariaDB
Delivery L1

How code becomes a running container.

Hoardr Docker Compose Azure DevOps GitHub Actions
Access & network L0

What stands between the internet and the application.

Porta ProxyPass Linux nginx

written by me, running in my own production in use

My products are my stack's first customers.

Saldra

syncs through AutoPatch, stores in SproutDB, bills through the Timelane API

ProxyPass

billing through Timelane

VerifiedApp

bills through Timelane

Every product

images from Hoardr on docker.qsp.app, access through Porta, continuously scanned by VerifiedApp

None of this is theory. Timelane issues the invoices for my entire portfolio, SproutDB holds the data, Porta carries the traffic — and when one of them breaks, I am the one who gets up at night.

Working together

How working together goes.

I either join your team as a developer, or I act as a second opinion on an architecture decision you would rather not make alone. Both start the same way: with a conversation about what the problem actually is.

After that you get an honest assessment — including when it turns out you don't need me. I take on few projects, and I take on none where I'm not convinced I'm the right person for it.

“Working with QSP is a real pleasure. QSP grasps project requirements quickly, and the solutions are well written, precise and effective.”

Peter Mann · CTO & Director, CodeBook International Ltd.
Mode
Fully remote On site for onboarding and workshops.
Billing
Hourly Based on actual effort, tracked transparently.
Selection
By problem, not by size Small projects welcome — if the problem is interesting.
Budget
Discussed in the first call Free and non-binding, around 30 minutes.
Languages
German, English
Based in
Mattighofen, Upper Austria QSP GmbH · FN 677126z · Data stays in the EU.

Products built in-house

Four products I build and run myself.

No page builder, no white-label resale. Built and supported by QSP GmbH in Upper Austria, hosted in the EU.

Working with

Klartext KI JV · Saldra Czaja AI Systems JV · VerifiedApp rc-tec GmbH Client · AT HMT Engineering Client · LU CodeBook International Client · UK

Writing

I write where I build.

No central company blog — every product has its own. That's where what actually happened during the build gets written down.

Free

Infotafel

An activity calendar that pulls together what local clubs, kindergartens and schools are offering — so parents don't have to dig through twelve newsletters. Free, no ads, no tracking. Not every project has to pay for itself.

infotafel.qsp.app →

Contact

Tell me about the problem.

Not about the solution you have in mind — we'll find that together. I answer personally, and I answer honestly, including when the answer is that you need someone else.

What the first email should say

  1. What it's about — one paragraph is enough.
  2. Where it's stuck, and what you have already tried.
  3. What timeline you have in mind.
Describe your project
First call
approx. 30 min, no obligation
Based in
Mattighofen, Austria