Skip to content

About Kiriu Tech

We are an international product engineering company. Since 2024 we have shipped 40 systems for clients in 15 countries, and we still measure success the same way: does it hold in production.

Kiriu Tech in numbers

2024
Founded in Warsaw
60+
Engineers in-house
40+
Products shipped
15
Countries served
94%
Client retention
1.4y
Average partnership

About

How we started

Kiriu Tech began in 2024 in Warsaw with four engineers and one rule that has not changed: nothing ships without a test, a rollback plan and somebody accountable for it in production. In two years we grew to 60 engineers across two studios — Warsaw and Kyiv — without becoming a body shop: every client works with named people, not with anonymous capacity.

How we deliver

Mandatory code reviewRollback plan per releaseSAST in CINamed delivery ownerNDA before the first call

What we hold to

01

Say the real number

Estimates come as ranges with confidence levels. When something slips, you hear it the day it slips, not at the milestone review.

02

Own it in production

The team that builds a service carries the pager for it. That single rule removes most of the arguments about quality.

03

Write it down

Architecture decisions, runbooks, threat models. If it only exists in somebody's head, it does not exist.

04

Leave it transferable

Every engagement ends with a handover that works. We would rather be re-hired than be impossible to replace.

Our people

Executive team

The three people accountable for strategy, operations and the technical standard.

Ivan Taranenko

Ivan Taranenko

CEO — Chief Executive Officer

Sets the company strategy and owns the client partnerships. Signs off every architecture decision record that carries commercial risk.

Book 30 minutes
Kyiv, Ukraine
Sergey Simchuk

Sergey Simchuk

CTO — Chief Technology Officer

Runs the engineering guilds and owns the technical standard every project is measured against. Final call on stack, architecture and release gates.

Book 30 minutes
Kyiv, Ukraine
Olha Kovalenko

Olha Kovalenko

CGO — Chief Growth Officer

Owns growth: new markets, the partner network and the commercial side of every engagement from first call to signed statement of work.

Book 30 minutes
Kyiv, Ukraine

Heads of practice

Every practice has a named owner who sets its standard and answers for its output.

OM

Olena Marchuk

Head of .NET Practice

Warsaw, Poland

.NET architectureAzure
DR

Davide Rinaldi

Head of Systems Engineering

Warsaw, Poland

C++Low-latency systems
NB

Nadia Benali

Head of Web Practice

Kyiv, Ukraine

PHPNext.jsWeb performance
JO

James Okoro

Head of Cloud & SRE

Kyiv, Ukraine

KubernetesObservabilityFinOps
SL

Sofia Lindqvist

Head of Design

Kyiv, Ukraine

Product designDesign systemsAccessibility
RM

Rahul Mehta

Head of Data & AI

Warsaw, Poland

Data platformsML engineering
VS

Viktor Shevchenko

Head of Crypto & Digital Assets

Kyiv, Ukraine

Matching enginesCustodyMiCA compliance
IM

Iryna Melnyk

Head of Quality Engineering

Kyiv, Ukraine

Test strategyAutomationRelease gates
MZ

Marek Zieliński

Head of Mobile Practice

Warsaw, Poland

iOSAndroidFlutter
AL

Agata Lis

Head of Delivery

Warsaw, Poland

DeliveryPortfolio reviewClient governance
KN

Karolina Nowak

Head of People

Warsaw, Poland

HiringGrowth frameworks

How we work

The delivery model

A delivery model built so you always know what stage you are at, what it produced and what it cost.

01

Discovery & scoping

Duration: 1–2 weeks

A paid two-week sprint that turns a brief into a backlog, an architecture sketch and a budget you can defend internally.

Artefacts

  • Product brief
  • Solution architecture
  • Risk register
  • Estimate with ranges
02

Design & prototyping

Duration: 2–5 weeks

Interface design, clickable prototypes and usability testing with real users before a line of production code is written.

Artefacts

  • UX flows
  • UI kit & design system
  • Clickable prototype
  • Accessibility baseline
03

Architecture & setup

Duration: 1–2 weeks

Repositories, environments, CI/CD, observability and security baselines are provisioned as code before feature work starts.

Artefacts

  • Infrastructure as code
  • CI/CD pipelines
  • Threat model
  • Definition of done
04

Build in two-week increments

Duration: Continuous

Cross-functional squads ship to a staging environment every sprint. You get a demo, a changelog and a burn-up chart — not a status text.

Artefacts

  • Sprint demo
  • Release notes
  • Test reports
  • Updated roadmap
05

Hardening & release

Duration: 2–4 weeks

Load tests, penetration testing, SLO validation and a rehearsed go-live with a rollback path.

Artefacts

  • Load test report
  • Pen-test remediation
  • Runbooks
  • Go-live checklist
06

Run, measure, evolve

Duration: Ongoing

Managed SLAs from 8×5 to 24×7, quarterly architecture reviews and a roadmap driven by product analytics.

Artefacts

  • SLA reporting
  • Cost optimisation
  • Quarterly review
  • Knowledge transfer

Recognition

2026

Top 100 engineering partners

Nordic Delivery Index

2026

Fastest-growing engineering firms

Baltic Tech Review

2025

Twenty firms to watch

Open Delivery Digest

2025

Regional service provider ranking

Vistula Business Weekly

2025

Site of the month

Interface Craft Awards

2026

Interface of the year

Kyiv Frontend Summit

2026

Employer of the year

Warsaw Software Guild

2026

Engineering partner shortlist

Central Europe Product Forum

Where we are

Warsaw

HQ

Poland

Prosta 51, 00-838 Warsaw

[email protected]

Kyiv

Ukraine

Velyka Vasylkivska 72, 03150 Kyiv

[email protected]

Tell us what you are building

Send a brief and a solution architect replies within one business day — with questions, not with a template.