—Studio

We are the people you call at Day 1000.

A small digital engineering studio with its team in Germany and Spain, working with businesses across the EU. Small enough that you speak to the people writing the code. Kolo is Ukrainian for circle: the life of a system, from Day 0 to Day 1000 — and we stay for the whole circle.

01How we work with you

Direct contact with the people writing the code.

No account layer between you and the engineering. You describe the problem to someone who will be in the codebase the same week.

01

One point of contact

A named engineer who knows your system, its history and its constraints.
02

Written decisions

Scope, architecture choices and trade-offs in writing, so they survive holidays and handovers.
03

Specialists when needed

For work outside our depth — specialised infrastructure, design, compliance — we bring in trusted specialists rather than improvising.
02Where the experience sits

Both ends of the line.

We have shipped first releases and we have inherited systems a decade old. The second is harder, and it is most of the work.

  1. Day 0

    It ships

    A first release small enough to put in front of real users, and structured so the second release does not require a rewrite.

    LaravelReactPostgreSQL
  2. Day 100

    It changes

    The data model that looked right at launch meets how the business actually works. Integrations arrive. Someone asks for a report nobody planned.

    REST APIDocker
  3. Day 1000

    It is inherited

    The people who wrote it have moved on. The framework is three majors behind. The system is still running the business.

    PHPSymfonyMySQL
    This is where most projects reach us
New product development

Taking a product from concept to a first release: data model, API, web and mobile clients, and the deployment around them. We keep the first version small on purpose.

LaravelTypeScriptReactReact NativeNode.jsPostgreSQL
Existing and legacy systems

Reading an inherited codebase, getting it running locally and in CI, upgrading it in steps, and extending it without breaking what the business already depends on.

PHPSymfonyMySQLREST APIAWS
03Team extension
Most of our work has happened inside other companies’ codebases and other companies’ processes.Working principle

We have spent years working as part of internal teams — their repositories, their code review, their release process, across timezones. Work like that is not judged on a portfolio. It is judged on whether the client keeps you, and that is the reference we have.

04Facts

The practical detail

Team in
Germany · Spain
Working with
Businesses in Germany and across the EU
Languages
German · English · Spanish
Engagements
System-Check · Retainer · Team extension · Project · Consulting
Hosting
EU-based, or your own infrastructure
Sectors
Restaurant platforms · Data services · E-commerce

Start with the problem, not the technology.

Your contact

Kyrylo KovtunenkoFounder

Germany · EU · DE / EN / ES