Skip to content
Begin a project
Index 042A digital studio in East Frisia

Production systems for ambitious operators.

We design, engineer, and operate websites, automation, and SEO that move measurable business outcomes.

Begin a projectSelected work
Scope
Web · Automation · SEO
Based
East Frisia, DE
Now accepting
Q3 2026 engagements
  • Web Engineering
  • LLM Orchestration
  • Reverse Engineering
  • Automation Systems
  • Knowledge-Grounded Agents
  • Anti-Cheat Research
  • Game Server Tooling
  • Edge Security
  • Data Pipelines
  • Performance Architecture
  • Polyglot Workers
  • Rapid Shipping
  • Inertia SSR
  • Ollama + ChromaDB RAG
  • Rust · PyO3 hot-path
  • C# .NET 8 workers
  • nginx-lua HMAC audit
  • SOPS · age secrets
  • PM2 supervised
  • Postgres 16
  • Filament CMS
  • Lighthouse 99
  • WCAG 2.2 AA
  • RUM-instrumented
  • Hetzner bare-metal
  • Zero-downtime deploy

Selected Work

Built for the people who have to live in it.

By the numbersAcross the five cases below.
  • 96Years in businessLüpsen, third generation
  • 250Staff on a single platformDrivers, ops, workshop
  • 20+Years of trade reputationHenry Loerts, Meisterbetrieb
  • 18Years of catering, now onlinePartyservice Schmidt
  • 10Game titles in one storefrontKeadesware, tier-licensed
  • 5Languages shipped to dateDE, EN, FR, PL and more
luepsen.de homepage rendered on a monitor inside a cinematic warehouse scene with light rays through a skylight
Live atluepsen.de
Case 01 / 05

Lüpsen Logistics

Family logistics, third generation.

A 96-year-old family freight company with 250 employees and 150 trucks was running a brochure site that did not match the operation. The brief was to lift the brand to match the scale, win recruiting in a tight driver market, and hand the family a system they actually run themselves.

Shipped
2026
Scope
Brand site, staff dashboard, recruiting funnel

  • Filament command center

    Staff edit every page, image, vehicle, job posting and translation in real time.

  • DE / EN / PL out of the box

    Locale-routed URLs, hreflang, full content parity across three languages.

  • Recruiting funnel

    Live job board, quick-apply form with file uploads, ATS-style admin.

  • Defense-in-depth uploads

    Seven independent security layers, fifteen measures. Every CV passes Cloudflare Turnstile, then a VirusTotal scan across 70+ antivirus engines, then lands in a private vault outside the webroot. Rate-limited, audit-logged, CSRF-protected end to end.

Stack

  • Laravel 12
  • Inertia SSR
  • React 19
  • Filament v3
  • PostgreSQL 16
  • Tailwind v4
Read the case
henry-loerts.de homepage rendered on a desktop monitor in a dark electrician workshop scene with sparks flying, copper wiring and tools on a workbench, the page showing a dark hero with the headline Professionelle Elektrotechnik in bold yellow type
Live athenry-loerts.de
Case 02 / 05

Henry Loerts Elektroinstallationen

Twenty years of master-electrician work, finally with the digital identity to match.

Henry Loerts is a Meisterbetrieb electrician serving Detern and Ostfriesland, twenty-plus years deep, the kind of name people in the village pass on by word of mouth. They had no website to back the reputation. We delivered a sleek, dark-yellow themed site in German that matches the trade, and a Filament dashboard so the owner edits services, testimonials, jobs and contact details in real time without ever opening a code editor.

Shipped
2026
Scope
Brand site, services catalog, testimonials, careers funnel, owner dashboard

  • Hero that earns the trust

    Cinematic dark hero with rotating workshop scenes, the Meisterbetrieb tagline since 2003, click-to-call number and a 24/7 emergency hint.

  • Owner-edited services catalog

    Six service pillars (installations, maintenance, lighting, networks, smart home, 24/7 emergency) managed in Filament with live cache invalidation.

  • Five-star testimonials wall

    Curated customer reviews with star ratings and excerpts, featured on home and on a dedicated reviews page, editable per entry from the dashboard.

  • Karriere funnel, structured inbox

    JobListing resource in Filament with public application page, replacing the previous WhatsApp-and-verbal-referral hiring chain.

