Phone
Address
Wehlistraße 291/1/47
1020 Vienna
OPEN SOURCE · SHIPPED
A CMS, an email client, a file manager, a terminal crawler, a component library, and many open-source packages. All shipped by one developer, using the same foundation and AI workflow I set up for client teams. This page is the argument for Die Werkstatt, made in code rather than copy.
Any developer can describe a method. Far fewer will hand you the repositories and invite you to check.
Each of these started as a problem I hit twice and got tired of working around. Each one is public, running, and readable, including the parts I got wrong and fixed later. That's the standard of evidence I'd want before hiring someone, so it's the one I offer.
Headless CMS · Laravel + Vue
The user-first headless CMS. Laravel and Vue, 100% open source core.
What it solves: headless CMS setup that eats a week, editor experiences developers quietly hate, and content changes with no usable history.
Key features:
This site runs on it. So does every client site I build.
Cross-platform email client · Tauri + Nuxt
Email organised as a board rather than an infinite list, for developers and knowledge workers who treat the inbox as a queue of work. Lightweight, local-first, and quiet by default.
Remote file manager · Rust + GPUI
One cockpit for every filesystem: S3, SFTP, FTP, WebDAV, Google Cloud, Azure Blob, Drive, Dropbox, OneDrive, local. Dual-pane, drag and drop, and a transfer queue in SQLite that survives a crash and resumes mid-file.
Ships with an MCP server, so an agent can drive your storage directly.
Terminal crawler & SEO analyser · Rust + Tokio
Concurrent crawling with a live terminal interface, SEO scoring and issue detection, and optional WebDriver for JavaScript-heavy sites. It also handles sitemap discovery, robots.txt compliance, and CSV or JSON streaming export.
Vue component library · TypeScript
50+ components taken straight from production client work: the modals, tables, and form primitives worth building once. Styling you can override without a fight, keyboard and screen reader support included.
For the artisans
Small, boring, and used in every project I ship. Nothing clever, just the parts I refuse to write again.
The starting point I actually use, and the same one your Foundation phase begins from: authentication, API structure, and a deployment pipeline that works on day one.
The foundation, the reference implementation, and the agent workflow behind these products are the same ones I set up for client teams, then hand over.