Tallinn · Est. 2012
Built to outlast the hype.
Delivered at modern speed.
We build and maintain business software platforms. Senior engineers do the work, and we stay on after launch.
We work with industrial operators, telecoms, e-commerce platforms, and retail groups across the Baltics and Nordics. Most engagements run for years. We don't publish client names for security reasons. References are available after a first call.
§ 01 — What we build
What we build
Custom backends, modern frontends, and the integration and legacy work around them. The full list is on the Services page.
Custom Laravel platforms
We build custom backends with real business rules: order systems, billing, reporting, forecasting, and integrations with ERPs and data warehouses. We write this code expecting it to run for ten years, because most of ours has.
Modern frontends — React, Next.js, React Native
We build web and mobile apps, finish the features we start, and maintain the stack ourselves. We pick the smallest set of tools that does the job.
Business system integrations
We connect platforms to ERPs, accounting systems, prescription centers, payment providers, telcos, and fleet systems, and we keep those connections running.
Legacy rescue & stabilisation
We take over older systems: WordPress and WooCommerce stacks, vanilla PHP, the codebases other agencies decline to touch. We capture the business rules as tests, then stabilise the system or rebuild it in parallel without breaking production.
§ 02 — Selected work
Selected work
Six 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.
Read case study →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.
Read case study →A consumer app for private wine cellars: photograph a label, let the system identify the bottle, and place it in a model of your actual cellar — offline, because cellars have no signal.
One Expo/React Native codebase on a Laravel API. OCR and LLM extraction turn a label photo into a catalogued bottle.
Read case study →A Nordic wholesale supplier's closed B2B store had outgrown its page-builder stack. Contract pricing, reserved stock, and credit all live in the ERP, and the store had to match it at all times.
Replatformed onto a component-based stack. Pricing, stock, credit, orders, and invoices resolved against Business Central.
Read case study →A commercial property manager divided every building's utility costs across tenants in a spreadsheet only one person could safely operate.
Supplier e-invoices in, tenant allocation rules applied, sales invoices out to accounting. Monthly, for the whole portfolio.
Read case study →§ 03 — How we work
How we work
Senior-led delivery. Every engineer on your project is senior, and we do the hard parts ourselves. Claude Code is part of our toolchain, but generated code that nobody understands never reaches your repository.
Long-term ownership. Most of our engagements run past three years. We maintain what we build.
Tests over documentation. When we inherit a system, the first thing we do is capture what it actually does in tests. That is what lets us change it safely.
// 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');