Stack

  • Laravel 12
  • Inertia SSR
  • React 19
  • Filament v3
  • PostgreSQL 16
  • Local-SEO
Read the case
schmidt-partyservice.de homepage rendered on a desktop monitor in a warm rustic kitchen scene with hanging copper pans, fresh herbs and golden pendant lights, the page showing a catering hero with the family name in serif type
Live atschmidt-partyservice.de
Case 03 / 05

Partyservice Schmidt

Eighteen years of catering, finally with the website to match.

A family-run catering service with eighteen years of word-of-mouth and a base of Stammkunden that books the same menus year after year. They had no real online presence. We delivered a calm, modern site in German that mirrors the warmth of the operation, and a Filament dashboard so the owner edits menus, dishes, extras, gallery photos and job postings in real time without ever opening a code editor.

Shipped
2025
Scope
Brand site, menu and extras catalog, careers funnel, founder dashboard, GDPR control room

  • Menu and extras catalog

    Full catering catalog with seasonal menus, dish-level detail pages, allergen flags and bookable extras, all editable from the dashboard with live cache invalidation.

  • Live Google Reviews wall

    Reviews pulled from the Google Business profile through the Places API, cached per page and refreshable with one click from the admin.

  • Karriere funnel, owner-operated

    Job postings managed in Filament, public application form with file uploads, applicant inbox in the dashboard. Cuts the WhatsApp back-and-forth that ran the hiring before.

  • GDPR control room

    Built-in privacy compliance dashboard: cookie consent, mobile-tuned banner, scan reports, exportable compliance check, all owner-operable.

Stack

  • Laravel 11
  • Filament v3
  • PostgreSQL 16
  • Google Places
  • GDPR control room
  • Schema.org JSON-LD
Read the case
keadesware.com homepage rendered on a desktop monitor in a dark emerald scene with floating box-art renders of gaming tools, neon green accents and a premium storefront UI on screen
SourcePrivate storefront, NDA
Case 04 / 05
Private build

Keadesware

A premium-feel storefront for premium gaming tools.

Keadesware is a private gaming-tools brand selling premium client-side software across ten of the most-played competitive titles. The current site is a custom-built Laravel storefront with a tiered product catalog, a license-key issuer that ships keys per order, and an admin built on Filament v4 so the operator manages products, tiers, license keys, providers and orders without ever opening code. The proof here is not a single hero shot, it is a whole library of box-art designed by hand for the operator's Discord, each one a self-contained product render in the brand's signature emerald-on-black look.

Shipped
2026
Scope
Brand site, multi-game catalog, tiered checkout, license-key issuer, Filament admin

  • Tier-based licensing engine

    Day, week, month and lifetime tiers per product, priced and managed from Filament. Issued license keys ship with the order email and are revocable from the admin.

  • License-key issuer

    Per-order key generation with provider selection, expiry tracking and a clean revocation path. No spreadsheets, no manual hand-off, no leaked codes.

  • Hand-designed box-art library

    A whole product range of bespoke render-style box-art, each one shipped to the operator's Discord and pinned in the storefront. The visual brand is the moat.

  • Filament v4 from day one

    Products, tiers, license keys, providers, orders and customer messages all run from a single admin tuned for one operator.

Stack

  • Laravel 12
  • Filament v4
  • PostgreSQL 16
  • Tier-based licensing
  • License-key issuer
  • Custom box-art library
Read the case
tli-hub.com homepage rendered on a desktop monitor with a dark, fiery Torchlight Infinite themed scene, ember particles and rune sigils around the screen, the page showing the TLI-Hub hero with hero portraits, build cards and a database menu
Live attli-hub.com
Case 05 / 05
In progress

TLI-Hub

A community hub and build planner running on the live game's own data.

