Three tracks, because they answer three different questions: do I ship for paying clients, do I build without a brief, and do I keep systems running over time. Everything listed here exists. What does not exist yet is not listed.
Paid work for real businesses, all live, all reachable under their own name.
Marketing site for a Vienna-based outdoor-surfaces cleaning business operating across Vienna, Lower Austria, Burgenland and Carinthia — terraces, driveways, stone and concrete surfaces, walkways, green areas. Clear structure, fast load times, inquiries straight through the site instead of phone tag.
Direct inquiries instead of a phone chain — web presence and lead channel in one.
Marketing landing page I built for a friend — his Carinthia-based nonprofit is a curated member community for young founders, athletes, and ambitious 18- to 30-year-olds. Concept, design, and build end-to-end.
Entry point for member inquiries and community communications.
Competent execution — I will absolutely recommend Benjamin.
Marketing landing page I built for a friend running a 360° virtual tours and drone videos business in Austria. Concept, design, and build end-to-end — a practical example of how I approach a landing page.
Central inquiry channel and online presence for the business.
Genuinely strong work! The SCANZY website is modern, clear, and immediately makes you want to see more. Design and structure fit the offering perfectly — you instantly understand what SCANZY does. Very happy, a clear recommendation!
Projects with no client attached. They answer whether I build when nobody is paying.
End-to-end web app showcase — calendar app with multi-device auth, email reminders and a bilingual UI. Evidence of web app work beyond marketing sites.
Showcase for cleanly built web apps — full stack from a single hand.
Market analysis for investment property in Carinthia. A daily full crawl of two property portals pulls in every listing; duplicate listings of the same object are merged into one real property instead of skewing the statistics. That builds time series of gross yield and price per square metre, against which my own portfolio can be measured against the market median. Server-rendered HTML, deliberately without a client framework. Running daily since July 2026, private for now.
Buying decisions measured against real market data instead of gut feeling.
This site. Astro 6 on a hand-written CSS token system, no framework, no tracking, bilingual with its own voice per language. Design system, content, build, and operation all in the same hands.
The page you are reading right now.
Not built and handed over, but kept running: servers, network, and services I maintain myself and repair myself when they break. The date on each line is the actual evidence.
running since
Rented EU cloud server carrying my own agent and automation layer: crons, briefings, repo upkeep, monitoring logic.
Deliberately kept apart from client hosting, so a fault in the automation can never touch a client site.
running since
Self-run deploy platform on a rented EU cloud server. Client and personal web applications run in containers, each with its own TLS certificate.
The machine behind the hosting offer.
running since
Repurposed desktop hardware serving as a private media and file server, a second location, and a place to test things.
Reachable only over the private network, no open access from outside.
running since
Connects servers, workstations, and mobile devices into one encrypted private network. Administration and data sync run entirely across it.
The only things reachable from the public internet are the ones that are supposed to be.
running since
Self-hosted invoicing instead of a SaaS subscription (Invoice Ninja): e-invoices in the European standard format as hybrid PDFs with embedded XML and a payment QR code.
My own bookkeeping actually runs on it, starting with the first invoice on setup day.
running since
Watches every operated service and backup chain and alerts on failure (Uptime Kuma, self-hosted). New services get a monitor by default.
In July 2026 it surfaced a silent backup failure that would otherwise have gone unnoticed for weeks.
running since
Own build: a self-healing backup chain that mirrors database dumps and user data to a separate offsite target every night, with a real write test before each run.
It aborts on error instead of reporting success, so the monitoring picks it up. Written in July 2026 straight out of a real failure.
Three pieces of work broken down: what had to be solved, how I built it, what with, and what actually shipped.
SCANZY sells 360° tours, drone flights, and FPV cinematics to hotels, real estate, and hospitality. The product is visual, the previous site did not pay the promise. Brief: deliver the premium story in five seconds without sliding into agency-showreel optics, and keep the established industry routes (hotel, real estate, restaurant, Carinthia) intact in the header.
Editorial dark hero with the drone footage as signature element, brand system in midnight navy, cream gold, and a warm cream background (Edition 2026 PDF as canon). Source Serif display with gold italics as recurring accent motif, deliberately not Fraunces. Industry routes for real estate, hotel, restaurant, and Carinthia landings preserved in the header, legal pages tidy alongside.
Brand system locked into code, not only in the PDF. Central inquiry channel; the founder has been actively recommending the work onward since then ("design and structure fit the offering perfectly").
Calendar apps like Google or Outlook pull events, reminders and auth into someone else's ecosystem. I wanted hard evidence that I can build and run a full web app end-to-end, with no vendor in between: frontend, backend, database, auth, mail, deploy.
Next.js on the front, NestJS on the back, Prisma over PostgreSQL. Own session-based auth instead of a third-party provider, multi-device, email reminders via SMTP. Bilingual UI (DE/EN), dark and light themes. It ran as a demo on my own Hetzner infrastructure; the code is public.
A reference app: every layer (auth, ORM, UI, mail, deploy) can be followed in the code.
Stock dev-portfolio templates sell the wrong thing: Geist plus Geist Mono is the AI-template default, "trusted by" walls are the agency reflex, animated gradients the showreel reflex. An offer built on recurring care for small landing pages needs a visual layer that reads as calm, precise, trustworthy, not as a cursor-blob showreel.
Self-hosted Astro 6 site with a hand-written CSS token system (no Tailwind, no framework), a single ink-blue hue (oklch 248°), General Sans Variable plus Commit Mono instead of the Geist default, asymmetric editorial layout instead of centred bullet grids. Bilingual DE/EN, each with its own voice rather than a one-to-one translation. Contact form with honeypot plus per-IP rate-limit, SMTP via nodemailer, no third-party transactional service. No tracking, no third-party fonts.
The page right here. Lighthouse mobile consistently ≥95 on Performance, Accessibility, Best Practices, SEO. Brand and tooling layer carry the offer instead of just illustrating it.