130+ projects. Every hour scoped.
Most of them you'll never see published.
The bulk of our WordPress work is white-label — agency-owned, named only when the partner agency clears it. Below: the projects we can name, and brief teasers of the ones we can't. Engineering-practice work — custom development, data, and infrastructure — lives here too; use the practice filter to narrow. Everything else is described without identifying details.
Each card below shows hours of build effort across calendar days. Hours come from Redmine, calendar from kickoff to handoff. Filter by industry or engagement type below — 136 projects authorised for publication; the rest are teased without identifying details.
Selected work
Glass Configurator: 900 hours, not signed off yet
A 3,393-hour estimate did not fit the budget. We split the work, cut the scope fivefold, joined the client's team and shipped a working version in 69 days.
An 18-month estimate we refused to lowball
The full estimate came to 3,393 hours against a budget several times smaller. We kept the number, sold discovery as its own stage, and the client came back.
397 days stalled and a working version
After 397 days of standstill we cut the agreed scope from 3,393 hours to 667. The product reached pilot use in 69 days and two factories checked its…
Two engineers inside the client’s team
The client already had developers. We placed 2 engineers inside their team and took technical leadership: 632 days, first version in 69, code stayed in-house.
How to tell whether you need AI, before you pay for it
Five steps: pick a narrow zone and build a prototype, choose the security perimeter, plan for failure, roll the solution out to neighbouring processes, and budget honestly for…
The contractor who talks you out: 9 episodes over 2 years
9 documented episodes over 2 years where a DevOps contractor talked the client out of billable work, and why the client then trusted us with its end client.
~70 incidents over 24 months: the bot notices before people do
~70 incidents over 24 months: the bot notices first, the engineer is in within 1-9 minutes, recovery in 7-50. Incident response without a formal SLA.
Peak-season crisis: two days, four root causes
A Bitrix store goes down in peak season. Four root causes: panel antivirus, a one-digit DB-config typo, disk degradation, a slow DDoS. Closed in two days.
GitLab: from 15.4 to 18.11 over two years, zero data loss
A studio's self-hosted GitLab, stuck on 15.4: two major versions and two PostgreSQL migrations in 5 hours, patches on release day, zero data loss in two years.
Migrating an infected NextCloud: 400 GB with no docker in 7 hours
The studio's old cloud caught a virus through docker. Not a cleanup but a new server: a clean NextCloud, no containers, 400 GB moved nightly. 7h tracked.
A two-byte diagnosis: a seven-month bug closed in one evening
Seven months of broken Excel downloads: fine on disk, unopenable in the browser. Diagnosed in one evening to two stray CRLF bytes from the code.
An inherited fleet of 12 VDS: audited in 6 hours, in order within a month
A web studio handed us 12 VDS where 'something reliably breaks weekly.' Audit in 6h, fleet update in 1.75h not six, a wiki page per server, monitoring in…
Server operations as a service: 4.5 years of infrastructure under a growing B2B product
From shared hosting to a ClickHouse server cluster, a scraping VPS farm, daily S3 backups, Grafana monitoring. Every upgrade signed off, every outage closed.
A B2B platform on retainer: 4.5 years of unbroken work, the parser as the core of the service
One retainer keeps an in-house product alive: nonstop registry parsing, small prepaid changes, incident response in minutes, backups and protection.
How we work: prototype before the invoice, economics before the start, an honest status on every task
Our method on the Certificate Analytics platform: before taking money we prototype, test viability, model the economics, and talk you out of weak ideas.
DocMarket — an MVP for self-service sale of data exports
A new product from Certificate Analytics: automating a manual B2C service of selling data exports through a self-service web app with on-site payment.
Parsing three government certification registries (KG/KZ/BY): around 260 hours on Laravel queues
Parsers for the Kyrgyz, Kazakh, and Belarusian certification registries: Laravel Horizon queues, proxy rotation, incremental collection by next number.
From attack to hardening and migration: security and infrastructure for a B2B platform in 2025–2026
Investigating a server breach via an open Docker API: rootkit and miner removed, login history with IP whitelist, then a January 2026 migration, documented.
Want to see more?
If you're an agency considering us, we can share deeper detail on any project over messenger or email — staging URLs, screenshots, the QA-loop workflow, enough to gauge fit.
Request a portfolio walkthrough