TLI-Hub is a wiki and build planner for Torchlight Infinite that runs on the game's actual data, not on community spreadsheets. Getting there meant bypassing the client's anti-debug, anti-tamper and telemetry layers cleanly, dumping the embedded SDK, recovering the AES key it ships with and pulling a full client dump. From that one source of truth I model heroes, skills, talents, affixes, item bases, memories and pact-spirits in PostgreSQL, then build the planner, the guide platform and the desktop importer on top.

Shipped
2026
Scope
Wiki + database, build guides, farming guides, author program with affiliate links, one-click build importer

  • Planner on the game's own data

    Heroes, skills, talents, affixes, item bases, memories and pact-spirits modeled in PostgreSQL from a full client dump. Tooltip numbers match in-game numbers because they are the same numbers.

  • Author program, affiliate revenue

    Sign up, publish a build or farming guide, embed your own affiliate links inside it and earn from the site's traffic. Likes, comments and per-author analytics out of the box.

  • One-click build importer

    A small companion app reads any guide on the site and writes it straight into the live client. Shipped behind a code-signed installer for players who want it.

  • Anti-debug + anti-tamper bypassed

    The client's anti-debug, anti-tamper and telemetry layers were bypassed clean enough to dump the embedded SDK and recover the AES key. The how stays private, on purpose.

Stack

  • Laravel 12
  • Inertia SSR
  • React 19
  • PostgreSQL 16
  • OAuth (Socialite)
  • Code-signed installer
Read the case

More work

Five is a sample. The full archive lives here.

View every project

Filter by stack, industry and outcome.

How we work

Four steps, no theatre, no surprise invoices.

Every engagement runs the same way. You see the staging URL on day one, ship to it every Friday, and walk away owning the keys. Here is what each step actually looks like.

Step 01 / 041 week

Discover

We sit down with the operators, not just the founder. We audit the stack you already have, learn the words your team uses for things, and write a one-page brief that everyone signs before a line of code is written.

What you get

  • Stakeholder interviews with the people who actually use the system
  • Honest audit of the current stack, hosting and data
  • One-page brief with goals, scope, success metrics and a fixed price

If we cannot describe the win in one page, the brief is not done.

Step 02 / 041 to 2 weeks

Architect

We pick the stack honestly, draw the data model, and ship a clickable prototype on a staging URL. You log in, click around, and tell us where reality and the brief disagree before we build anything expensive.

What you get

  • Data model and integration map you can actually read
  • Stack decision record, no buzzwords, just trade-offs
  • Clickable prototype on staging, locked behind your password

Cheap to change in a prototype. Expensive to change in production.

Step 03 / 044 to 12 weeks

Build

We ship to staging every Friday. You log in over the weekend, actually use it, and we adjust on Monday. No big-bang reveal, no demo-only features. The thing you see is the thing that goes live.

What you get

  • Weekly Friday ship to staging, with a written changelog
  • Real data, real users, real edge cases from week two onwards
  • Performance, accessibility and security gates enforced in CI

If it is not on staging, it is not real. If it is on staging, it is honest.

Step 04 / 04Ongoing

Hand off

You get the keys. Filament admin, runbooks, monitoring dashboards, source code, deployment pipeline. Your team can take it from here, or we stay on a small retainer for new features and on-call coverage. Your call, no lock-in.

What you get

  • Filament admin tuned for your team, not for us
  • Runbooks for the three things that will actually break
  • Source code, infra-as-code, and the deployment pipeline you watched us use

A handover is good when the team forgets we ever ran it.

Studio

One operator, every layer.

P42 Studio is one person. No agency, no juniors, no handover between sales and the people who write the code. You talk to the same person who picks the stack, types the migrations and watches the deploy.

Black and white rear-view photo of Thies Bergenthal at a multi-monitor workstation, with framed The Sun and The Map tarot cards on the wall above the screens.
Real nameThies Bergenthal
Studio 01 / 01

I have been writing production code for thirteen years and running my own infrastructure for most of them. Web platforms, content automation brains, low-level reverse engineering, secure tooling, the whole stack. Different domains, same posture: build it well, run it yourself, take responsibility when something breaks at 2am.

