Tallinn · Est. 2012 · Still shipping
Built to outlast the hype.
Delivered at modern speed.
Senior engineering. Long-term ownership. Platforms that don't break. Since 2012.
We work with industrial operators, telecoms, e-commerce platforms, and retail groups across the Baltics and Nordics. Most engagements run for years, not months. We do not publish a client list. That is deliberate: several of ours have been targeted by pretexting attacks built on publicly listed client information. Verifiable references after a first conversation.
§ 01 — What we build
What we build
Two things we've spent more than a decade getting right, plus the integrations and rescue work that keeps them running.
Custom Laravel platforms
Custom backends with real business rules. Order systems, billing, reporting, forecasting, integrations with the ERPs and data warehouses you don't get to choose. The unglamorous code that runs a company — not the kind that ends up in a pitch deck. We write it like it has to last ten years, because most of ours has.
Modern frontends — React, Next.js, React Native
Web and mobile apps that feel deliberate. No design-system theatre, no half-finished features. We pick the smallest stack that gets the job done and we maintain it ourselves.
Business system integrations
ERP, accounting, prescription centers, payment providers, telcos, fleet systems. The work that doesn't get talked about because when it works, nobody notices. We make sure nobody notices.
Legacy rescue & stabilisation
You inherited a system that scares everyone — older WordPress and WooCommerce stacks, vanilla PHP, the codebases other agencies decline to touch. We get inside it, capture the business rules as tests, and either stabilise it or rebuild it in parallel without breaking production. Quiet, methodical, no rewrites for their own sake.
§ 02 — Selected work
Selected work
Three engagements, described by the engineering, not the client.
An industrial operator's twelve-year-old operational platform — forty screens, around a hundred users across four countries — had to move off vanilla PHP without breaking a single reported number.
Rebuilt in parallel on Laravel 12. 1,100+ tests against the legacy. Cutover without incident.
Read case study →A telecoms operator needed a multi-market storefront for SIM and eSIM purchase, activation, and top-up.
Live worldwide. Purchase, activation, top-up, and billing in one storefront.
A Nordic FMCG group needed an order platform that handled contractual pricing, availability, and approval flows alongside walk-in customers.
Replaced a brittle legacy stack. Ordering wired end-to-end into SAP and the product information system.
§ 03 — How we work
How we work
Three habits, not a methodology.
Senior-led delivery. Engineers measured in years, not months. Claude Code is part of our stack the same way an IDE is, but generated code that nobody understands never reaches your repo. We don't have juniors learning on your project, and we don't outsource the hard parts.
Long-term ownership. Most of our engagements outlast three years. We don't hand off and disappear.
Tests over documentation. Documentation rots. Tests don't — they break loudly when reality changes. When we inherit a system, the first thing we do is capture what it actually does in tests. That's what lets us change it without fear.
// What a few of those captured rules look like. it('rounds fees half-up, not half-even'); it('monthly aggregation matches legacy to the cent'); it('zero-quantity orders never reach billing');