About the company

Who we are

A German company based in Munich. The engineering team in Wrocław.

Who stands behind the company, since when, in what composition, and by what rules we work. Where there is a specific task, we say whether it falls within our scope and on what terms.

Outline your case
Company

Company profile

Legal form and registered office
blue veery GmbH, Munich. A German company — the contract, the billing and the liability sit on the German side.
Year founded
2015.
Management
Magdalena Niedziela-Drozd and Cezary Drozd. The company is privately held, with no outside investor.
Locations
Munich — the registered office and the management. Wrocław — the engineering team.
Languages
The working language of projects is English. The management also holds client discussions in German, including technical ones — whichever suits the client better.
Markets
German-speaking countries: Germany, Austria, Switzerland.
Experience

Twenty-six years in software development

That is the length of our experience in the industry — gained first in other companies and then in our own business. blue veery GmbH has been running since 2015.

For the client this means that technical and commercial decisions here are taken by people who wrote code themselves and were responsible for maintaining it for years — not only for selling it.

Team

Team and capacity

We work with a team of around forty engineers in Wrocław, supported by interface designers. They work in parallel on projects for different clients. The management works in Munich — that is where commercial discussions are held and where the company answers for the work.

The team for a project is matched to its scope and that team is named in the contract. Capacity of this size means there is someone to choose from also when a task calls for a rarer specialisation, or when the staffing changes along the way.

Scope

What we do

We work in three closed packages, each with a defined scope, a fixed price and a deadline written into the contract.

AI code audit and security

review of existing code

A review of code produced with AI tools: security, dependencies, tests, readiness for release.

Audit details →

Turnkey software modules

building new functionality

A closed module built in sprints, accepted on the client’s side, at a price agreed before the start.

Module details →

Refactoring and technical debt

putting an existing system in order

Putting the code in order in stages, measured before and after, without halting ongoing development.

Refactoring details →

We also maintain our own products and libraries that we use in client projects.

Working together

The rules we work by

Four rules that apply from the first conversation through to acceptance of the work.

We flag unnecessary work before quotingWhere we consider part of the scope unnecessary, or the problem solvable more cheaply, we say so before the proposal, not after acceptance.
The price and deadline are in the contractNot in a presentation and not in an email. Scope, price and date are written down before the work starts.
Quality rests on recognised standardsISO/IEC 25010, the BSI guidelines and OWASP. The page on quality sets out where in the process each of them takes effect.
No code goes to production without a reviewEvery change goes through a second engineer’s review and the automated tests and scans. That applies to code produced with AI as well.

How we work in practice

Tell us what needs doing. The initial assessment of the starting point is free of charge — after it we propose a scope of work, a fixed price and a deadline.

Outline your case