Our work

Case studies

What we found, what we did and what changed, with the numbers we can stand behind.

E-commerce · Electronics retail

From FTP edits to an AI-managed pipeline in about a week

Two online stores, 42,000 products synced from 1C, and changes made directly on the live server. One week later, the owner was shipping changes by describing them to an AI agent.

~1 week from first look to a working gated pipeline42,000 products synced from 1C, untouched by the move6 h database backup interval, restore tested
Fintech · Payments & cards

DevOps leadership for a payments fintech's PCI DSS-scope infrastructure

A European fintech processing payments, cards and crypto, with 20–50 people and a regulated core. We lead its DevOps over the long term: infrastructure as code, PCI DSS controls, payments connectivity and disaster recovery.

PCI DSS scope infrastructure built and operatedEKS KYC, AML, wallets and ledger services as codeHSM over a private link to AWS for card processing
E-commerce · B2B wholesale marketplace

A safe delivery pipeline for a 9-year-old marketplace, live in one day

A Laravel marketplace with about 3,900 commits since 2017, one dedicated server under memory pressure, and changes going straight to production. The gated pipeline went live in a single day.

1 day to a live pipeline, across 39 pull requests including real fixes49 → 9 background workers, duplicates removed, none running as root2.5 → 10.3 GB free RAM on the same server
Crypto infrastructure · Node operations

A blockchain node fleet across 8 networks, with chain-aware health checks

Eight blockchain networks on dedicated servers, built with Terraform and Ansible. A custom health daemon knows when a node has fallen behind the chain and takes it out of rotation on its own.

8 networks: Bitcoin, Ethereum, BNB Chain, Solana, XRP, TON, TRON, LitecoinChain-aware health checks decide where the load balancer sends trafficAutomatic removal of lagging nodes from rotation
Marketplace · Supplier tools

A Telegram bot that deploys itself and rolls back on its own

Suppliers use a Telegram bot to publish products to their channels, and they pay for it. A broken release means broken posts for paying customers, so the bot checks itself after every deploy and undoes the release if something is wrong.

On merge the bot deploys itself, no manual step25 s health check after every deployAutomatic rollback if the new version is not healthy
E-commerce · Hardware incident

Rescuing an online store from a failing PCIe slot and dying NVMe drives

A failing PCIe slot and two dying NVMe drives under a live online store. We got the data off with only 35 bad sectors lost, rebuilt the RAID and planned the move to a current platform.

35 bad sectors lost, the rest of the data recovered2 dying NVMe drives, RAID rebuiltMagento 2.4.8 with OpenSearch, Redis and object storage: the planned target
Marketplace · Incident response

A 5-hour marketplace outage, traced and written up the same day

A marketplace platform was down for 5 hours. The same day, we found the cause, put a stopgap in place and wrote three separate explanations: one for the developer, one for operations and one for the owner.

5 h outage of the marketplace platformSame day root cause found and a stopgap in place3 write-ups: for the developer, operations and the owner
E-commerce · Incident response

A full disk took an online store down. It was back the same afternoon

An online store stopped working because its server's disk was full. We freed 340 GB, disk use fell from 89% to 5%, and the store was selling again the same afternoon.

340 GB of disk space freed89% → 5% disk use after the clean-upSame afternoon store back online

We describe our clients generically, by sector and size, and never by name. The setups, the work and the results are real. More detail, including how a similar engagement could look for you, is available on request under NDA.

Recognise your situation?

Tell us what you are dealing with. An engineer replies within one business day and suggests the smallest useful first step.

Talk to an engineer