Own products and client work
Software & tech Software, websites and complex SaaS products
I build software — for companies and for myself.
Architecture, code and operation come from one place: from the website to the online store to the platform that has to keep running. Under the Nexentrium brand, products of my own grow out of the same work.
What I have built
The home pages as they look today, and the engineering behind them.
Nexentrium
Nexentrium
The brand my software products are built under, with a website in German and English.
Technically interesting
- A typed dictionary makes the type check fail as soon as a translation is missing.
- The home page is a scroll film: the wheel scrubs camera moves generated for it, with a keyframe every eight frames so every seek lands at once.
- One check run of build, type check, lint and tests that stops at a single warning.
- Next.js
- TypeScript
- Tailwind CSS
- Vercel
What I build
Software for companies
Internal tools, portals and automations built around the way a business actually works, rather than the way an off-the-shelf product expects it to.
Complex SaaS products
Platforms with several tenants, roles and permissions, billing and interfaces. Products that run around the clock and grow with the people using them.
Websites and online stores
From the first line of code to hosting. This website and my own stores run on code I wrote myself.
Interfaces and automation
Inventory, payment providers, shipping, accounting: systems that never met before pass the data along instead of someone retyping it.
Portals and logins
Closed areas for clients, staff or applicants, with logins, permissions, files and messages. The client portal on this website is one of them.
Operation and maintenance
Hosting, backups, updates and monitoring. Whoever builds an application has to keep it alive, or launch day stays its best day.
How this website works
From a push to an inquiry in the inbox.
Your request
Browser
Every address is a finished HTML file. The text is in the first byte, before any JavaScript runs.
Tap or point at a building block.
This website in numbers
Counted in the repository, not estimated.
1,934
pre-rendered pages
8
languages
547
redirect rules for the old WordPress site
61
automated checks in every build
450
checks of the PHP API
4,041
images in several widths
1,201
merged pull requests
As of 13 October 2026
What every build checks
Before a change goes live, guards run over images, copy, languages and links.
Available for your project
Companies hire me when off-the-shelf software has stopped fitting.
I take a project on end to end: clarify the requirements, design the architecture, build it, ship it and run it. You get one person to talk to instead of an agency, a developer and a host passing the blame between them.
One pair of hands
Concept, development and operation stay with the same person.
Not a kit
The application follows your process, not the other way round.
Open afterwards
You get the source code and are not tied to me.
From idea to running product
Conversation
First understand how things run today and where they catch.
Concept
What gets built, in what order, and how we know it is done.
Architecture
Data model, interfaces and the limits of the system.
Development
In stages you can look at, instead of months of silence.
Operation
Shipping, backups, monitoring, and then it runs unattended.
Evolution
Whatever the live system reveals goes back into the product.
What I work with
Backed by the repositories of this website and of the products above.
Interface
- React
- Next.js
- Vite
- Tailwind CSS
- Framer Motion
- TypeScript
Data and logic
- Node.js
- Express
- PHP
- Python
- FastAPI
- Prisma
Databases
- PostgreSQL
- Neon
- SQLite
- MongoDB
- Redis
Interfaces and APIs
- Shopify
- Claude API
- Telegram Bot API
- Cloudinary
- Resend
Image and video
- FFmpeg
- OpenCV
- sharp
Operation and quality
- Vercel
- Render
- Docker
- Apache
- GitHub Actions
- Vitest
- Git
Standard rarely fits
A finished product arrives with the process it was designed for. Work with it long enough and you start bending the business until it fits the software, paying for features nobody opens while the one that matters is missing. I go the other way round: the process stands, and the software follows it.
Building and running belong together
Write an application, hand it over and move on, and you never learn what grates in daily use. I run my own stores and platforms myself, with everything that comes with it: outages, backups, updates, invoices. It changes how I build, because every shortcut is one I pay for later.
The same way of working as behind the camera
Film or software, the job is the same: think a thing through until it looks simple. A cut nobody notices and a form nobody has to puzzle over are the same craft. The medium changes; the care does not.