How we think about software, business and the work itself.
Essays and hands-on guides on the choices we keep making and the reasons behind them. Long-form, opinionated, written so you can decide whether we are the right fit before the first call.
Engineering
Why we build WebSocket-first
Most of the web still polls every few seconds for state it already had. We picked WebSockets early, kept maintaining the runtime when the upstream went quiet, and shipped the features Laravel itself eventually copied.
Read essay
Guide
PHP 8.2 end of life: move WordPress to PHP 8.4 without the critical error
Security support for PHP 8.2 ends on 31 December 2026. How to test the switch to PHP 8.4 on a staging copy, scan plugin code for breakage, and bring a site back when WordPress shows a critical error.
Read guide
Guide
Hacked WordPress: the first steps
Your site redirects to a fake shop, or Google warns visitors away. What not to do in the first hour, how to take the site offline the right way, lock the attacker out, keep the evidence, clean up and get the Google warning removed.
Read guide
Guide
What a security check covers, and what it does not
The free website check reads what anyone on the internet can see. The security check goes further, under a signed scope. What each one covers, three things you can look up yourself today, and how to read the report.
Read guide
Guide
Website relaunch: when it pays off and how existing URLs keep working
When a relaunch pays off and when new content is enough. Then the URL map, permanent redirects for Apache and nginx, the launch-day steps and a curl loop that tests every old address.
Read guide
Guide
WooCommerce or Shopify for an Austrian shop
Shopify's plans and payment fees from its own pricing page, what WooCommerce costs instead, how each one gets EPS, Klarna, Apple Pay and PayPal, who controls the data, and the Austrian shop duties someone has to build.
Read guide
Guide
Accessibility in online shops: what applies since June 2025
Austria's Accessibility Act covers shops that sell to consumers. Who is exempt, what it asks for technically, the statement you have to publish, who supervises, and a checklist you can run on your own checkout.
Read guide
Operations
Docker by default, Traefik on top
Every project ships containerised, every container is labelled for Traefik, every deploy looks the same. "Works on my machine" was a 2014 problem; we solved it in 2014.
Read essay
Operations
Linux everywhere
We use Linux on our laptops, our build machines and our hosts. The same OS runs the place you write the code and the place it serves traffic, so the smallest gap between dev and prod is the gap that closes the most bugs.
Read essay
Business model
Open source by default
Every recurring piece of code becomes a module. We do not bill while we package it, we maintain it after shipping, and your project gets the next ten years of fixes for free.
Read essay
Workflow
How we work with AI
We use AI assistants in our daily workflow. Honestly, deliberately, and without an AI surcharge on the invoice. Here is what they do, what they do not, and what it means for your bill.
Read essay
Trust
Every minute, with a note
We bill by the second and write a note for every minute. Open the invoice, read what we did, when, and why. No agency math, no rounded hours.
Read essay
Product · Craft
We build for the morning user
The person who pays for the software and the person who lives in it every morning are rarely the same person. We optimise for the second.
Read essay
How we engage
Built with startups
Early-stage product work is where software is allowed to be honest. We love it, we shape every other engagement around it, and we work the way founders work.
Read essay
Curious how this plays out in practice?
These essays are the why. The how shows up in the projects we ship. Drop us a note and we can talk about your specific case.