What that buys you on a project is simple. Decisions land in hours, not in meetings. The person who promises a thing is the person who ships it. There is no junior between us. There is no slide deck between the brief and the code. You see the staging URL on day one and the keys on day done.

Solo does not mean alone. There is a small circle of operators I trust and bring in when a project needs a hand, and I take work from agencies and other developers who need a senior pair of hands they can hand the keys to. Quietly, under NDA, without my name on the credits if that is what the engagement needs.

Based in
Niedersachsen, DE, working internationally
Time zone
Europe / Berlin, flexible
Working in
DE, EN

Track record

  • Shipping production code since2013
  • Projects shipped to date110+
  • Internal AI brain serving themSLTR42
  • Where it runsOwn homelab + Hetzner
  • TopologyProxmox CTs across nodes, OPNsense + WireGuard, reverse-proxied
CurrentlyAccepting one new engagement for Q3 2026.

Ways to work together

  • Direct project

    You bring the brief, I run the engagement end to end on my infrastructure. Discover, architect, build, hand off the keys.

  • Agency overflow

    Your studio has a project that needs a senior full-stack pair of hands. I slot in under your brand, ship under your name, invoice you, leave clean.

  • Embedded contractor

    Founder team or in-house dev needs reinforcements on a hard system: AI pipelines, hardened uploads, infra, reversing, performance work. Day rate, NDA, defined scope.

Engagement posture

  • NDA-ready
  • Source-private builds on request
  • No public case study unless you ask
  • White-label for partner studios

Solo by design. Deep on purpose. Boring where it matters.

Free tool

See your site the way Google sees it.

Run a real Lighthouse audit, Core Web Vitals, structured data and 25+ checks, finished in under a minute. No signup, no email, fully sandboxed.

Run a free SEO auditLighthouse · Core Web Vitals · 27 checks

Frequently asked

What people ask before they email.

  • It depends on scope, not on hours. A focused marketing site lands in the low single-digit thousands. A serious web application with auth, payments, dashboards and infrastructure is five figures and up. I quote a fixed price for the scope after the first conversation, not a hand-wavy range. If your budget is honest you will get an honest answer about what fits.

  • I run one engagement at a time and usually have a slot inside two to six weeks. A small site ships in two to four weeks of focused work. A larger application is six to twelve weeks depending on integrations. You get a working staging URL in week one, every week, no exceptions.

  • I will tell you on the same day. If the project is a fit and the timing is not, I either propose a slot you can wait for, or I refer you to one of the operators in my circle and stay close as a second pair of eyes. I do not say yes to projects I cannot give my full attention.

  • Yes to both, regularly. White-label engagements for agencies and partner studios are a normal part of the work. NDAs are signed before any technical detail is shared. Source code, infrastructure access and any client material stays private and is never used in a public case study unless you explicitly ask.

  • You do. Source ships to a repository you control, infrastructure runs in your accounts unless you explicitly want me to host. Hand-off includes documented runbooks, environment files and a recorded walkthrough. No lock-in, no proprietary platform you have to keep paying me to access.

  • Both. Most engagements start as a fixed-scope project and roll into a small monthly retainer for evolution, performance work and on-call response. The retainer is opt-in, not a contract trap, and you can pause or end it at the close of any month.

  • Yes. I have shipped into Laravel, Node, Django, Next.js and bare-metal Rust codebases owned by other teams. If your stack is reasonable I will respect it. If it is fighting you I will say so, with the trade-offs spelled out, and let you decide.

  • I build them where they earn their keep and I push back where they do not. SLTR42, my own content brain, runs production AI pipelines daily. I have also talked clients out of adding a chatbot that would have made their product worse. The deciding question is always whether the user gets a better outcome, not whether the deck looks more modern.

Start a conversation

Tell me what you are actually building.

One operator on the other end of this form. No discovery call gauntlet, no SDR. You will hear back from me, usually inside a working day, sometimes faster.

Project enquiry

Protected by Cloudflare Turnstile. No tracking, no cookies set unless a challenge runs.