Projects
Many projects are confidential. We show anonymized technical work and outcomes from projects we have actually worked on without exposing clients or data.
8 results
How a property platform became extendable again
New workflows without rewriting the mature domain — a codebase that can grow on purpose again.
Read storyHow meter data and billing became one clear flow
APIs, validation and traceable handoffs across energy processes — without losing data mid-pipeline.
Read storyFrom manual shipping to reproducible releases
Builds, tests and releases instead of Friday-night deploys — a pipeline the team can repeat.
Read storyAnonymized, but technically concrete.
Discuss a similar projectBusiness logic and growing systems
Data flows, billing and integrations
Releases, stabilization and operations
Making legacy PHP safely changeable again
Critical paths mapped, tests as a safety net, changes without fear of silent regressions.
Read storyMoving AI from demo to real billing workflows
AI where invoices actually happen — embedded in product flows instead of a demo corner.
Read storyConnecting Linux, monitoring and security into one ops base
Deployments, backups and security signals in one operating model — not scattered tools.
Read storyShops launched, ERP-connected and kept operable
Shopify, Shopware or WooCommerce — customized, ERP-connected and operable day to day.
Read storyWordPress sites with planned technical care
Updates, backups, monitoring and security checks as a repeatable rhythm — not fire drills.
Read storyDoes your project sound like one of these patterns?
Tell us what is not reliable today. We will help you frame the problem.
